This bug is a mix of a bunch of different issues, none of which actually
related or even traceable to the same issue. All of them are hardware-
specific and thus need to be file separately.
PLEASE, if you're seeing "this bug" or anything that makes you think
whatever you're experiencing as issues are "this bug", file a new bug
report for your own issues, don't comment here. This bug report actually
really just needs to be closed as Invalid, since any new reports will
cover the exact symptoms and issues specifically. The original issues
reported have long since been fixed
There's a couple of different things in here:
- Issues with Broadcom drivers and/or the ath5k driver and keeping connections
established, needs to be debugged separately, and needs wpa_supplicant logs:
that all needs to be done as separate new bug reports, not as comments here.
- priorities for connections/don't automatically connect: a long-time Wishlist
report alreday reported elsewhere.
- automatic connections to unwanted networks: they just need to be deleted from
the connection editor, then won't be connected to automatically.
** Changed in: network-manager (Ubuntu)
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/111502
Title:
network-manager unreliable with multiple APs
Status in NetworkManager:
Incomplete
Status in “network-manager” package in Ubuntu:
Invalid
Bug description:
Binary package hint: network-manager
Ubuntu 7.04 (PPC)
Broadcom 4306 (bcm43xx driver)
Network manager is totally unreliable when I use it at my University,
where there are multiple APs.
It drops the connection all the time, and when (more like if) it
manages to reconnect it doesn't re-establish the lost VPN connection.
I am trying to connect to this one wireless network, "central" - there
is one AP on channel 1 and one on channel 11. It works fine if I
configure my device manually through iwconfig to channel 1, maybe n-m
tries to keep switching between the two or something, then
occasionally it just randomly roams to a completely different network
for no reason. This should be apparent from my daemon.log.
All the APs are of similar strength, and as I said they work fine
configured manually without n-m which has been a complete pain in the
backside ever since it was included in Feisty.
To manage notifications about this bug go to:
https://bugs.launchpad.net/network-manager/+bug/111502/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : [email protected]
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
