[Pkg-utopia-maintainers] Bug#534568: NM brings the eth0 connection using the configuration for tun0
Josselin Mouette
joss at debian.org
Thu Jun 25 10:53:15 UTC 2009
Package: network-manager
Version: 0.7.1-1
Severity: normal
In addition to the DHCP configuration for eth0, I have a tunnel
configured in /etc/network/interfaces, that I sometimes need to bring up
manually. Here are the contents of the file:
# The loopback network interface
auto lo
iface lo inet loopback
# The primary network interface
allow-hotplug eth0
iface eth0 inet dhcp
iface tun0 inet static
address 192.168.42.2
netmask 255.255.255.0
NM shows two available wired connections in the applet: eth0 and tun0.
The first problem is that it always select tun0 by default; even when I
select the other by hand, it uses tun0 when the connection comes back.
The second problem is that it configures eth0 with the IP that should be
used for tun0.
Here is the output of NetworkManager --no-daemon :
NetworkManager: <info> starting...
/sbin/ifup: interface lo already configured
NetworkManager: <info> Found radio killswitch /org/freedesktop/Hal/devices/pci_8086_4229_rfkill_4965AGN_wlan
NetworkManager: <info> (eth0): new Ethernet device (driver: 'sky2')
NetworkManager: <info> (eth0): exported as /org/freedesktop/Hal/devices/net_00_17_42_2d_66_bb
NetworkManager: <info> (wlan0): driver supports SSID scans (scan_capa 0x01).
NetworkManager: <info> (wlan0): new 802.11 WiFi device (driver: 'iwlagn')
NetworkManager: <info> (wlan0): exported as /org/freedesktop/Hal/devices/net_00_13_e8_a0_3c_0d
NetworkManager: <info> (ttyS0): ignoring due to lack of mobile broadband capabilties
NetworkManager: <info> (ttyS3): ignoring due to lack of mobile broadband capabilties
NetworkManager: <info> Wireless now disabled by radio killswitch
After a few seconds, it brings up eth0 with the IP for tun0:
NetworkManager: <info> (eth0): device state change: 1 -> 2
NetworkManager: <info> (eth0): bringing up device.
NetworkManager: <info> (eth0): preparing device.
NetworkManager: <info> (eth0): deactivating device (reason: 2).
NetworkManager: <info> (wlan0): device state change: 1 -> 2
NetworkManager: <info> (wlan0): bringing up device.
NetworkManager: <info> (wlan0): preparing device.
NetworkManager: <info> (wlan0): deactivating device (reason: 2).
NetworkManager: <info> (eth0): carrier now ON (device state 2)
NetworkManager: <info> (eth0): device state change: 2 -> 3
NetworkManager: <info> Activation (eth0) starting connection 'Ifupdown (tun0)'
NetworkManager: <info> (eth0): device state change: 3 -> 4
NetworkManager: <info> Activation (eth0) Stage 1 of 5 (Device Prepare) scheduled...
NetworkManager: <info> Activation (eth0) Stage 1 of 5 (Device Prepare) started...
NetworkManager: <info> Activation (eth0) Stage 2 of 5 (Device Configure) scheduled...
NetworkManager: <info> Activation (eth0) Stage 1 of 5 (Device Prepare) complete.
NetworkManager: <info> Activation (eth0) Stage 2 of 5 (Device Configure) starting...
NetworkManager: <info> (eth0): device state change: 4 -> 5
NetworkManager: <info> Activation (eth0) Stage 2 of 5 (Device Configure) successful.
NetworkManager: <info> Activation (eth0) Stage 3 of 5 (IP Configure Start) scheduled.
NetworkManager: <info> Activation (eth0) Stage 2 of 5 (Device Configure) complete.
NetworkManager: <info> Activation (eth0) Stage 3 of 5 (IP Configure Start) started...
NetworkManager: <info> (eth0): device state change: 5 -> 7
NetworkManager: <info> Activation (eth0) Stage 4 of 5 (IP Configure Get) scheduled...
NetworkManager: <info> Activation (eth0) Stage 3 of 5 (IP Configure Start) complete.
NetworkManager: <info> Activation (eth0) Stage 4 of 5 (IP Configure Get) started...
NetworkManager: <info> Activation (eth0) Stage 5 of 5 (IP Configure Commit) scheduled...
NetworkManager: <info> Activation (eth0) Stage 4 of 5 (IP Configure Get) complete.
NetworkManager: <info> Activation (eth0) Stage 5 of 5 (IP Configure Commit) started...
NetworkManager: <info> (eth0): removing resolv.conf from /sbin/resolvconf
NetworkManager: <info> (eth0): device state change: 7 -> 8
NetworkManager: <info> (eth0): removing resolv.conf from /sbin/resolvconf
NetworkManager: <info> Policy set 'Ifupdown (tun0)' (eth0) as default for routing and DNS.
NetworkManager: <info> Activation (eth0) successful, device activated.
NetworkManager: <info> Activation (eth0) Stage 5 of 5 (IP Configure Commit) complete.
And this is what happens if I select eth0 by hand in the applet:
NetworkManager: <info> (eth0): device state change: 8 -> 3
NetworkManager: <info> (eth0): deactivating device (reason: 0).
NetworkManager: <info> (eth0): removing resolv.conf from /sbin/resolvconf
-- Error received: Numerical result out of range
-- Original message: type=0x19 length=56 flags=<REQUEST,ACK> sequence-nr=1245926391 pid=4199931
NetworkManager: <WARN> check_one_route(): (eth0) error -34 returned from rtnl_route_del(): Sucess
NetworkManager: <info> Activation (eth0) starting connection 'Ifupdown (eth0)'
NetworkManager: <info> (eth0): device state change: 3 -> 4
NetworkManager: <info> Activation (eth0) Stage 1 of 5 (Device Prepare) scheduled...
NetworkManager: <info> Activation (eth0) Stage 1 of 5 (Device Prepare) started...
NetworkManager: <info> Activation (eth0) Stage 2 of 5 (Device Configure) scheduled...
NetworkManager: <info> Activation (eth0) Stage 1 of 5 (Device Prepare) complete.
NetworkManager: <info> Activation (eth0) Stage 2 of 5 (Device Configure) starting...
NetworkManager: <info> (eth0): device state change: 4 -> 5
NetworkManager: <info> Activation (eth0) Stage 2 of 5 (Device Configure) successful.
NetworkManager: <info> Activation (eth0) Stage 3 of 5 (IP Configure Start) scheduled.
NetworkManager: <info> Activation (eth0) Stage 2 of 5 (Device Configure) complete.
NetworkManager: <info> Activation (eth0) Stage 3 of 5 (IP Configure Start) started...
NetworkManager: <info> (eth0): device state change: 5 -> 7
NetworkManager: <info> Activation (eth0) Beginning DHCP transaction.
Internet Systems Consortium DHCP Client V3.1.1
Copyright 2004-2008 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/
NetworkManager: <info> dhclient started with pid 5689
NetworkManager: <info> Activation (eth0) Stage 3 of 5 (IP Configure Start) complete.
NetworkManager: <info> DHCP: device eth0 state changed (null) -> preinit
Listening on LPF/eth0/00:17:42:2d:66:bb
Sending on LPF/eth0/00:17:42:2d:66:bb
Sending on Socket/fallback
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 3
DHCPOFFER from 194.167.21.254
DHCPREQUEST on eth0 to 255.255.255.255 port 67
DHCPACK from 194.167.21.254
NetworkManager: <info> DHCP: device eth0 state changed preinit -> bound
NetworkManager: <info> Activation (eth0) Stage 4 of 5 (IP Configure Get) scheduled...
NetworkManager: <info> Activation (eth0) Stage 4 of 5 (IP Configure Get) started...
NetworkManager: <info> address 194.167.21.146
NetworkManager: <info> prefix 24 (255.255.255.0)
NetworkManager: <info> gateway 194.167.21.254
NetworkManager: <info> nameserver '192.168.36.50'
NetworkManager: <info> nameserver '192.168.38.70'
NetworkManager: <info> nameserver '192.168.38.71'
NetworkManager: <info> domain name 'btic.loc'
NetworkManager: <info> wins '192.168.36.50'
NetworkManager: <info> wins '192.168.38.70'
NetworkManager: <info> wins '192.168.38.71'
NetworkManager: <info> Activation (eth0) Stage 5 of 5 (IP Configure Commit) scheduled...
NetworkManager: <info> Activation (eth0) Stage 4 of 5 (IP Configure Get) complete.
NetworkManager: <info> Activation (eth0) Stage 5 of 5 (IP Configure Commit) started...
bound to 194.167.21.146 -- renewal in 43114 seconds.
NetworkManager: <info> (eth0): writing resolv.conf to /sbin/resolvconf
NetworkManager: <info> (eth0): device state change: 7 -> 8
NetworkManager: <info> (eth0): writing resolv.conf to /sbin/resolvconf
NetworkManager: <info> Policy set 'Ifupdown (eth0)' (eth0) as default for routing and DNS.
NetworkManager: <info> Activation (eth0) successful, device activated.
NetworkManager: <info> Activation (eth0) Stage 5 of 5 (IP Configure Commit) complete.
It would be nice if NM understood the tun0 configuration is meant for a
different device.
It would be even better if the tunnel could be set up or down
independently of the state of other connections; as you can imagine, a
tunnel is not very useful if there is no existing connection.
-- System Information:
Debian Release: squeeze/sid
Architecture: amd64 (x86_64)
Kernel: Linux 2.6.30-1-amd64 (SMP w/2 CPU cores)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages network-manager depends on:
ii adduser 3.110 add and remove users and groups
ii dbus 1.2.1-5 simple interprocess messaging syst
ii dhcp3-client 3.1.1-6 DHCP client
ii hal 0.5.12~git20090406.46dc48-2 Hardware Abstraction Layer
ii ifupdown 0.6.8+nmu1 high level tools to configure netw
ii libc6 2.9-1 GNU C Library: Shared libraries
ii libdbus-1-3 1.2.1-5 simple interprocess messaging syst
ii libdbus-glib 0.80-3 simple interprocess messaging syst
ii libgcrypt11 1.4.4-2 LGPL Crypto library - runtime libr
ii libglib2.0-0 2.20.0-2 The GLib library of C routines
ii libgnutls26 2.6.4-2 the GNU TLS library - runtime libr
ii libgpg-error 1.6-1 library for common error values an
ii libhal1 0.5.11-8 Hardware Abstraction Layer - share
ii libnl1 1.1-3 library for dealing with netlink s
ii libnm-glib0 0.7.1-1 network management framework (GLib
ii libnm-util1 0.7.1-1 network management framework (shar
ii libpolkit-db 0.9-3 library for accessing PolicyKit vi
ii libpolkit2 0.9-3 library for accessing PolicyKit
ii libtasn1-3 1.8-1 Manage ASN.1 structures (runtime)
ii libuuid1 1.41.3-1 universally unique id library
ii lsb-base 3.2-20 Linux Standard Base 3.2 init scrip
ii wpasupplican 0.6.4-3 Client support for WPA and WPA2 (I
ii zlib1g 1:1.2.3.3.dfsg-12 compression library - runtime
Versions of packages network-manager recommends:
ii dnsmasq-base 2.49-1 A small caching DNS proxy and DHCP
ii iptables 1.4.2-5 administration tools for packet fi
ii network-manager-gnome 0.7.1-1 network management framework (GNOM
ii policykit 0.9-3 framework for managing administrat
ii ppp 2.4.4rel-10.1 Point-to-Point Protocol (PPP) - da
Versions of packages network-manager suggests:
ii avahi-autoipd 0.6.23-4 Avahi IPv4LL network address confi
-- no debconf information
--
.''`. Josselin Mouette
: :' :
`. `' “I recommend you to learn English in hope that you in
`- future understand things” -- Jörg Schilling
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: Ceci est une partie de message num?riquement sign?e
URL: <http://lists.alioth.debian.org/pipermail/pkg-utopia-maintainers/attachments/20090625/311589a2/attachment.pgp>
More information about the Pkg-utopia-maintainers
mailing list