GNOME Bugzilla – Bug 739244
network-manager breaks ptp tun interfaces
Last modified: 2014-10-27 21:01:23 UTC
Version: 0.9.10.0-3 Bug-Debian: https://bugs.debian.org/767002 As reported downstream: Hi, I start a couple tun devices outside of network manager using openvpn. For instance: } 88: tun-n2-axon: <POINTOPOINT,MULTICAST,NOARP,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UNKNOWN group default qlen 100 } link/none } inet 172.22.126.18 peer 172.22.126.21/32 scope global tun-n2-axon } valid_lft forever preferred_lft forever If network manager is runningm the configuration of that device is changed to: } 88: tun-n2-axon: <POINTOPOINT,MULTICAST,NOARP,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UNKNOWN group default qlen 100 } link/none } inet 172.22.126.18 peer 172.22.126.21/32 scope global tun-n2-axon } valid_lft forever preferred_lft forever } inet 172.22.126.18/32 brd 172.22.126.18 scope global tun-n2-axon } valid_lft forever preferred_lft forever Adding ] [keyfile] ] unmanaged-devices=interface-name:tun-n2-axon prevents that, but that "solution" is really sub-optimal (I have many such devices, and they change etc.Timeout, server anguilla.debian.or.at not responding. We discussed this briefly on IRC, and it might be caused by the connection assume feature. weasel@defiant:~$ logread | grep -i netw | grep -i axon Oct 27 14:59:42 defiant daemon.info NetworkManager[21335]: <info> devices added (path: /sys/devices/virtual/net/tun-n2-axon, iface: tun-n2-axon) Oct 27 14:59:42 defiant daemon.info NetworkManager[21335]: <info> device added (path: /sys/devices/virtual/net/tun-n2-axon, iface: tun-n2-axon): no ifupdown configuration found. Oct 27 14:59:42 defiant daemon.info NetworkManager[21335]: <info> (tun-n2-axon): link connected Oct 27 14:59:42 defiant daemon.info NetworkManager[21335]: <info> (tun-n2-axon): carrier is ON Oct 27 14:59:42 defiant daemon.info NetworkManager[21335]: <info> (tun-n2-axon): new Tun device (driver: 'tun' ifindex: 73) Oct 27 14:59:42 defiant daemon.info NetworkManager[21335]: <info> (tun-n2-axon): exported as /org/freedesktop/NetworkManager/Devices/6 Oct 27 14:59:42 defiant daemon.info NetworkManager[21335]: <info> (tun-n2-axon): device state change: unmanaged -> unavailable (reason 'connection-assumed') [10 20 41] Oct 27 14:59:42 defiant daemon.info NetworkManager[21335]: <info> (tun-n2-axon): device state change: unavailable -> disconnected (reason 'connection-assumed') [20 30 41] Oct 27 14:59:42 defiant daemon.info NetworkManager[21335]: <info> Activation (tun-n2-axon) starting connection 'tun-n2-axon' Oct 27 14:59:42 defiant daemon.info NetworkManager[21335]: <info> Activation (tun-n2-axon) Stage 1 of 5 (Device Prepare) scheduled... Oct 27 14:59:42 defiant daemon.info NetworkManager[21335]: <info> Activation (tun-n2-axon) Stage 1 of 5 (Device Prepare) started... Oct 27 14:59:42 defiant daemon.info NetworkManager[21335]: <info> (tun-n2-axon): device state change: disconnected -> prepare (reason 'none') [30 40 0] Oct 27 14:59:42 defiant daemon.info NetworkManager[21335]: <info> Activation (tun-n2-axon) Stage 2 of 5 (Device Configure) scheduled... Oct 27 14:59:42 defiant daemon.info NetworkManager[21335]: <info> Activation (tun-n2-axon) Stage 1 of 5 (Device Prepare) complete. Oct 27 14:59:42 defiant daemon.info NetworkManager[21335]: <info> Activation (tun-n2-axon) Stage 2 of 5 (Device Configure) starting... Oct 27 14:59:42 defiant daemon.info NetworkManager[21335]: <info> (tun-n2-axon): device state change: prepare -> config (reason 'none') [40 50 0] Oct 27 14:59:42 defiant daemon.info NetworkManager[21335]: <info> Activation (tun-n2-axon) Stage 2 of 5 (Device Configure) successful. Oct 27 14:59:42 defiant daemon.info NetworkManager[21335]: <info> Activation (tun-n2-axon) Stage 3 of 5 (IP Configure Start) scheduled. Oct 27 14:59:42 defiant daemon.info NetworkManager[21335]: <info> Activation (tun-n2-axon) Stage 2 of 5 (Device Configure) complete. Oct 27 14:59:43 defiant daemon.info NetworkManager[21335]: <info> Activation (tun-n2-axon) Stage 3 of 5 (IP Configure Start) started... Oct 27 14:59:43 defiant daemon.info NetworkManager[21335]: <info> (tun-n2-axon): device state change: config -> ip-config (reason 'none') [50 70 0] Oct 27 14:59:43 defiant daemon.info NetworkManager[21335]: <info> Activation (tun-n2-axon) Stage 5 of 5 (IPv4 Configure Commit) scheduled... Oct 27 14:59:43 defiant daemon.info NetworkManager[21335]: <info> Activation (tun-n2-axon) Stage 3 of 5 (IP Configure Start) complete. Oct 27 14:59:43 defiant daemon.info NetworkManager[21335]: <info> Activation (tun-n2-axon) Stage 5 of 5 (IPv4 Commit) started... Oct 27 14:59:43 defiant daemon.info NetworkManager[21335]: <info> (tun-n2-axon): device state change: ip-config -> ip-check (reason 'none') [70 80 0] Oct 27 14:59:43 defiant daemon.info NetworkManager[21335]: <info> Activation (tun-n2-axon) Stage 5 of 5 (IPv4 Commit) complete. Oct 27 14:59:43 defiant daemon.info NetworkManager[21335]: <info> (tun-n2-axon): device state change: ip-check -> secondaries (reason 'none') [80 90 0] Oct 27 14:59:43 defiant daemon.info NetworkManager[21335]: <info> (tun-n2-axon): device state change: secondaries -> activated (reason 'none') [90 100 0] Oct 27 14:59:43 defiant daemon.info NetworkManager[21335]: <info> Activation (tun-n2-axon) successful, device activated. Oct 27 14:59:44 defiant user.notice logger: dnssec-trigger-hook(networkmanager) tun-n2-axon up added global DNS
Is there a chance we can get --log-level=debug output from this? It's likely some issue with NM mis-reading the state or not storing the state correctly, and that should certainly be fixed.
After reviewing the logs I think: cb94fe0a9e985647d0feb3637dabdeab56a650a1 core: don't override external route metrics (bgo #738268) should fix this issue as well, since it actually doesn't just apply to route metrics but also to addresses. The issue was that merging the generated setting back into the config lost some information which caused NM to think the existing address/routes were not correct, and NM overwrote them.
cb94fe0a9e985647d0feb3637dabdeab56a650a1 was confirmed to fix the bug. Thus closing