10857 questions

12933 answers

20163 comments

25452 members

0 votes
46 views 1 comments
by

hello!

after rut240 restart l2tp connection works. after 1 minute restart connection lost.

here is systemlog. 

Wed Jun  8 18:38:56 2022 daemon.notice netifd: Interface 'johvi2' is setting up now

Wed Jun  8 18:38:56 2022 daemon.notice xl2tpd[16465]: Connecting to host 213.35.0.0, port 1701

Wed Jun  8 18:38:56 2022 daemon.info xl2tpd[16465]: Can not find tunnel 21788 (refhim=0)

Wed Jun  8 18:38:56 2022 daemon.debug xl2tpd[16465]: network_thread: unable to find call or tunnel to handle packet.  call = 34045, tunnel = 21788 Dumping.

Wed Jun  8 18:38:57 2022 daemon.info xl2tpd[16465]: Can not find tunnel 21788 (refhim=0)

Wed Jun  8 18:38:57 2022 daemon.debug xl2tpd[16465]: network_thread: unable to find call or tunnel to handle packet.  call = 34045, tunnel = 21788 Dumping.

Wed Jun  8 18:38:57 2022 daemon.info xl2tpd[16465]: Can not find tunnel 21788 (refhim=0)

Wed Jun  8 18:38:57 2022 daemon.debug xl2tpd[16465]: network_thread: unable to find call or tunnel to handle packet.  call = 34045, tunnel = 21788 Dumping.

Wed Jun  8 18:38:59 2022 daemon.info xl2tpd[16465]: Can not find tunnel 21788 (refhim=0)

Wed Jun  8 18:38:59 2022 daemon.debug xl2tpd[16465]: network_thread: unable to find call or tunnel to handle packet.  call = 34045, tunnel = 21788 Dumping.

Wed Jun  8 18:38:59 2022 daemon.info xl2tpd[16465]: Can not find tunnel 21788 (refhim=0)

Wed Jun  8 18:38:59 2022 daemon.debug xl2tpd[16465]: network_thread: unable to find call or tunnel to handle packet.  call = 34045, tunnel = 21788 Dumping.

Wed Jun  8 18:39:01 2022 daemon.info xl2tpd[16465]: Can not find tunnel 21788 (refhim=0)

Wed Jun  8 18:39:01 2022 daemon.debug xl2tpd[16465]: network_thread: unable to find call or tunnel to handle packet.  call = 34045, tunnel = 21788 Dumping.

Wed Jun  8 18:39:03 2022 daemon.info xl2tpd[16465]: Can not find tunnel 21788 (refhim=0)

Wed Jun  8 18:39:03 2022 daemon.debug xl2tpd[16465]: network_thread: unable to find call or tunnel to handle packet.  call = 34045, tunnel = 21788 Dumping.

Wed Jun  8 18:39:03 2022 daemon.info xl2tpd[16465]: Can not find tunnel 21788 (refhim=0)

Wed Jun  8 18:39:03 2022 daemon.debug xl2tpd[16465]: network_thread: unable to find call or tunnel to handle packet.  call = 34045, tunnel = 21788 Dumping.

Wed Jun  8 18:39:06 2022 daemon.debug xl2tpd[16465]: Unable to deliver closing message for tunnel 47757. Destroying anyway.

Wed Jun  8 18:39:06 2022 daemon.info xl2tpd[16465]: Can not find tunnel 21788 (refhim=0)

Wed Jun  8 18:39:06 2022 daemon.debug xl2tpd[16465]: network_thread: unable to find call or tunnel to handle packet.  call = 34045, tunnel = 21788 Dumping.

Wed Jun  8 18:39:07 2022 daemon.info xl2tpd[16465]: Can not find tunnel 21788 (refhim=0)

Wed Jun  8 18:39:07 2022 daemon.debug xl2tpd[16465]: network_thread: unable to find call or tunnel to handle packet.  call = 34045, tunnel = 21788 Dumping.

Wed Jun  8 18:39:09 2022 daemon.info xl2tpd[16465]: Can not find tunnel 21788 (refhim=0)

Wed Jun  8 18:39:09 2022 daemon.debug xl2tpd[16465]: network_thread: unable to find call or tunnel to handle packet.  call = 34045, tunnel = 21788 Dumping.

Wed Jun  8 18:39:11 2022 daemon.info xl2tpd[16465]: Can not find tunnel 21788 (refhim=0)

Wed Jun  8 18:39:11 2022 daemon.debug xl2tpd[16465]: network_thread: unable to find call or tunnel to handle packet.  call = 34045, tunnel = 21788 Dumping.

Wed Jun  8 18:39:11 2022 daemon.info xl2tpd[16465]: Can not find tunnel 21788 (refhim=0)

Wed Jun  8 18:39:11 2022 daemon.debug xl2tpd[16465]: network_thread: unable to find call or tunnel to handle packet.  call = 34045, tunnel = 21788 Dumping.

Wed Jun  8 18:39:13 2022 daemon.info xl2tpd[16465]: Can not find tunnel 21788 (refhim=0)

Wed Jun  8 18:39:13 2022 daemon.debug xl2tpd[16465]: network_thread: unable to find call or tunnel to handle packet.  call = 34045, tunnel = 21788 Dumping.

Wed Jun  8 18:39:17 2022 daemon.info xl2tpd[16465]: Disconnecting from 213.35.0.0, Local: 30587, Remote: 0

Wed Jun  8 18:39:17 2022 daemon.info xl2tpd[16465]: Connection 0 closed to 213.35.10.0, port 1701 (Goodbye!)

Wed Jun  8 18:39:17 2022 daemon.notice netifd: Interface 'johvi2' is now down

1 Answer

0 votes
by

Hello,

It would help if you could provide a picture with your network topology, device connections, IP addresses.

Also please check this configuration example. It is created on an older WebUI design, however, configurable settings should be smilar: https://wiki.teltonika-networks.com/view/L2TP_configuration_examples.

Next you can send me a troubleshoot file to view your configuration. To generate one, access router's WebUI, go to System -> Administration > Troubleshoot section and download troubleshoot file from there.

Best regards,

Žygimantas

by

i sent you a privatemessage troubleshoot file

i use same l2tp settings with another rut240 and rut950 (as client)
network topology is:

RUTx10 (l2tp server) - public ip 213.35.0.0, l2tp server ip 192.168.0.1, local ip 192.168.9.1, firmware RUTX_R_00.07.02.1

rut240 (l2tp works) - public ip dynamic, l2tp server ip 192.168.0.21. local ip 192.168.1.1 firmware RUT2_R_00.07.02 

rut 950 (l2tp wokrs) - public ip dynamic, l2tp server ip 192.168.0.20, local ip 192.168.8.1, firmware RUT9_R_00.07.02

rut240 (l2tp not works) - public ip dynamic, l2tp server ip must pe 192.168.0.24, local ip 192.168.10.1, firmware RUT2_R_00.07.02.1