[Bug 57501] Re: After resume, thinks my wireless network is wired

*** This bug is a duplicate of bug 59981 *** ** This bug has been marked a duplicate of bug 59981 suspend makes network-manager say eth1 is a wired device -- After resume, thinks my wireless network is wired https://launchpad.net/bugs/57501 -- ubuntu-bugs mailing list

[Bug 57501] Re: After resume, thinks my wireless network is wired

** Bug 61652 has been marked a duplicate of this bug -- After resume, thinks my wireless network is wired https://launchpad.net/bugs/57501 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 57501] Re: After resume, thinks my wireless network is wired

Same here, 2 year old Asus M6Ne. I had filed a bug on network manager, https://launchpad.net/distros/ubuntu/+source/network-manager/+bug/61652 , but this sounds like a more appropriate place. -- After resume, thinks my wireless network is wired https://launchpad.net/bugs/57501 -- ubuntu-bugs

[Bug 57501] Re: After resume, thinks my wireless network is wired

Forgot to say... restarting Network Manager does not solve it, removing and reinserting the network modules does. (tg3 and ipw2200 modules, in my case.) The exact effect is eth0 and eth1 getting switched at resume, but not always, which indeed suggests some race condition. -- After resume,

[Bug 57501] Re: After resume, thinks my wireless network is wired

Just wanted to confirm this bug on my laptop. As above, reloading ipw2200 works. -- After resume, thinks my wireless network is wired https://launchpad.net/bugs/57501 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 57501] Re: After resume, thinks my wireless network is wired

Same here on a Dell Latitude D810 notebook, with latest kernel (2.6.17-8). Reloading ipw2200/ieee80211 works. Restarting network manager has no effect. -- After resume, thinks my wireless network is wired https://launchpad.net/bugs/57501 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com

[Bug 57501] Re: After resume, thinks my wireless network is wired

Could be a regression in the upstream kernel ** Changed in: network-manager (Ubuntu) Sourcepackagename: network-manager = linux-source-2.6.17 -- After resume, thinks my wireless network is wired https://launchpad.net/bugs/57501 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com

[Bug 57501] Re: After resume, thinks my wireless network is wired

I believe this is a network manager bug. If iwconfig can detect that the interface is wireless (which it can when this occurs) then network manager should recognize this as well. I know that when it happens on my machine, there's two things that make be believe this: 1) The wired interface(s) it

[Bug 57501] Re: After resume, thinks my wireless network is wired

It's certainly a network manager bug. If you restart network manager, sanity returns. ** Changed in: network-manager (Ubuntu) Importance: Untriaged = Medium Status: Unconfirmed = Confirmed -- After resume, thinks my wireless network is wired https://launchpad.net/bugs/57501 --

[Bug 57501] Re: After resume, thinks my wireless network is wired

Revised my opinion of this bug. After rechecking, it seems that reloading ieee80211 modules does fix the issue. Also affected by this problem appears to be iftab, which does not readily change the interface to the correct name in what seems to be a race condition. ** Changed in: network-manager

[Bug 57501] Re: After resume, thinks my wireless network is wired

Forgot to write that wireless works after resume _every_ time when just having wireless-essid and wireless-key in interfaces. So while the bug does not happen with 2.6.15-26, I don't think it's a kernel problem... -- After resume, thinks my wireless network is wired