Автор Тема: Проблема с VPN L2TP подключением  (Прочитано 829 раз)

0 Пользователей и 1 Гость просматривают эту тему.

Оффлайн AlexTiger

  • Новичок
  • **
  • Автор темы
  • Сообщений: 24
Re: Проблема с VPN L2TP подключением
« Ответ #15 : Сентябрь 27, 2021, 13:50:06 »
HsH, ядро 5.4.0-77-generic
Пользователь. Интересно... Но один из DNS-адресов таки совпадает. Попробую вбить их вручную, расскажу что получится.

Оффлайн AlexTiger

  • Новичок
  • **
  • Автор темы
  • Сообщений: 24
Re: Проблема с VPN L2TP подключением
« Ответ #16 : Октябрь 11, 2021, 16:24:12 »
HsH, обновил ядро до 5.4.0-87-generic
Пользователь, Прописал ДНСки вручную в интерфейсе VPN

Понаблюдал. Всё по прежнему. То подключается сразу, то раза с 10-го...
Ниже два лога нерабочих подключений. Причем первый без ошибки рекурсии (?!)


Oct 11 15:12:02 home1 NetworkManager[793]: <info>  [1633954322.1818] audit: op="connection-activate" uuid="e410df79-5ea1-4a96-a7c3-1030fc38ebe8" name="Beeline" pid=1298 uid=1000 result="success"
Oct 11 15:12:02 home1 NetworkManager[793]: <info>  [1633954322.1860] vpn-connection[0x55822c502310,e410df79-5ea1-4a96-a7c3-1030fc38ebe8,"Beeline",0]: Started the VPN service, PID 1831
Oct 11 15:12:02 home1 NetworkManager[793]: <info>  [1633954322.1918] vpn-connection[0x55822c502310,e410df79-5ea1-4a96-a7c3-1030fc38ebe8,"Beeline",0]: Saw the service appear; activating connection
Oct 11 15:12:02 home1 NetworkManager[793]: <info>  [1633954322.1962] vpn-connection[0x55822c502310,e410df79-5ea1-4a96-a7c3-1030fc38ebe8,"Beeline",0]: VPN connection: (ConnectInteractive) reply received
Oct 11 15:12:02 home1 nm-l2tp-service[1831]: Check port 1701
Oct 11 15:12:02 home1 nm-l2tp-service[1831]: xl2tpd started with pid 1834
Oct 11 15:12:02 home1 NetworkManager[793]: xl2tpd[1834]: Not looking for kernel SAref support.
Oct 11 15:12:02 home1 NetworkManager[793]: xl2tpd[1834]: Using l2tp kernel support.
Oct 11 15:12:02 home1 NetworkManager[793]: xl2tpd[1834]: xl2tpd version xl2tpd-1.3.10 started on home1 PID:1834
Oct 11 15:12:02 home1 NetworkManager[793]: xl2tpd[1834]: Written by Mark Spencer, Copyright (C) 1998, Adtran, Inc.
Oct 11 15:12:02 home1 NetworkManager[793]: xl2tpd[1834]: Forked by Scott Balmos and David Stipp, (C) 2001
Oct 11 15:12:02 home1 NetworkManager[793]: xl2tpd[1834]: Inherited by Jeff McAdams, (C) 2002
Oct 11 15:12:02 home1 NetworkManager[793]: xl2tpd[1834]: Forked again by Xelerance (www.xelerance.com) (C) 2006-2016
Oct 11 15:12:02 home1 NetworkManager[793]: xl2tpd[1834]: Listening on IP address 0.0.0.0, port 1701
Oct 11 15:12:02 home1 NetworkManager[793]: xl2tpd[1834]: Connecting to host 78.107.181.4, port 1701
Oct 11 15:12:02 home1 NetworkManager[793]: <info>  [1633954322.2090] vpn-connection[0x55822c502310,e410df79-5ea1-4a96-a7c3-1030fc38ebe8,"Beeline",0]: VPN plugin: state changed: starting (3)
Oct 11 15:12:02 home1 NetworkManager[793]: xl2tpd[1834]: Connection established to 78.107.181.4, 1701.  Local: 13841, Remote: 15385 (ref=0/0).
Oct 11 15:12:02 home1 NetworkManager[793]: xl2tpd[1834]: Calling on tunnel 13841
Oct 11 15:12:02 home1 NetworkManager[793]: xl2tpd[1834]: Call established with 78.107.181.4, Local: 26001, Remote: 16875, Serial: 1 (ref=0/0)
Oct 11 15:12:02 home1 NetworkManager[793]: xl2tpd[1834]: start_pppd: I'm running:
Oct 11 15:12:02 home1 NetworkManager[793]: xl2tpd[1834]: "/usr/sbin/pppd"
Oct 11 15:12:02 home1 NetworkManager[793]: xl2tpd[1834]: "plugin"
Oct 11 15:12:02 home1 NetworkManager[793]: xl2tpd[1834]: "pppol2tp.so"
Oct 11 15:12:02 home1 NetworkManager[793]: xl2tpd[1834]: "pppol2tp"
Oct 11 15:12:02 home1 NetworkManager[793]: xl2tpd[1834]: "7"
Oct 11 15:12:02 home1 NetworkManager[793]: xl2tpd[1834]: "passive"
Oct 11 15:12:02 home1 NetworkManager[793]: xl2tpd[1834]: "nodetach"
Oct 11 15:12:02 home1 NetworkManager[793]: xl2tpd[1834]: ":"
Oct 11 15:12:02 home1 NetworkManager[793]: xl2tpd[1834]: "file"
Oct 11 15:12:02 home1 NetworkManager[793]: xl2tpd[1834]: "/var/run/nm-l2tp-ppp-options-e410df79-5ea1-4a96-a7c3-1030fc38ebe8"
Oct 11 15:12:02 home1 pppd[1835]: Plugin pppol2tp.so loaded.
Oct 11 15:12:02 home1 pppd[1835]: Plugin /usr/lib/pppd/2.4.7/nm-l2tp-pppd-plugin.so loaded.
Oct 11 15:12:02 home1 pppd[1835]: pppd 2.4.7 started by root, uid 0
Oct 11 15:12:02 home1 pppd[1835]: Using interface ppp0
Oct 11 15:12:02 home1 pppd[1835]: Connect: ppp0 <-->
Oct 11 15:12:02 home1 pppd[1835]: Overriding mtu 1500 to 1400
Oct 11 15:12:02 home1 pppd[1835]: Overriding mru 1500 to mtu value 1400
Oct 11 15:12:02 home1 NetworkManager[793]: <info>  [1633954322.2223] manager: (ppp0): new Ppp device (/org/freedesktop/NetworkManager/Devices/4)
Oct 11 15:12:02 home1 systemd-udevd[1838]: link_config: autonegotiation is unset or enabled, the speed and duplex are not writable.
Oct 11 15:12:02 home1 NetworkManager[793]: <info>  [1633954322.2314] devices added (path: /sys/devices/virtual/net/ppp0, iface: ppp0)
Oct 11 15:12:02 home1 NetworkManager[793]: <info>  [1633954322.2314] device added (path: /sys/devices/virtual/net/ppp0, iface: ppp0): no ifupdown configuration found.
Oct 11 15:12:02 home1 pppd[1835]: Overriding mtu 1460 to 1400
Oct 11 15:12:02 home1 pppd[1835]: CHAP authentication succeeded: CHAP authentication success
Oct 11 15:12:02 home1 pppd[1835]: CHAP authentication succeeded
Oct 11 15:12:02 home1 charon: 08[KNL] 100.126.121.173 appeared on ppp0
Oct 11 15:12:02 home1 pppd[1835]: local  IP address 100.126.121.173
Oct 11 15:12:02 home1 pppd[1835]: remote IP address 100.126.0.1
Oct 11 15:12:02 home1 charon: 10[KNL] 100.126.121.173 disappeared from ppp0
Oct 11 15:12:02 home1 NetworkManager[793]: <info>  [1633954322.2832] device (ppp0): state change: unmanaged -> unavailable (reason 'connection-assumed', sys-iface-state: 'external')
Oct 11 15:12:02 home1 charon: 12[KNL] 100.126.121.173 appeared on ppp0
Oct 11 15:12:02 home1 NetworkManager[793]: <info>  [1633954322.2871] vpn-connection[0x55822c502310,e410df79-5ea1-4a96-a7c3-1030fc38ebe8,"Beeline",0]: VPN connection: (IP4 Config Get) reply received from old-style plugin
Oct 11 15:12:02 home1 charon: 14[KNL] interface ppp0 activated
Oct 11 15:12:02 home1 NetworkManager[793]: <info>  [1633954322.2882] vpn-connection[0x55822c502310,e410df79-5ea1-4a96-a7c3-1030fc38ebe8,"Beeline",4:(ppp0)]: Data: VPN Gateway: 78.107.181.4
Oct 11 15:12:02 home1 NetworkManager[793]: <info>  [1633954322.2882] vpn-connection[0x55822c502310,e410df79-5ea1-4a96-a7c3-1030fc38ebe8,"Beeline",4:(ppp0)]: Data: Tunnel Device: "ppp0"
Oct 11 15:12:02 home1 NetworkManager[793]: <info>  [1633954322.2882] vpn-connection[0x55822c502310,e410df79-5ea1-4a96-a7c3-1030fc38ebe8,"Beeline",4:(ppp0)]: Data: IPv4 configuration:
Oct 11 15:12:02 home1 NetworkManager[793]: <info>  [1633954322.2882] vpn-connection[0x55822c502310,e410df79-5ea1-4a96-a7c3-1030fc38ebe8,"Beeline",4:(ppp0)]: Data:   Internal Address: 100.126.121.173
Oct 11 15:12:02 home1 NetworkManager[793]: <info>  [1633954322.2883] vpn-connection[0x55822c502310,e410df79-5ea1-4a96-a7c3-1030fc38ebe8,"Beeline",4:(ppp0)]: Data:   Internal Prefix: 32
Oct 11 15:12:02 home1 NetworkManager[793]: <info>  [1633954322.2883] vpn-connection[0x55822c502310,e410df79-5ea1-4a96-a7c3-1030fc38ebe8,"Beeline",4:(ppp0)]: Data:   Internal Point-to-Point Address: 100.126.0.1
Oct 11 15:12:02 home1 NetworkManager[793]: <info>  [1633954322.2883] vpn-connection[0x55822c502310,e410df79-5ea1-4a96-a7c3-1030fc38ebe8,"Beeline",4:(ppp0)]: Data:   Static Route: 0.0.0.0/0   Next Hop: 0.0.0.0
Oct 11 15:12:02 home1 NetworkManager[793]: <info>  [1633954322.2883] vpn-connection[0x55822c502310,e410df79-5ea1-4a96-a7c3-1030fc38ebe8,"Beeline",4:(ppp0)]: Data:   Static Route: 100.126.0.1/32   Next Hop: 0.0.0.0
Oct 11 15:12:02 home1 NetworkManager[793]: <info>  [1633954322.2883] vpn-connection[0x55822c502310,e410df79-5ea1-4a96-a7c3-1030fc38ebe8,"Beeline",4:(ppp0)]: Data:   Internal DNS: 85.21.192.3
Oct 11 15:12:02 home1 NetworkManager[793]: <info>  [1633954322.2884] vpn-connection[0x55822c502310,e410df79-5ea1-4a96-a7c3-1030fc38ebe8,"Beeline",4:(ppp0)]: Data:   Internal DNS: 213.234.192.8
Oct 11 15:12:02 home1 NetworkManager[793]: <info>  [1633954322.2884] vpn-connection[0x55822c502310,e410df79-5ea1-4a96-a7c3-1030fc38ebe8,"Beeline",4:(ppp0)]: Data:   DNS Domain: '(none)'
Oct 11 15:12:02 home1 NetworkManager[793]: <info>  [1633954322.2884] vpn-connection[0x55822c502310,e410df79-5ea1-4a96-a7c3-1030fc38ebe8,"Beeline",4:(ppp0)]: Data: No IPv6 configuration
Oct 11 15:12:02 home1 NetworkManager[793]: <info>  [1633954322.2884] vpn-connection[0x55822c502310,e410df79-5ea1-4a96-a7c3-1030fc38ebe8,"Beeline",4:(ppp0)]: VPN plugin: state changed: started (4)
Oct 11 15:12:02 home1 NetworkManager[793]: <info>  [1633954322.2886] device (ppp0): state change: unavailable -> disconnected (reason 'none', sys-iface-state: 'external')
Oct 11 15:12:02 home1 NetworkManager[793]: <info>  [1633954322.2901] vpn-connection[0x55822c502310,e410df79-5ea1-4a96-a7c3-1030fc38ebe8,"Beeline",4:(ppp0)]: VPN connection: (IP Config Get) complete
Oct 11 15:12:02 home1 dbus-daemon[746]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service' requested by ':1.9' (uid=0 pid=793 comm="/usr/sbin/NetworkManager --no-daemon " label="unconfined")
Oct 11 15:12:02 home1 systemd[1]: Starting Network Manager Script Dispatcher Service...
Oct 11 15:12:02 home1 dbus-daemon[746]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher'
Oct 11 15:12:02 home1 systemd[1]: Started Network Manager Script Dispatcher Service.
Oct 11 15:12:02 home1 nm-dispatcher: req:1 'vpn-up' [ppp0]: new request (1 scripts)
Oct 11 15:12:02 home1 nm-dispatcher: req:1 'vpn-up' [ppp0]: start running ordered scripts...
Oct 11 15:12:23 home1 kernel: [  185.750136] [UFW BLOCK] IN=enp3s0 OUT= MAC=#### SRC=10.124.236.77 DST=224.0.0.1 LEN=32 TOS=0x00 PREC=0xC0 TTL=1 ID=62588 PROTO=2
Oct 11 15:12:24 home1 kernel: [  187.590209] [UFW BLOCK] IN= OUT=ppp0 SRC=100.126.121.173 DST=91.189.94.4 LEN=76 TOS=0x10 PREC=0x00 TTL=64 ID=58596 DF PROTO=UDP SPT=60925 DPT=123 LEN=56
Oct 11 15:12:24 home1 kernel: [  187.590491] [UFW BLOCK] IN= OUT=ppp0 SRC=100.126.121.173 DST=91.189.91.157 LEN=76 TOS=0x10 PREC=0x00 TTL=64 ID=18455 DF PROTO=UDP SPT=40098 DPT=123 LEN=56
Oct 11 15:12:24 home1 kernel: [  187.590754] [UFW BLOCK] IN= OUT=ppp0 SRC=100.126.121.173 DST=91.189.89.198 LEN=76 TOS=0x10 PREC=0x00 TTL=64 ID=26511 DF PROTO=UDP SPT=50645 DPT=123 LEN=56
Oct 11 15:12:24 home1 kernel: [  187.591161] [UFW BLOCK] IN= OUT=ppp0 SRC=100.126.121.173 DST=91.189.89.199 LEN=76 TOS=0x10 PREC=0x00 TTL=64 ID=31474 DF PROTO=UDP SPT=55622 DPT=123 LEN=56


