I stand corrected, network manager (at least the latest), does remember
the bssid/ssid combination. If it knows about both it will roam. Only
for networks that have a factory defaul SSID (e.g. belkin54g) it will
refuse to roam.
I don't see how to improve this without breaking roaming, except
Alexander mentioned network-manager doesn't index by essid/address
combination.
Not doing so might be a design option to accommodate the case where the same
essid serves the same network.
A better idea would be to index by the essid/mode/encryption-type and that way
it wouldn't break the
** Tags added: qa-hardy-platform
** Tags removed: qa-hardy-list
--
NM cannot distinguish between two networks with the same SSID at all
https://bugs.launchpad.net/bugs/129908
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
** Tags added: qa-hardy-list
--
NM cannot distinguish between two networks with the same SSID at all
https://bugs.launchpad.net/bugs/129908
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
I'm in the same case.
In fact NM knows mac adresses of acces points (AP), and nm-applet store it in
/system/networking/wireless/networks/ESSID/bssids (use gconf-editor to browse
it).
But it will also scan for new AP and thus can try to connect to an AP with same
essid if it found it before the
It would be great if nm-applet was able to check if there is one or more
AP, and ask the user witch one it should connect to if there are
several.
If this can't quickly be fixed, it would be great to have a control on
this using gconf-editor (lock the list of bssid, and chose an order or
check
My university provides wireless internet in a number of locations. When
reception is poor however, it seems that a number of other users'
laptops will advertise an 'ad-hoc' wireless network with the same SSID
as the university's 'master' routers. As a result, nm usually tries to
connect to them,
On Sun, Sep 16, 2007 at 07:54:01PM -, Andrew J. Montalenti wrote:
I'd just like to confirm this bug. On my network, I have two APs -- one
is my router/gateway, and the other is a Linksys range extender. They
are both using the same SSID (since that's how range extenders work),
but
I'd just like to confirm this bug. On my network, I have two APs -- one
is my router/gateway, and the other is a Linksys range extender. They
are both using the same SSID (since that's how range extenders work),
but depending where I am, one may have more strength than the other.
I can see this
does it really bounce in between those two networks ... or just away
from the initial association after system-start?
** Changed in: network-manager (Ubuntu)
Importance: Undecided = Medium
--
NM cannot distinguish between two networks with the same SSID at all
For some reason I really could not comprehend you question. Maybe it's
because I haven't eaten or because I'm tired, but I'll try to answer
anyway...
Yes, it really bounces between the two quite randomly.
Sometimes it will choose the network you want, and suddenly later it
will switch to the
this sounds a bit like network-manager doesn't index by essid/address
combination, but just by essid. WIll investigate if this idea matches
what can be found in code.
** Changed in: network-manager (Ubuntu)
Assignee: (unassigned) = Alexander Sack
Status: Incomplete = Confirmed
--
NM
can you please post the output of:
sudo iwlist scan
Thanks,
- Alexander
** Changed in: network-manager (Ubuntu)
Status: New = Incomplete
--
NM cannot distinguish between two networks with the same SSID at all
https://bugs.launchpad.net/bugs/129908
You received this bug notification
[EMAIL PROTECTED]:~$ sudo iwlist scan
Password:
loInterface doesn't support scanning.
wifi0 Interface doesn't support scanning.
ath0 Scan completed :
Cell 01 - Address: 00:18:39:BA:67:D2
ESSID:linksys
Mode:Master
14 matches
Mail list logo
