Seit Jahren verbinde ich mich per Auto-Connect des Network Managers beim Rechnerstart zu einem VPN. Seit neulich geht das nicht mehr, ich muss nach dem Start manuell eine Verbidung zum VPN herstellen. Keinen Blassen, was sich (durch ein Update?) geändert hat.
Wo könnte ich denn nach dem Fehler suchen und diesen beheben?
Network Manager: Auto-connect to VPN
Re: Network Manager: Auto-connect to VPN
Mir 'journalctl' und dann nach passenden Stichworten grep'en und mit 'systemctl status' die Ausgaben der spezifischen Dienste prüfen.
Re: Network Manager: Auto-connect to VPN
Code: Alles auswählen
journalctl | grep Network
Sep 25 06:54:40 tardis NetworkManager[702]: <info> [1506315280.9320] manager: startup complete
Sep 25 06:54:40 tardis NetworkManager[702]: <info> [1506315280.9321] device (tun0): state change: disconnected -> prepare (reason 'none') [30 40 0]
Sep 25 06:54:40 tardis NetworkManager[702]: <info> [1506315280.9326] device (tun0): state change: prepare -> config (reason 'none') [40 50 0]
Sep 25 06:54:40 tardis NetworkManager[702]: <info> [1506315280.9329] device (tun0): state change: config -> ip-config (reason 'none') [50 70 0]
Sep 25 06:54:40 tardis NetworkManager[702]: <info> [1506315280.9336] device (tun0): state change: ip-config -> ip-check (reason 'none') [70 80 0]
Sep 25 06:54:40 tardis NetworkManager[702]: <info> [1506315280.9342] device (tun0): state change: ip-check -> secondaries (reason 'none') [80 90 0]
Sep 25 06:54:40 tardis NetworkManager[702]: <info> [1506315280.9345] device (tun0): state change: secondaries -> activated (reason 'none') [90 100 0]
Sep 25 06:54:40 tardis systemd[1]: Started Network Manager Wait Online.
Sep 25 06:54:40 tardis systemd[1]: Reached target Network is Online.
Sep 25 06:54:41 tardis NetworkManager[702]: <info> [1506315281.0642] manager: NetworkManager state is now CONNECTED_LOCAL
Sep 25 06:54:41 tardis NetworkManager[702]: <info> [1506315281.0644] manager: NetworkManager state is now CONNECTED_GLOBAL
Sep 25 06:54:41 tardis NetworkManager[702]: <info> [1506315281.0645] policy: set 'tun0' (tun0) as default for IPv4 routing and DNS
Sep 25 06:54:41 tardis NetworkManager[702]: <info> [1506315281.0648] device (tun0): Activation: successful, device activated.
Sep 25 07:03:17 tardis nm-openvpn[1057]: /usr/lib/NetworkManager/nm-openvpn-service-openvpn-helper --debug 0 1046 --bus-name org.freedesktop.NetworkManager.openvpn.Connection_2 --tun -- tun0 1500 1542 10.8.0.10 10.8.0.9 restart
Sep 25 07:03:17 tardis NetworkManager[702]: <error> [1506315797.2772] platform-linux: do-add-ip4-route[3: 0.0.0.0/0 50]: failure 101 (Network is unreachable)
Sep 25 07:03:17 tardis NetworkManager[702]: <warn> [1506315797.2773] default-route: failed to add default route 0.0.0.0/0 via 10.8.0.9 dev 3 metric 50 mss 0 src vpn with effective metric 50
Sep 25 07:03:17 tardis NetworkManager[702]: <info> [1506315797.2774] manager: NetworkManager state is now CONNECTED_LOCAL
Sep 25 07:03:17 tardis NetworkManager[702]: <info> [1506315797.2775] manager: NetworkManager state is now CONNECTED_GLOBAL
Sep 25 07:03:17 tardis NetworkManager[702]: <info> [1506315797.2775] policy: set 'Tardis VPN 2016' (tun0) as default for IPv4 routing and DNS
Sep 25 07:03:17 tardis NetworkManager[702]: <info> [1506315797.2780] device (tun0): state change: activated -> unmanaged (reason 'unmanaged') [100 10 3]
Sep 25 07:03:33 tardis NetworkManager[702]: <info> [1506315813.9917] devices removed (path: /sys/devices/virtual/net/tun0, iface: tun0)
Sep 25 07:03:33 tardis systemd[1]: Starting Network Manager Script Dispatcher Service...
Sep 25 07:03:34 tardis NetworkManager[702]: <warn> [1506315814.0007] vpn-connection[0x55dd11db8290,5429deee-4615-497a-90f3-c79549a382a3,"Tardis VPN 2016",3:(tun0)]: VPN plugin: failed: connect-failed (1)
Sep 25 07:03:34 tardis NetworkManager[702]: <info> [1506315814.0007] vpn-connection[0x55dd11db8290,5429deee-4615-497a-90f3-c79549a382a3,"Tardis VPN 2016",3:(tun0)]: VPN plugin: state changed: stopping (5)
Sep 25 07:03:34 tardis NetworkManager[702]: <info> [1506315814.0008] vpn-connection[0x55dd11db8290,5429deee-4615-497a-90f3-c79549a382a3,"Tardis VPN 2016",3:(tun0)]: VPN plugin: state changed: stopped (6)
Sep 25 07:03:34 tardis NetworkManager[702]: <info> [1506315814.0016] vpn-connection[0x55dd11db8290,5429deee-4615-497a-90f3-c79549a382a3,"Tardis VPN 2016",3:(tun0)]: VPN plugin: state change reason: unknown (0)
Sep 25 07:03:34 tardis NetworkManager[702]: <info> [1506315814.0016] manager: NetworkManager state is now CONNECTED_LOCAL
Sep 25 07:03:34 tardis systemd[1]: Started Network Manager Script Dispatcher Service.
Sep 25 07:03:34 tardis NetworkManager[702]: <info> [1506315814.2643] manager: NetworkManager state is now CONNECTED_GLOBAL
Sep 25 07:03:34 tardis NetworkManager[702]: <info> [1506315814.2669] vpn-connection[0x55dd11db8290,5429deee-4615-497a-90f3-c79549a382a3,"Tardis VPN 2016",0]: VPN service disappeared
Re: Network Manager: Auto-connect to VPN
Das ist eine Folge von "VPN plugin: failed: connect-failed (1)", siehe 8 Zeilen weiter oben im Log._ash hat geschrieben:25.09.2017 07:13:10"VPN service disappeared" - eine Idee, warum das passiert?
Re: Network Manager: Auto-connect to VPN
Wie könnte ich das beheben?
- Lord_Carlos
- Beiträge: 5578
- Registriert: 30.04.2006 17:58:52
- Lizenz eigener Beiträge: GNU Free Documentation License
- Wohnort: Dänemark
Re: Network Manager: Auto-connect to VPN
Kannst du dich noch manuell verbinden?
Code: Alles auswählen
╔═╗┬ ┬┌─┐┌┬┐┌─┐┌┬┐╔╦╗
╚═╗└┬┘└─┐ │ ├┤ │││ ║║
╚═╝ ┴ └─┘ ┴ └─┘┴ ┴═╩╝ rockt das Forum!
Re: Network Manager: Auto-connect to VPN
Jup, manuell ist kein Problem.