Oct 11 16:05:01 home1 NetworkManager[793]: <info>  [1633957501.8216] audit: op="connection-activate" uuid="e410df79-5ea1-4a96-a7c3-1030fc38ebe8" name="Beeline" pid=1298 uid=1000 result="success"
Oct 11 16:05:01 home1 NetworkManager[793]: <info>  [1633957501.8262] vpn-connection[0x55822c502110,e410df79-5ea1-4a96-a7c3-1030fc38ebe8,"Beeline",0]: Started the VPN service, PID 2645
Oct 11 16:05:01 home1 NetworkManager[793]: <info>  [1633957501.8335] vpn-connection[0x55822c502110,e410df79-5ea1-4a96-a7c3-1030fc38ebe8,"Beeline",0]: Saw the service appear; activating connection
Oct 11 16:05:01 home1 NetworkManager[793]: <info>  [1633957501.8404] vpn-connection[0x55822c502110,e410df79-5ea1-4a96-a7c3-1030fc38ebe8,"Beeline",0]: VPN connection: (ConnectInteractive) reply received
Oct 11 16:05:01 home1 nm-l2tp-service[2645]: Check port 1701
Oct 11 16:05:01 home1 nm-l2tp-service[2645]: xl2tpd started with pid 2648
Oct 11 16:05:01 home1 NetworkManager[793]: xl2tpd[2648]: Not looking for kernel SAref support.
Oct 11 16:05:01 home1 NetworkManager[793]: xl2tpd[2648]: Using l2tp kernel support.
Oct 11 16:05:01 home1 NetworkManager[793]: xl2tpd[2648]: xl2tpd version xl2tpd-1.3.10 started on home1 PID:2648
Oct 11 16:05:01 home1 NetworkManager[793]: xl2tpd[2648]: Written by Mark Spencer, Copyright (C) 1998, Adtran, Inc.
Oct 11 16:05:01 home1 NetworkManager[793]: xl2tpd[2648]: Forked by Scott Balmos and David Stipp, (C) 2001
Oct 11 16:05:01 home1 NetworkManager[793]: xl2tpd[2648]: Inherited by Jeff McAdams, (C) 2002
Oct 11 16:05:01 home1 NetworkManager[793]: xl2tpd[2648]: Forked again by Xelerance (www.xelerance.com) (C) 2006-2016
Oct 11 16:05:01 home1 NetworkManager[793]: xl2tpd[2648]: Listening on IP address 0.0.0.0, port 1701
Oct 11 16:05:01 home1 NetworkManager[793]: xl2tpd[2648]: Connecting to host 85.21.129.81, port 1701
Oct 11 16:05:01 home1 NetworkManager[793]: <info>  [1633957501.8546] vpn-connection[0x55822c502110,e410df79-5ea1-4a96-a7c3-1030fc38ebe8,"Beeline",0]: VPN plugin: state changed: starting (3)
Oct 11 16:05:01 home1 NetworkManager[793]: xl2tpd[2648]: Connection established to 85.21.129.81, 1701.  Local: 44826, Remote: 39898 (ref=0/0).
Oct 11 16:05:01 home1 NetworkManager[793]: xl2tpd[2648]: Calling on tunnel 44826
Oct 11 16:05:01 home1 NetworkManager[793]: xl2tpd[2648]: Call established with 85.21.129.81, Local: 4132, Remote: 50754, Serial: 1 (ref=0/0)
Oct 11 16:05:01 home1 NetworkManager[793]: xl2tpd[2648]: start_pppd: I'm running:
Oct 11 16:05:01 home1 NetworkManager[793]: xl2tpd[2648]: "/usr/sbin/pppd"
Oct 11 16:05:01 home1 NetworkManager[793]: xl2tpd[2648]: "plugin"
Oct 11 16:05:01 home1 NetworkManager[793]: xl2tpd[2648]: "pppol2tp.so"
Oct 11 16:05:01 home1 NetworkManager[793]: xl2tpd[2648]: "pppol2tp"
Oct 11 16:05:01 home1 NetworkManager[793]: xl2tpd[2648]: "7"
Oct 11 16:05:01 home1 NetworkManager[793]: xl2tpd[2648]: "passive"
Oct 11 16:05:01 home1 NetworkManager[793]: xl2tpd[2648]: "nodetach"
Oct 11 16:05:01 home1 NetworkManager[793]: xl2tpd[2648]: ":"
Oct 11 16:05:01 home1 NetworkManager[793]: xl2tpd[2648]: "file"
Oct 11 16:05:01 home1 NetworkManager[793]: xl2tpd[2648]: "/var/run/nm-l2tp-ppp-options-e410df79-5ea1-4a96-a7c3-1030fc38ebe8"
Oct 11 16:05:01 home1 pppd[2649]: Plugin pppol2tp.so loaded.
Oct 11 16:05:01 home1 pppd[2649]: Plugin /usr/lib/pppd/2.4.7/nm-l2tp-pppd-plugin.so loaded.
Oct 11 16:05:01 home1 pppd[2649]: pppd 2.4.7 started by root, uid 0
Oct 11 16:05:01 home1 pppd[2649]: Using interface ppp0
Oct 11 16:05:01 home1 pppd[2649]: Connect: ppp0 <-->
Oct 11 16:05:01 home1 pppd[2649]: Overriding mtu 1500 to 1400
Oct 11 16:05:01 home1 pppd[2649]: Overriding mru 1500 to mtu value 1400
Oct 11 16:05:01 home1 systemd-udevd[2652]: link_config: autonegotiation is unset or enabled, the speed and duplex are not writable.
Oct 11 16:05:01 home1 NetworkManager[793]: <info>  [1633957501.8669] manager: (ppp0): new Ppp device (/org/freedesktop/NetworkManager/Devices/10)
Oct 11 16:05:01 home1 pppd[2649]: Overriding mtu 1460 to 1400
Oct 11 16:05:01 home1 pppd[2649]: Overriding mru 1460 to mtu value 1400
Oct 11 16:05:01 home1 NetworkManager[793]: <info>  [1633957501.8762] devices added (path: /sys/devices/virtual/net/ppp0, iface: ppp0)
Oct 11 16:05:01 home1 NetworkManager[793]: <info>  [1633957501.8762] device added (path: /sys/devices/virtual/net/ppp0, iface: ppp0): no ifupdown configuration found.
Oct 11 16:05:01 home1 pppd[2649]: CHAP authentication succeeded
Oct 11 16:05:01 home1 pppd[2649]: CHAP authentication succeeded
Oct 11 16:05:01 home1 charon: 06[KNL] 10.16.127.132 appeared on ppp0
Oct 11 16:05:01 home1 pppd[2649]: local  IP address 10.16.127.132
Oct 11 16:05:01 home1 NetworkManager[793]: <info>  [1633957501.9363] device (ppp0): state change: unmanaged -> unavailable (reason 'connection-assumed', sys-iface-state: 'external')
Oct 11 16:05:01 home1 pppd[2649]: remote IP address 85.21.129.81
Oct 11 16:05:01 home1 charon: 07[KNL] 10.16.127.132 disappeared from ppp0
Oct 11 16:05:01 home1 charon: 05[KNL] 10.16.127.132 appeared on ppp0
Oct 11 16:05:01 home1 charon: 10[KNL] interface ppp0 activated
Oct 11 16:05:01 home1 NetworkManager[793]: <info>  [1633957501.9409] vpn-connection[0x55822c502110,e410df79-5ea1-4a96-a7c3-1030fc38ebe8,"Beeline",0]: VPN connection: (IP4 Config Get) reply received from old-style plugin
Oct 11 16:05:01 home1 NetworkManager[793]: <info>  [1633957501.9428] vpn-connection[0x55822c502110,e410df79-5ea1-4a96-a7c3-1030fc38ebe8,"Beeline",10:(ppp0)]: Data: VPN Gateway: 85.21.129.81
Oct 11 16:05:01 home1 NetworkManager[793]: <info>  [1633957501.9429] vpn-connection[0x55822c502110,e410df79-5ea1-4a96-a7c3-1030fc38ebe8,"Beeline",10:(ppp0)]: Data: Tunnel Device: "ppp0"
Oct 11 16:05:01 home1 NetworkManager[793]: <info>  [1633957501.9430] vpn-connection[0x55822c502110,e410df79-5ea1-4a96-a7c3-1030fc38ebe8,"Beeline",10:(ppp0)]: Data: IPv4 configuration:
Oct 11 16:05:01 home1 NetworkManager[793]: <info>  [1633957501.9431] vpn-connection[0x55822c502110,e410df79-5ea1-4a96-a7c3-1030fc38ebe8,"Beeline",10:(ppp0)]: Data:   Internal Address: 10.16.127.132
Oct 11 16:05:01 home1 NetworkManager[793]: <info>  [1633957501.9431] vpn-connection[0x55822c502110,e410df79-5ea1-4a96-a7c3-1030fc38ebe8,"Beeline",10:(ppp0)]: Data:   Internal Prefix: 32
Oct 11 16:05:01 home1 NetworkManager[793]: <info>  [1633957501.9431] vpn-connection[0x55822c502110,e410df79-5ea1-4a96-a7c3-1030fc38ebe8,"Beeline",10:(ppp0)]: Data:   Internal Point-to-Point Address: 85.21.129.81
Oct 11 16:05:01 home1 NetworkManager[793]: <info>  [1633957501.9432] vpn-connection[0x55822c502110,e410df79-5ea1-4a96-a7c3-1030fc38ebe8,"Beeline",10:(ppp0)]: Data:   Static Route: 0.0.0.0/0   Next Hop: 0.0.0.0
Oct 11 16:05:01 home1 NetworkManager[793]: <info>  [1633957501.9432] vpn-connection[0x55822c502110,e410df79-5ea1-4a96-a7c3-1030fc38ebe8,"Beeline",10:(ppp0)]: Data:   Static Route: 85.21.129.81/32   Next Hop: 0.0.0.0
Oct 11 16:05:01 home1 NetworkManager[793]: <info>  [1633957501.9433] vpn-connection[0x55822c502110,e410df79-5ea1-4a96-a7c3-1030fc38ebe8,"Beeline",10:(ppp0)]: Data:   Internal DNS: 85.21.192.3
Oct 11 16:05:01 home1 NetworkManager[793]: <info>  [1633957501.9433] vpn-connection[0x55822c502110,e410df79-5ea1-4a96-a7c3-1030fc38ebe8,"Beeline",10:(ppp0)]: Data:   Internal DNS: 213.234.192.8
Oct 11 16:05:01 home1 NetworkManager[793]: <info>  [1633957501.9434] vpn-connection[0x55822c502110,e410df79-5ea1-4a96-a7c3-1030fc38ebe8,"Beeline",10:(ppp0)]: Data:   DNS Domain: '(none)'
Oct 11 16:05:01 home1 NetworkManager[793]: <info>  [1633957501.9434] vpn-connection[0x55822c502110,e410df79-5ea1-4a96-a7c3-1030fc38ebe8,"Beeline",10:(ppp0)]: Data: No IPv6 configuration
Oct 11 16:05:01 home1 NetworkManager[793]: <info>  [1633957501.9436] vpn-connection[0x55822c502110,e410df79-5ea1-4a96-a7c3-1030fc38ebe8,"Beeline",10:(ppp0)]: VPN plugin: state changed: started (4)
Oct 11 16:05:01 home1 NetworkManager[793]: <info>  [1633957501.9464] vpn-connection[0x55822c502110,e410df79-5ea1-4a96-a7c3-1030fc38ebe8,"Beeline",10:(ppp0)]: VPN connection: (IP Config Get) complete
Oct 11 16:05:01 home1 NetworkManager[793]: <info>  [1633957501.9468] device (ppp0): state change: unavailable -> disconnected (reason 'none', sys-iface-state: 'external')
Oct 11 16:05:01 home1 dbus-daemon[746]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service' requested by ':1.9' (uid=0 pid=793 comm="/usr/sbin/NetworkManager --no-daemon " label="unconfined")
Oct 11 16:05:01 home1 systemd[1]: Starting Network Manager Script Dispatcher Service...
Oct 11 16:05:01 home1 dbus-daemon[746]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher'
Oct 11 16:05:01 home1 systemd[1]: Started Network Manager Script Dispatcher Service.
Oct 11 16:05:01 home1 nm-dispatcher: req:1 'vpn-up' [ppp0]: new request (1 scripts)
Oct 11 16:05:01 home1 nm-dispatcher: req:1 'vpn-up' [ppp0]: start running ordered scripts...
Oct 11 16:05:04 home1 systemd-resolved[741]: Using degraded feature set (UDP) for DNS server 85.21.192.3.
Oct 11 16:05:08 home1 systemd-resolved[741]: Using degraded feature set (UDP) for DNS server 213.234.192.8.
Oct 11 16:05:11 home1 systemd-resolved[741]: Using degraded feature set (TCP) for DNS server 85.21.192.3.
Oct 11 16:05:11 home1 kernel: [ 3354.523071] ppp0: recursion detected
Oct 11 16:05:17 home1 systemd-resolved[741]: Using degraded feature set (TCP) for DNS server 213.234.192.8.
Oct 11 16:05:21 home1 kernel: [ 3364.539203] ppp0: recursion detected
Oct 11 16:05:31 home1 kernel: [ 3374.554671] ppp0: recursion detected
Oct 11 16:05:32 home1 systemd-resolved[741]: Using degraded feature set (UDP) for DNS server 85.21.192.3.

