Problem with L2TP connectivity and RUT241

Hello,

We’re having difficulties with most, if not all, recent RUT241s, updated to the latest firmware, connecting to our L2TP VPN. Here is a typical log file (I masked all personal info) :

Tue Dec 5 13:07:39 2023 daemon.notice xl2tpd[3986]: Connecting to host l2tpXX.XXXXX.XXXXXX.XX, port 1701
Tue Dec 5 13:07:39 2023 daemon.notice xl2tpd[3986]: Connection established to XXX.XXX.X.XX, XXXX. Local: 61990, Remote: 29634 (ref=0/0).
Tue Dec 5 13:07:39 2023 daemon.notice xl2tpd[3986]: Calling on tunnel 61990
Tue Dec 5 13:07:39 2023 daemon.info xl2tpd[3986]: Can not find tunnel 16403 (refhim=0)
Tue Dec 5 13:07:39 2023 daemon.debug xl2tpd[3986]: network_thread: unable to find call or tunnel to handle packet. call = 0, tunnel = 16403 Dumping.
Tue Dec 5 13:07:44 2023 daemon.debug xl2tpd[3986]: Unable to deliver closing message for tunnel 28047. Destroying anyway.
Tue Dec 5 13:07:47 2023 daemon.info xl2tpd[3986]: Can not find tunnel 16403 (refhim=0)
Tue Dec 5 13:07:47 2023 daemon.debug xl2tpd[3986]: network_thread: unable to find call or tunnel to handle packet. call = 0, tunnel = 16403 Dumping.
Tue Dec 5 13:07:53 2023 daemon.info xl2tpd[3986]: Can not find tunnel 28047 (refhim=0)
Tue Dec 5 13:07:53 2023 daemon.debug xl2tpd[3986]: network_thread: unable to find call or tunnel to handle packet. call = 0, tunnel = 28047 Dumping.
Tue Dec 5 13:07:54 2023 daemon.warn xl2tpd[3986]: network_thread: recvfrom returned error 146 (Connection refused)
Tue Dec 5 13:07:54 2023 daemon.info xl2tpd[3986]: Can not find tunnel 28047 (refhim=0)
Tue Dec 5 13:07:54 2023 daemon.debug xl2tpd[3986]: network_thread: unable to find call or tunnel to handle packet. call = 0, tunnel = 28047 Dumping.
Tue Dec 5 13:07:55 2023 daemon.info xl2tpd[3986]: Can not find tunnel 28047 (refhim=0)
Tue Dec 5 13:07:55 2023 daemon.debug xl2tpd[3986]: network_thread: unable to find call or tunnel to handle packet. call = 0, tunnel = 28047 Dumping.
Tue Dec 5 13:07:57 2023 daemon.info xl2tpd[3986]: Can not find tunnel 28047 (refhim=0)
Tue Dec 5 13:07:57 2023 daemon.debug xl2tpd[3986]: network_thread: unable to find call or tunnel to handle packet. call = 0, tunnel = 28047 Dumping.
Tue Dec 5 13:07:59 2023 daemon.info xl2tpd[3986]: Disconnecting from XXX.XXX.X.XX, Local: 61990, Remote: 29634
Tue Dec 5 13:07:59 2023 daemon.info xl2tpd[3986]: Connection 29634 closed to XXX.XXX.X.XX, port 1701 (Goodbye!)

Rince and repeat.
I talked with the company hosting the VPN and they say this is the problem, that it’s not on their side.
This actual problem is preventing us from deploying our routers on new sites.

Has anybody ever faced this before ? I’ve read that this process was updated in the latest firmware, could it come from this ?

Thanks in advance,
Safe-T

Hello,

I did a test on my side, using the RUT241 running the latest firmware (07.05.04) and I successfully established an L2TP tunnel with a server.

In your case, kindly check the VPN provider if extra configuration is required such as CHAP and PAP authentication.

EDIT:
The tunnel has been up for 40 mins now and the connection is still up and stable.

Best regards,
Robert

Hi Robert, thanks for taking the time to do that.
It seems the problem comes from mob1s1a1 connections, depending on the mobile operator, some successfully manage to connect to the L2TP, others don’t … so despite what I was told, it is not a problem of xl2tpd.
Thanks again for your help,
Safe T

This topic was automatically closed after 15 days. New replies are no longer allowed.