Package: network-manager
Version: 0.9.10.0-3
Severity: important
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
assumption feature.
--
| .''`. ** Debian **
Peter Palfrader | : :' : The universal
http://www.palfrader.org/ | `. `' Operating System
| `- http://www.debian.org/
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