Оффлайн Пользователь.

  • Местный
  • *****
  • Сообщений: 4264
Re: Проблема с VPN L2TP подключением
« Ответ #17 : Октябрь 11, 2021, 18:39:38 »
Раз ручная правка DNS не помогла, значит дело не в этом.

Осталось бороться с рекурсией, я в этом не разбираюсь.

Оффлайн AlexTiger

  • Новичок
  • **
  • Автор темы
  • Сообщений: 24
Re: Проблема с VPN L2TP подключением
« Ответ #18 : Октябрь 17, 2021, 01:16:43 »
HsH, мистика какая-то  ::)
Всё заработало, если полностью отключить l2tp и пересоздать Ethernet.
То есть заработало на чистом Ethernet, вопреки инструкциям провайдера.
Это глюк или фича?!  :o

Оффлайн HsH

  • Administrator
  • *****
  • Сообщений: 2983
Re: Проблема с VPN L2TP подключением
« Ответ #19 : Октябрь 18, 2021, 12:26:18 »
HsH, обновил ядро до 5.4.0-87-generic
Имелось ввиду обновление не внутри одной версии, а на другой релиз (например, 5.11 и т.п.).

Всё заработало, если полностью отключить l2tp и пересоздать Ethernet. То есть заработало на чистом Ethernet, вопреки инструкциям провайдера.
Не всегда провайдер держит в актуальном состоянии свои инструкции, особенно если пользователь получает услугу относительно продолжительное время. Чаще всего настройки производит сотрудник провайдера, который в курсе текущих протоколов,  пользователь этим "не заморачивается".
Для верности конечно стоит уточнить у компетентных сотрудников поддержки, как именно организован доступ в вашей локации.

