After resume, thinks my wireless network is wired

[Stian Jordet]

With kernels 2.6.17-6 and self compiled 2.6.18-rc4 after resume sometimes (but not always) network-manager thinks that my ipw2200 is wired. And then it obviously can't connect...

Never have this problem with the dapper kernel (2.6.15-26).

[Stian Jordet (stian-web)]

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...

[Scott James Remnant (Canonical) (canonical-scott)]

Could be a regression in the upstream kernel

[Ben Collins (ben-collins)]

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 shows are actually the names of the wireless ESSID's
2) Reloading the driver(s) (including ieee80211) for my bcm43xx doesn't fix it.

This seems to be irrelevant to the card being used. Two other ubuntu developers noticed this problems as well, and they are using different chips/drivers than myself (and even the submitter).

[Simon Law (sfllaw)]

It's certainly a network manager bug. If you restart network manager,
sanity returns.

[Ben Collins (ben-collins)]

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.

[Santiago Canez (canez)]

Just wanted to confirm this bug on my laptop. As above, reloading ipw2200 works.

[gpothier (gpothier)]

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.

[Paulo Miguel Marques (nightwish)]

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.

[Paulo Miguel Marques (nightwish)]

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.