Public bug reported:
Summary:
If I suspend-to-ram while connected via the wired ethernet card (eth0), and
then resume with the ethernet cord unplugged but in range of a wireless access
point, network manager will correctly establish a connection with my wireless
access point. However, /etc/resolv.conf still reflects the wired ethernet
connection, so the wireless internet connection doesn't work. The problem is
easily fixed by running the command 'sudo resolvconf -d eth0'.
Steps to reproduce error:
1) Have laptop connected via wired network connection (eth0).
2) suspend-to-ram
3) unplug ethernet cord
4) move to within range of wireless access point
5) resume computer
What happens:
Upon resuming from suspend-to-ram, network manager will detect my wireless
access point and establish a connection. However, /etc/resolv.conf still shows
the name servers that belonged to the wired ethernet connection. This means
that the wireless network connection gives the impression of not being
connected.
What should happen:
network manager should inform resolvconf that the wired network connection has
been taken down, so that resolvconf removes the corresponding entries from
/etc/resolv.conf.
Temporary work-around: upon resuming, run the command:
sudo resolvconf -d eth0
This removes the entries from the wireless network connection from
/etc/resolv.conf, and replaces them with the entries belonging to the
wireless network connection.
Oddly enough, the problem doesn't seem to happen in reverse (switching
from wireless to wired).
I'm running Edgy Eft with network-manager-0.6.3-2ubuntu6. While I am at
work I connect the laptop via the wired ethernet card (eth0), but while
I'm at home I connect using a wireless network card (ath0).
** Affects: Ubuntu
Importance: Undecided
Status: Unconfirmed
--
network-manager not deleting resolvconf information on resume from suspend
https://launchpad.net/bugs/84313
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
