Public bug reported:
Binary package hint: network-manager
in ubuntu 7.10 gutsy, I have the wired interface (eth0) set to a static
IP, but not set to ifup automatically at boot as it is not normally
connected. When network manager starts, it 'turns on' eth0, meaning I
can see it in ifconfig, but it has no IP address or anything of that
sort. Network manager then continues to bring up and connect the
wireless interface (wlan0) automatically. So far so good. However, upon
suspend/resume, eth0 is ifuped, and attempts to connect to the network,
which there is none as it is not connected. The problem with this is
that eth0 now has an entry in my routing table, which causes any address
on the local network to fail to work (verified by cups failing to print,
nautilus cannot connect via smb/ssh, etc.). Addresses outside the local
network still work. This is due to the way the /etc/acpi/suspend.d/55
-down-interfaces.sh script works. The acpi script read what interfaces
are active by looking at the output of ifconfig. Thus, it sees the
supposedly 'up' eth0, and marks it as an interface to bring back on
resume. Sure enough, upon resume /etc/acpi/resume.d/62-ifup.sh happily
brings eth0 back up, causing the trouble outlined above.
It seems to me that the way to fix this is to make network-manager not
'turn on' network interfaces it does not control. I presume the purpose
of turning it on is so that NM can sense when a cable is plugged in,
however this is unnecessary if NM is not managing the interface, and I
expect it might save a miniscule amount of power as well. alternatively,
the acpi fiup/down scripts could be made to check for the presence of a
cable (or an ip?) and only ifdown/ifup those interfaces that do have
one.
I have verified this on two different laptops, one an HP Pavilion dv4000
with 10/100 ethernet and intel 2200bg wifi, and the other a lenovo
thinkpad t61 with gigabit ethernet and intel 4965abgn wifi.
I hypothesize that the reason I experience this particular phenomenon
with the routing is because in this case the wired and wireless networks
are on separate subnets (255.255.248.0 and 255.255.224.0 respectively),
so the routing works differently than it would in most cases, where they
would use the same subnet.
** Affects: network-manager (Ubuntu)
Importance: Undecided
Status: New
--
network manager 'turns on' wired interface with static IP, causing it to be
ifuped upon resume from sleep/hibernate
https://bugs.launchpad.net/bugs/191413
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
