desktop-packages team mailing list archive

[Romano Giannetti <romano.giannetti@xxxxxxxxx>]

I have this problem too, or a similar one. Oneiric 11.10.

The Wifi here in my university has different SSIDs --- all normally with
very similar strengths. I have sometime connected to all of them, but
having them different "privileges".

For example, I have a WPA2 "local" SSID with full access to the network,
and a WPA2 "global" SSID working in almost all Spanish Universities with
quite reduced access (it's thought for guests, and it's the same SSID
all around, so when I am in another university, I use it).

There seems no way to say to NM that I want the local one, if in range,
even if the global could be stronger. If a disconnect occur, or if an
auto-suspend occurs, NM reconnects to one of them in almost arbitrary
way.

I understand the trend to keep the interfaces simple, but a way of
marking "personal priority" should be provided.

And by the way, a "never ever again connect to that network automatically " should be there, too: 
there are a lot of very insecure free hotspot around and if you make the error of connecting one time, then it's very convoluted to mark them off-limits (see also https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/891678)

-- 
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:
  Confirmed
Status in “network-manager” package in Ubuntu:
  Confirmed

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