Оффлайн AlexTiger

  • Новичок
  • **
  • Автор темы
  • Сообщений: 24
Re: Проблема с VPN L2TP подключением
« Ответ #20 : Октябрь 18, 2021, 15:01:59 »
HsH, на сайте еще старая инструкция. Но недавно потребовали авторизацию через браузер и запомнили (IPoE?). С l2tp теперь Линукса не пускает. Но голый ethernet это же небезопасно?!

Но появилась новая проблема. Теперь вдруг отваливается IP-адрес на минуту. Потом восстанавливается, такой же. Но вся связь рушится. В логе перед обрывом куча сообщений от dhcp. После восстановления пишет, что был таймаут dhcp 45 секунд.
Что бы это значило?

Oct 18 14:29:43 home1 dhclient[8523]: DHCPREQUEST of 100.125.20.208 on enp3s0 to 100.125.0.1 port 67 (xid=0x2ae3c1fa)
Oct 18 14:29:43 home1 dhclient[8523]: send_packet: Operation not permitted
Oct 18 14:29:43 home1 dhclient[8523]: dhclient.c:2743: Failed to send 300 byte long packet over fallback interface.
Oct 18 14:29:43 home1 kernel: [11310.455232] [UFW BLOCK] IN= OUT=enp3s0 SRC=100.125.20.208 DST=100.125.0.1 LEN=328 TOS=0x00 PREC=0x00 TTL=64 ID=50735 DF PROTO=UDP SPT=68 DPT=67 LEN=308
Oct 18 14:29:58 home1 kernel: [11324.873856] [UFW BLOCK] IN=enp3s0 OUT= MAC=######## SRC=10.124.236.77 DST=224.0.0.1 LEN=32 TOS=0x00 PREC=0xC0 TTL=1 ID=48924 PROTO=2
Oct 18 14:30:02 home1 dhclient[8523]: DHCPREQUEST of 100.125.20.208 on enp3s0 to 100.125.0.1 port 67 (xid=0x2ae3c1fa)
Oct 18 14:30:02 home1 dhclient[8523]: send_packet: Operation not permitted
Oct 18 14:30:02 home1 dhclient[8523]: dhclient.c:2743: Failed to send 300 byte long packet over fallback interface.
Oct 18 14:30:02 home1 kernel: [11328.827180] [UFW BLOCK] IN= OUT=enp3s0 SRC=100.125.20.208 DST=100.125.0.1 LEN=328 TOS=0x00 PREC=0x00 TTL=64 ID=52810 DF PROTO=UDP SPT=68 DPT=67 LEN=308
Oct 18 14:30:19 home1 dhclient[8523]: DHCPREQUEST of 100.125.20.208 on enp3s0 to 100.125.0.1 port 67 (xid=0x2ae3c1fa)
Oct 18 14:30:19 home1 dhclient[8523]: send_packet: Operation not permitted
Oct 18 14:30:19 home1 dhclient[8523]: dhclient.c:2743: Failed to send 300 byte long packet over fallback interface.
Oct 18 14:30:19 home1 kernel: [11345.711188] [UFW BLOCK] IN= OUT=enp3s0 SRC=100.125.20.208 DST=100.125.0.1 LEN=328 TOS=0x00 PREC=0x00 TTL=64 ID=54991 DF PROTO=UDP SPT=68 DPT=67 LEN=308
Oct 18 14:30:36 home1 dhclient[8523]: DHCPREQUEST of 100.125.20.208 on enp3s0 to 100.125.0.1 port 67 (xid=0x2ae3c1fa)
Oct 18 14:30:36 home1 dhclient[8523]: send_packet: Operation not permitted
Oct 18 14:30:36 home1 dhclient[8523]: dhclient.c:2743: Failed to send 300 byte long packet over fallback interface.
Oct 18 14:30:36 home1 kernel: [11363.363208] [UFW BLOCK] IN= OUT=enp3s0 SRC=100.125.20.208 DST=100.125.0.1 LEN=328 TOS=0x00 PREC=0x00 TTL=64 ID=57138 DF PROTO=UDP SPT=68 DPT=67 LEN=308
Oct 18 14:30:47 home1 dhclient[8523]: DHCPREQUEST of 100.125.20.208 on enp3s0 to 100.125.0.1 port 67 (xid=0x2ae3c1fa)
Oct 18 14:30:47 home1 dhclient[8523]: send_packet: Operation not permitted
Oct 18 14:30:47 home1 dhclient[8523]: dhclient.c:2743: Failed to send 300 byte long packet over fallback interface.
Oct 18 14:30:47 home1 kernel: [11374.431201] [UFW BLOCK] IN= OUT=enp3s0 SRC=100.125.20.208 DST=100.125.0.1 LEN=328 TOS=0x00 PREC=0x00 TTL=64 ID=57782 DF PROTO=UDP SPT=68 DPT=67 LEN=308
Oct 18 14:31:01 home1 dhclient[8523]: DHCPREQUEST of 100.125.20.208 on enp3s0 to 255.255.255.255 port 67 (xid=0x2ae3c1fa)
Oct 18 14:31:13 home1 kernel: [11399.903065] [UFW BLOCK] IN= OUT=enp3s0 SRC=100.125.20.208 DST=216.58.209.161 LEN=1385 TOS=0x00 PREC=0x00 TTL=64 ID=0 DF PROTO=UDP SPT=49012 DPT=443 LEN=1365
Oct 18 14:31:13 home1 kernel: [11399.972612] [UFW BLOCK] IN= OUT=enp3s0 SRC=100.125.20.208 DST=173.194.176.159 LEN=1385 TOS=0x00 PREC=0x00 TTL=64 ID=0 DF PROTO=UDP SPT=45146 DPT=443 LEN=1365
Oct 18 14:31:14 home1 kernel: [11400.969790] [UFW BLOCK] IN= OUT=enp3s0 SRC=100.125.20.208 DST=216.58.210.130 LEN=1385 TOS=0x00 PREC=0x00 TTL=64 ID=0 DF PROTO=UDP SPT=41797 DPT=443 LEN=1365
Oct 18 14:31:23 home1 kernel: [11410.231808] [UFW BLOCK] IN= OUT=enp3s0 SRC=100.125.20.208 DST=216.58.210.130 LEN=1385 TOS=0x00 PREC=0x00 TTL=64 ID=0 DF PROTO=UDP SPT=35239 DPT=443 LEN=1365
Oct 18 14:32:03 home1 kernel: [11449.872924] [UFW BLOCK] IN=enp3s0 OUT= MAC=################## SRC=10.124.236.77 DST=224.0.0.1 LEN=32 TOS=0x00 PREC=0xC0 TTL=1 ID=49138 PROTO=2
Oct 18 14:31:59 home1 dhclient[8523]: message repeated 4 times: [ DHCPREQUEST of 100.125.20.208 on enp3s0 to 255.255.255.255 port 67 (xid=0x2ae3c1fa)]
Oct 18 14:32:07 home1 charon: 07[KNL] 100.125.20.208 disappeared from enp3s0
Oct 18 14:32:07 home1 NetworkManager[774]: <info>  [1634556727.6722] manager: NetworkManager state is now CONNECTED_SITE
Oct 18 14:32:07 home1 dbus-daemon[738]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service' requested by ':1.11' (uid=0 pid=774 comm="/usr/sbin/NetworkManager --no-daemon " label="unconfined")
Oct 18 14:32:07 home1 systemd[1]: Starting Network Manager Script Dispatcher Service...
Oct 18 14:32:07 home1 dbus-daemon[738]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher'
Oct 18 14:32:07 home1 systemd[1]: Started Network Manager Script Dispatcher Service.
Oct 18 14:32:07 home1 nm-dispatcher: req:1 'connectivity-change': new request (1 scripts)
Oct 18 14:32:07 home1 nm-dispatcher: req:1 'connectivity-change': start running ordered scripts...
Oct 18 14:32:08 home1 NetworkManager[774]: <info>  [1634556728.3947] dhcp4 (enp3s0): state changed bound -> expire
Oct 18 14:32:08 home1 NetworkManager[774]: <info>  [1634556728.4272] dhcp4 (enp3s0): canceled DHCP transaction, DHCP client pid 8523
Oct 18 14:32:08 home1 NetworkManager[774]: <info>  [1634556728.4272] dhcp4 (enp3s0): state changed expire -> done
Oct 18 14:32:08 home1 NetworkManager[774]: <info>  [1634556728.4278] device (enp3s0): scheduling DHCPv4 restart in 120 seconds, 3 tries left (reason: lease expired)

Oct 18 14:34:08 home1 NetworkManager[774]: <info>  [1634556848.5236] dhcp4 (enp3s0): activation: beginning transaction (timeout in 45 seconds)
Oct 18 14:34:08 home1 NetworkManager[774]: <info>  [1634556848.5267] dhcp4 (enp3s0): dhclient started with pid 8756

« Последнее редактирование: Октябрь 19, 2021, 05:21:19 от AlexTiger »

Оффлайн AlexTiger

  • Новичок
  • **
  • Автор темы
  • Сообщений: 24
Re: Проблема с VPN L2TP подключением
« Ответ #21 : Октябрь 19, 2021, 02:11:38 »
Надоело мучиться - поставил таки роутер  8)
И он-то на l2tp спокойно работает
« Последнее редактирование: Октябрь 19, 2021, 05:22:11 от AlexTiger »

Оффлайн HsH

  • Administrator
  • *****
  • Сообщений: 2983
Re: Проблема с VPN L2TP подключением
« Ответ #22 : Октябрь 20, 2021, 10:21:04 »
Роутер - оптимальное решение для обеспечения интернетом домашней сети.