Comment 64 for bug 64173

Revision history for this message
Lars M Bengtsson (lars-m-bengtsson) wrote :

Hi all,

Although I am the guy who created this bug report, I'm beginning to feel like I have to come to the defence of NetworkManager here.... :)

The issue that I had with the WLAN in Edgy was that the network link would seem to be interrupted for some very short time now and then - ie like if you pull the cable from a network card for some fractions of a second. This did not seem to happen when some other similar network manager program was used (kwlan, for example) so I put the blame on NetworkManager - wrongly, I now think. I would now guess that it was due to some ipw2200 driver bug, which by the way seems to me to have been fixed by now - if it still happens I have not been able to detect it.

I have never seen networkmanager completely break an existing connection with an access point and go through the whole interface setup procedure, renew IP-addresses, etcetera. Granted, KNetworkManager can be somewhat tricky to use at times, but when it has established a connection it is rock solid from there on.

My apologies if the initial report was not clear enough about the exact problem I had. I guess it may be the case that some of you who have added to this bug report have seen a different problem.

I have seen some behavior similar to my initial problem on another laptop I have (the WLAN "hangs" for a second or two now and then) but this laptop (an LG M1, Intel 3945, ipw3945 driver) has proven generally Linux-unfriendly so I am not yet ready to put the blame on Ubuntu for this. Except for those annoying short lockups, the wireless network software and notably networkmanager itself seems to work perfectly fine.

I guess my point is that Networkmanager at this time actually works very well, at least for me, so it can't be completely broken. Unfortunately I have no tips, tricks or good explanations for those of you who have more trouble with it than I have had...

Best regards,
Lars