Public bug reported:
Binary package hint: network-manager
One way to reproduce the frustrating discomfort caused by the lack of a
"preferred network order" feature:
Pre-requisite: be connected to your usual wifi network with at least
one other wireless network you connected to in the past (logged in NM
history) and available at that time (=available known alternative
network).
Example modification triggering a short network drop: setting wifi network
available to all users drops the connection and won't reconnect to the original
network although it has always been available in the process.
1. Open NM (right click on the network notification applet, modify connections)
2. Select the wifi network you are connected to, modify
3. Check the bottom box "Available to all users"
The current connection you just modified drops and NM reconnects to the
**next available known network**, not the original one.
If there's no other known network available though, NM properly
reconnects to your wifi network (reproduce this by cleaning up the other
available wifi networks in the history).
This is more generally an issue of setting a preferred network/preference order
in NM (wishlist?).
Currently there's no preference order other than most recent connection.
Tougher to implement: NM notifies users when recently disconnected preferred
network is back and they would like to switch back to it.
This would be especially useful when you use a fallback (limited) network and
would want to reconnect to you primary network asap (more or less temporary ISP
failure).
I would set the importance higher than a wishlist issue considering the
professional and intensive use of a connection.
** Affects: network-manager (Ubuntu)
Importance: Undecided
Status: New
** Summary changed:
- Dropped connection will reconnect to next known network (lack of WLAN
preference order feature)
+ Dropped connection will reconnect to next known network, even if original
network is available (lack of WLAN preference order feature)
** Description changed:
Binary package hint: network-manager
One way to reproduce the frustrating discomfort caused by the lack of a
"preferred network order" feature:
Pre-requisite: be connected to your usual wifi network with at least
one other wireless network you connected to in the past (logged in NM
history) and available at that time (=available known alternative
network).
- Example modification triggering network drop: setting wifi network available
to all users drops the connection
+ Example modification triggering a short network drop: setting wifi network
available to all users drops the connection and won't reconnect to the original
network although it has always been available in the process.
1. Open NM (right click on the network notification applet, modify
connections)
2. Select the wifi network you are connected to, modify
3. Check the bottom box "Available to all users"
The current connection you just modified drops and NM reconnects to the
- **next available known network**, not the previous one.
+ **next available known network**, not the original one.
If there's no other known network available though, NM properly
reconnects to your wifi network (reproduce this by cleaning up the other
available wifi networks in the history).
This is more generally an issue of setting a preferred network/preference
order in NM (wishlist?).
Currently there's no preference order other then most recent connection.
Tougher to implement: NM notifies users when recently disconnected preferred
network is back and he would like to switch to it.
This would be especially useful when you use a fallback (limited) network and
would want to reconnect to you primary network asap (more or less temporary ISP
failure). This is especially important for professionals.
** Description changed:
Binary package hint: network-manager
One way to reproduce the frustrating discomfort caused by the lack of a
"preferred network order" feature:
Pre-requisite: be connected to your usual wifi network with at least
one other wireless network you connected to in the past (logged in NM
history) and available at that time (=available known alternative
network).
Example modification triggering a short network drop: setting wifi network
available to all users drops the connection and won't reconnect to the original
network although it has always been available in the process.
1. Open NM (right click on the network notification applet, modify
connections)
2. Select the wifi network you are connected to, modify
3. Check the bottom box "Available to all users"
The current connection you just modified drops and NM reconnects to the
**next available known network**, not the original one.
If there's no other known network available though, NM properly
reconnects to your wifi network (reproduce this by cleaning up the other
available wifi networks in the history).
+
This is more generally an issue of setting a preferred network/preference
order in NM (wishlist?).
- Currently there's no preference order other then most recent connection.
+ Currently there's no preference order other than most recent connection.
- Tougher to implement: NM notifies users when recently disconnected preferred
network is back and he would like to switch to it.
- This would be especially useful when you use a fallback (limited) network and
would want to reconnect to you primary network asap (more or less temporary ISP
failure). This is especially important for professionals.
+ Tougher to implement: NM notifies users when recently disconnected preferred
network is back and they would like to switch back to it.
+ This would be especially useful when you use a fallback (limited) network and
would want to reconnect to you primary network asap (more or less temporary ISP
failure).
+ I would set the importance higher than a wishlist issue considering the
professional and intensive use of a connection.
--
Dropped connection will reconnect to next known network, even if original
network is available (lack of WLAN preference order feature)
https://bugs.launchpad.net/bugs/672541
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
