[opensuse] force changing ssid
Hi We have a series of rooms with wifi. If we walk from one room to the next, a phone or an ipad will use the wifi in the new room. An opensuse 13.2 laptop doesn't do that. You connect to room one and you stay with room one all day unless you walk out of range or reboot. Is there a way we can make the opensuse change as per the phones? We think the relevant part is NetworkManager Applet 0.9.10.0 but don't know where to start. Thanks -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 09/18/2015 04:09 PM, buhorojo wrote:
Hi We have a series of rooms with wifi. If we walk from one room to the next, a phone or an ipad will use the wifi in the new room. An opensuse 13.2 laptop doesn't do that. You connect to room one and you stay with room one all day unless you walk out of range or reboot. Is there a way we can make the opensuse change as per the phones?
We think the relevant part is NetworkManager Applet 0.9.10.0 but don't know where to start. Thanks
I don't know of any mechanism that would alert the operating system to your changing rooms. More than likely, your laptop is marginal in its reception capability, and as you walk from one room to the next, there is a spot where the signal is a little weaker--a phenomenon called a null, which will happen in all RF environments, but especially within a building. It is this null in signal strength which causes the loss of wifi connection. --doug, retired RF engineer -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 09/18/2015 02:15 PM, Doug wrote:
I don't know of any mechanism that would alert the operating system to your changing rooms. More than likely, your laptop is marginal in its reception capability, and as you walk from
Actually, that's supposed to be part of the normal operation, when multiple access points have the same SSID. The portable device keeps an eye on signal strength and looks for other access points with the same SSID that have a better signal. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Fri, Sep 18, 2015 at 1:09 PM, buhorojo <buhorojo.lcb@gmail.com> wrote:
We think the relevant part is NetworkManager Applet 0.9.10.0 but don't know where to start.
The NetworkManager team was working on this [1]. No updates yet. [1] https://bugzilla.gnome.org/show_bug.cgi?id=737356 Brandon Vincent -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 18/09/15 22:15, Brandon Vincent wrote:
On Fri, Sep 18, 2015 at 1:09 PM, buhorojo <buhorojo.lcb@gmail.com> wrote:
We think the relevant part is NetworkManager Applet 0.9.10.0 but don't know where to start. The NetworkManager team was working on this [1]. No updates yet.
[1] https://bugzilla.gnome.org/show_bug.cgi?id=737356
Brandon Vincent Thanks. We'll keep a lookout. Do we have alternatives we could try meanwhile? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Fri, Sep 18, 2015 at 1:32 PM, buhorojo <buhorojo.lcb@gmail.com> wrote:
Thanks. We'll keep a lookout. Do we have alternatives we could try meanwhile?
I think a couple of people have written custom shell scripts in conjunction with wpa_supplicant, but one of the reasons this feature has been delayed in NetworkManager is because if I recall correctly, a lot of wireless drivers in the kernel do not report signal strength very reliably. Obviously with a cell phone and iOS or Android, on any given device there is only one wireless chipset that needs to be supported. When you have to support a much wider variety of wireless chipsets on a laptop or desktop, the chance that the driver is going to function correctly is much slimmer. Brandon Vincent -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 18/09/15 22:40, Brandon Vincent wrote:
On Fri, Sep 18, 2015 at 1:32 PM, buhorojo <buhorojo.lcb@gmail.com> wrote:
Thanks. We'll keep a lookout. Do we have alternatives we could try meanwhile? I think a couple of people have written custom shell scripts in conjunction with wpa_supplicant, but one of the reasons this feature has been delayed in NetworkManager is because if I recall correctly, a lot of wireless drivers in the kernel do not report signal strength very reliably.
Obviously with a cell phone and iOS or Android, on any given device there is only one wireless chipset that needs to be supported. When you have to support a much wider variety of wireless chipsets on a laptop or desktop, the chance that the driver is going to function correctly is much slimmer.
Brandon Vincent For a workaround, would systemctl restart network get the strongest ssid?
If so, could I make it into a one tap button? It seems only admin can do that. Can I get a user to run it? Thanks -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Sat, Sep 19, 2015 at 11:41 AM, buhorojo <buhorojo.lcb@gmail.com> wrote:
For a workaround, would systemctl restart network get the strongest ssid?
You would probably want to restart NetworkManager and even then NetworkManager would probably try connecting to the access points by their saved order rather than signal strength. Brandon Vincent -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 09/19/2015 11:47 AM, Brandon Vincent wrote:
On Sat, Sep 19, 2015 at 11:41 AM, buhorojo <buhorojo.lcb@gmail.com> wrote:
For a workaround, would systemctl restart network get the strongest ssid?
You would probably want to restart NetworkManager and even then NetworkManager would probably try connecting to the access points by their saved order rather than signal strength.
Brandon Vincent
Why would you have to restart network manager? The network manager tray widget shows all available connections, and you can simply click the on you want to connect to. The only thing that tray widget lacks is a numerical signal strength meter, (although the number of bars is shown for each connection). There is no problem manually selecting an access point. The problem is automatically selecting an access point. Suggesting a manual restart of NM does not seem like a solution to an automatic selection problem. -- After all is said and done, more is said than done. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Sat, 19 Sep 2015, John Andersen wrote:
On 09/19/2015 11:47 AM, Brandon Vincent wrote:
On Sat, Sep 19, 2015 at 11:41 AM, buhorojo <buhorojo.lcb@gmail.com> wrote:
For a workaround, would systemctl restart network get the strongest ssid?
The problem is automatically selecting an access point. Suggesting a manual restart of NM does not seem like a solution to an automatic selection problem.
Isn't this about BSSID rather than (E)SSID? You want to pick the "basic service set" with the strongest signal out of the "extended service set available, right? In other words, there are multiple radios for the same network, and you want to pick the strongest. Otherwise I don't understand. Maybe you just want the strongest SSID. Or the SSID with the strongest BSSID available. Regards. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 09/19/2015 03:12 PM, Xen wrote:
On Sat, 19 Sep 2015, John Andersen wrote:
On 09/19/2015 11:47 AM, Brandon Vincent wrote:
On Sat, Sep 19, 2015 at 11:41 AM, buhorojo <buhorojo.lcb@gmail.com> wrote:
For a workaround, would systemctl restart network get the strongest ssid?
The problem is automatically selecting an access point. Suggesting a manual restart of NM does not seem like a solution to an automatic selection problem.
Isn't this about BSSID rather than (E)SSID? You want to pick the "basic service set" with the strongest signal out of the "extended service set available, right? In other words, there are multiple radios for the same network, and you want to pick the strongest.
Otherwise I don't understand. Maybe you just want the strongest SSID. Or the SSID with the strongest BSSID available.
Regards.
This article has some info on SSID, BSSID and ESSID: https://en.wikipedia.org/wiki/Service_set_%28802.11_network%29 If you *REALLY* want to get into the details of how WiFi works, you can get some books by Matthew Gast, from O'Reilly. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Otherwise I don't understand. Maybe you just want the strongest SSID. Or the SSID with the strongest BSSID available.
Say 15 laptops running Linux connect first lesson of the day in room 1. They stay connected all day. When the next class arrives it takes ages, so they connect to room 2 where there are also students connected. Tablets only is no problem. We've narrowed it to linux. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 El 2015-09-20 a las 16:16 +0200, buhorojo escribió:
Otherwise I don't understand. Maybe you just want the strongest SSID. Or the SSID with the strongest BSSID available.
Say 15 laptops running Linux connect first lesson of the day in room 1. They stay connected all day. When the next class arrives it takes ages, so they connect to room 2 where there are also students connected. Tablets only is no problem. We've narrowed it to linux.
If students on room 1 should use only the AP in room 1, then you should have different SSID for each room. Otherwise, who cares to which AP they connect? The computers will connect to the best one they can find. - -- Cheers Carlos E. R. (from 13.1 x86_64 "Bottle" (Minas Tirith)) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iF4EAREIAAYFAlX+xRgACgkQja8UbcUWM1z8ygD/RGX/nChhgDU5gFbVpDhs4FPc L5Q6f6e3CY55whs7GmYA/3+43lTKF01KbMW1OD2YB8bB361bSPN2jQfDKHzl/HHl =uyqw -----END PGP SIGNATURE-----
On 09/20/2015 10:39 AM, Carlos E. R. wrote:
If students on room 1 should use only the AP in room 1, then you should have different SSID for each room.
That's contrary to good practice, unless there's some reason to keep the traffic for a room isolated. It's more likely the students are using the same resources, no matter which class they're in.
Otherwise, who cares to which AP they connect? The computers will connect to the best one they can find.
The guy hiding in a back corner of a class might get a better signal from another AP than the one in his room. WiFi is designed for roaming among APs. It's the responsibility of the device to switch when necessary for a better signal. This is different from the cell phone network, where the network tells a phone to check other signals and move if necessary. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On September 20, 2015 10:46:38 AM EDT, James Knott <james.knott@rogers.com> wrote:
On 09/20/2015 10:39 AM, Carlos E. R. wrote:
If students on room 1 should use only the AP in room 1, then you should have different SSID for each room.
That's contrary to good practice, unless there's some reason to keep the traffic for a room isolated. It's more likely the students are using the same resources, no matter which class they're in.
Otherwise, who cares to which AP they connect? The computers will connect to the best one they can find.
The guy hiding in a back corner of a class might get a better signal from another AP than the one in his room. WiFi is designed for roaming among APs. It's the responsibility of the device to switch when necessary for a better signal. This is different from the cell phone network, where the network tells a phone to check other signals and move if necessary.
A lot of wireless routers support multiple SSIDs. Maybe adding a generic school wide SSID to each router would make sense? Greg -- Sent from my Android device with K-9 Mail. Please excuse my brevity. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 09/20/2015 11:04 AM, greg.freemyer@gmail.com wrote:
A lot of wireless routers support multiple SSIDs.
Yep, but I don't think that's the issue here. However, they might have one SSID for students and another for staff. A few years ago, I set up some access points for a senior's residence. There was one SSID for staff and another for the residents.
Maybe adding a generic school wide SSID to each router would make sense?
I don't recall if the OP said the same SSID or different. I got the impression he was talking about different ones, but if he wants to roam from room to room, there should be one SSID. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 El 2015-09-20 a las 11:16 -0400, James Knott escribió:
I don't recall if the OP said the same SSID or different. I got the impression he was talking about different ones, but if he wants to roam from room to room, there should be one SSID.
- From memory (another thread) it is the same SSID on several rooms. - -- Cheers Carlos E. R. (from 13.1 x86_64 "Bottle" (Minas Tirith)) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iF4EAREIAAYFAlX+9EwACgkQja8UbcUWM1wJPgD9GxvBt76tIAIStzCGNMhys9iP bBEVlCJnL43/kFcayIYBAI1TgG1X5EFI7bnqDp4Y1Z1KxtG7Suhb7NU7idO3m81O =v5ju -----END PGP SIGNATURE-----
On September 20, 2015 2:00:44 PM EDT, "Carlos E. R." <robin.listas@telefonica.net> wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256
El 2015-09-20 a las 11:16 -0400, James Knott escribió:
I don't recall if the OP said the same SSID or different. I got the impression he was talking about different ones, but if he wants to roam from room to room, there should be one SSID.
- From memory (another thread) it is the same SSID on several rooms.
I'm pretty sure they are currently one unique SSID per room. If they change to a common. SSID shared by the campus, what level is the choice of APs made at? I would think the WLAN nic might do that internally? Greg -- Sent from my Android device with K-9 Mail. Please excuse my brevity. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 20/09/15 20:00, Carlos E. R. wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256
El 2015-09-20 a las 11:16 -0400, James Knott escribió:
I don't recall if the OP said the same SSID or different. I got the impression he was talking about different ones, but if he wants to roam from room to room, there should be one SSID.
- From memory (another thread) it is the same SSID on several rooms. Hi We've tried both. Only opensuse stays connected to the first room. Tablets are fine. I think we narrowed it to networkmanager and the bug report so we're really looking for a workaround.
If someone could help us with the button idea we mentioned that would be great: a one tap button which restarted the network. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 El 2015-09-22 a las 16:23 +0200, buhorojo escribió:
If someone could help us with the button idea we mentioned that would be great: a one tap button which restarted the network.
Just tap on NM applet to disconnect, then again to connect. The connection is reevaluated. - -- Cheers Carlos E. R. (from 13.1 x86_64 "Bottle" (Minas Tirith)) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iF4EAREIAAYFAlYBhEkACgkQja8UbcUWM1wDLAD5AWjAgcB1iruFR1+yRgFjxdFF 5HE1krPmXQk2J8WmkxcA/2mW7YazV7TcFzldSwYhSwS5b49cxcUyipGYOSQ6vBrQ =OaE3 -----END PGP SIGNATURE-----
On 22/09/15 18:39, Carlos E. R. wrote:
El 2015-09-22 a las 16:23 +0200, buhorojo escribió:
If someone could help us with the button idea we mentioned that would be great: a one tap button which restarted the network.
Just tap on NM applet to disconnect, then again to connect. The connection is reevaluated.
Hi Yes, of course. We didn't know it was tappable. It looks like 3 taps. tap the icon. tap disconnect. tap the room you are in. Is there any way we can get the list after the disconnect in order of signal strength I wonder. Anyway, great post. Thanks. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 El 2015-09-23 a las 08:59 +0200, buhorojo escribió:
On 22/09/15 18:39, Carlos E. R. wrote:
Just tap on NM applet to disconnect, then again to connect. The connection is reevaluated. Hi Yes, of course. We didn't know it was tappable. It looks like 3 taps. tap the icon. tap disconnect. tap the room you are in. Is there any way we can get the list after the disconnect in order of signal strength I wonder. Anyway, great post. Thanks.
Thanks :-) Well, yes, not a /single/ tap :-) I don't think NM gives strength information or sorting. There are cute applications on Windows and Android that display visually the signal strength and bandwidth of the nearby wifi access points. I'm not aware of a similar application available on the distribution, although there have been attempts to create one. So, maybe if we can find such an application, your users could run it, then choose an AP. Not automatically, though. I lost interest in them when I found a suitable app for my cheap android tablet... (Wifi Analyzer). It doesn't require to be connected to display nearby signal, but it does need WiFi to be active, of course. In Linux there are text applications. iwlist wlan peers, perhaps. Ah! I found a GUI one: iwScanner. But the information is given as a text table, not as a graph. Mmm... I found a few near me without encryption... Perhaps I can do downloads instead of using my phone theter... :-)~~ (slurp) - -- Cheers Carlos E. R. (from 13.1 x86_64 "Bottle" (Minas Tirith)) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iF4EAREIAAYFAlYClC4ACgkQja8UbcUWM1y6DQD+LBXRyMrInC7FztF92Y5Lf5rB fCkmQ6G13291R1FvUGkA/A5p5/mj/txYzI9benCQTeU8OBRL88DnnmxU13SQarmz =kOpP -----END PGP SIGNATURE-----
* Carlos E. R. <robin.listas@telefonica.net> [09-23-15 08:00]:
El 2015-09-23 a las 08:59 +0200, buhorojo escribió:
On 22/09/15 18:39, Carlos E. R. wrote:
Just tap on NM applet to disconnect, then again to connect. The connection is reevaluated. Hi Yes, of course. We didn't know it was tappable. It looks like 3 taps. tap the icon. tap disconnect. tap the room you are in. Is there any way we can get the list after the disconnect in order of signal strength I wonder. Anyway, great post. Thanks.
Thanks :-)
Well, yes, not a /single/ tap :-)
I don't think NM gives strength information or sorting.
There are cute applications on Windows and Android that display visually the signal strength and bandwidth of the nearby wifi access points. I'm not aware of a similar application available on the distribution, although there have been attempts to create one.
So, maybe if we can find such an application, your users could run it, then choose an AP. Not automatically, though.
I lost interest in them when I found a suitable app for my cheap android tablet... (Wifi Analyzer). It doesn't require to be connected to display nearby signal, but it does need WiFi to be active, of course.
In Linux there are text applications.
iwlist wlan peers, perhaps.
Ah! I found a GUI one: iwScanner. But the information is given as a text table, not as a graph. Mmm... I found a few near me without encryption... Perhaps I can do downloads instead of using my phone theter... :-)~~ (slurp)
iwlist <dev> scan provides Quality and Signal level and ESSID Quality=69/70 Signal level=-41 dBm ESSID:"2WIRE577" ## neighbor's wireless but would require some scripting to provide *only* desired information. -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri http://wahoo.no-ip.org Photo Album: http://wahoo.no-ip.org/gallery2 Registered Linux User #207535 @ http://linuxcounter.net -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Content-ID: <alpine.LSU.2.11.1509231443470.24753@minas-tirith.valinor> El 2015-09-23 a las 08:23 -0400, Patrick Shanahan escribió:
iwlist <dev> scan provides Quality and Signal level and ESSID Quality=69/70 Signal level=-41 dBm ESSID:"2WIRE577" ## neighbor's wireless
cer@minas-tirith:~> iwlist wlan scan wlan Interface doesn't support scanning. cer@minas-tirith:~> (same as root) which is false, I believe. The issue is, I think, that I'm not connected to any AP at the moment. But iwScanner lists them without problems. - -- Cheers Carlos E. R. (from 13.1 x86_64 "Bottle" (Minas Tirith)) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iF4EAREIAAYFAlYCnt4ACgkQja8UbcUWM1xBKgD/caNo4uBJLZh8czA60WNX27Aq Msnv6d9YAeo1CJjcty4A/23z+1VhJiutloFPlx6udJiGW+04hfd5lahg+/SNI+CD =bLUh -----END PGP SIGNATURE-----
* Carlos E. R. <robin.listas@telefonica.net> [09-23-15 08:45]:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256
Content-ID: <alpine.LSU.2.11.1509231443470.24753@minas-tirith.valinor>
El 2015-09-23 a las 08:23 -0400, Patrick Shanahan escribió:
iwlist <dev> scan provides Quality and Signal level and ESSID Quality=69/70 Signal level=-41 dBm ESSID:"2WIRE577" ## neighbor's wireless
cer@minas-tirith:~> iwlist wlan scan wlan Interface doesn't support scanning.
cer@minas-tirith:~>
(same as root)
which is false, I believe. The issue is, I think, that I'm not connected to any AP at the moment. But iwScanner lists them without problems.
iwlist <dev> scan insert bit smilie here iwlist wlp3s0 scan might work better as <dev> is *not* an interface :) -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri http://wahoo.no-ip.org Photo Album: http://wahoo.no-ip.org/gallery2 Registered Linux User #207535 @ http://linuxcounter.net -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 El 2015-09-23 a las 09:09 -0400, Patrick Shanahan escribió:
iwlist <dev> scan insert bit smilie here iwlist wlp3s0 scan
might work better as <dev> is *not* an interface :)
Ah. Well, it is wlan0 here. It was missing the '0'. The output is wayyy verbose. - -- Cheers Carlos E. R. (from 13.1 x86_64 "Bottle" (Minas Tirith)) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iF4EAREIAAYFAlYC0H0ACgkQja8UbcUWM1ysEAD/dN3fkIQeWwJ/s7MCU+cBjRMc DKW6FpxAdNYdv2YoYEEA/0WI1GILlW5XIH050bf1zScJ5UX/6lnvfWJRwexBZq61 =gm8O -----END PGP SIGNATURE-----
On 23/09/15 13:59, Carlos E. R. wrote:
Ah! I found a GUI one: iwScanner. But the information is given as a text table, not as a graph. Mmm... I found a few near me without encryption... Perhaps I can do downloads instead of using my phone theter... :-)~~ (slurp)
Yes. Are you still in Spain? Hint: A while ago all the Jaz?t??? installs seemed to be open until secured by the user, requiring the latter to refer to the ruter instructions to set it. Use your imagination LOL! HTH -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 El 2015-09-23 a las 21:02 +0200, buhorojo escribió:
On 23/09/15 13:59, Carlos E. R. wrote:
Ah! I found a GUI one: iwScanner. But the information is given as a text table, not as a graph. Mmm... I found a few near me without encryption... Perhaps I can do downloads instead of using my phone theter... :-)~~ (slurp)
Yes. Are you still in Spain? Hint: A while ago all the Jaz?t??? installs seemed to be open until secured by the user, requiring the latter to refer to the ruter instructions to set it. Use your imagination LOL! HTH
LOL :-) In this case they seem to be installs made by a local, small, internet provider that works around La Manga. I think they connect by some kind of long distance wireless, then setup a router with WiFi on each customer's house. It is an alternative, low cost connection, without a phone line. Guessing. - -- Cheers Carlos E. R. (from 13.1 x86_64 "Bottle" (Minas Tirith)) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iF4EAREIAAYFAlYDIAoACgkQja8UbcUWM1wxgQD/TV/RyQk0haV6QrZ3v0+Y2KXp 507cLnM8vLRYbLCy+ggA/A91wKi8meLSn0DudnZ60c5908G+GphhsPxe5kmQ88Tu =6EuC -----END PGP SIGNATURE-----
On 23/09/15 23:56, Carlos E. R. wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256
El 2015-09-23 a las 21:02 +0200, buhorojo escribió:
On 23/09/15 13:59, Carlos E. R. wrote:
Ah! I found a GUI one: iwScanner. But the information is given as a text table, not as a graph. Mmm... I found a few near me without encryption... Perhaps I can do downloads instead of using my phone theter... :-)~~ (slurp)
Yes. Are you still in Spain? Hint: A while ago all the Jaz?t??? installs seemed to be open until secured by the user, requiring the latter to refer to the ruter instructions to set it. Use your imagination LOL! HTH
LOL :-)
In this case they seem to be installs made by a local, small, internet provider that works around La Manga. I think they connect by some kind of long distance wireless, then setup a router with WiFi on each customer's house. It is an alternative, low cost connection, without a phone line.
Guessing.
Not far away. Altea: We have Vodafone at home where you type 192.168.0.1 to get at the box. and fibra at school to which we've added a similar box in each room. Absolutely zero idea how either of them work. We thought they were going to come back and make it wireless everywhere but they never. Instead we have the old windows domain cables to each room to which we've added an adsl router with 'phone input taped over acting as a switch and then a netgear wireless ethernet router on top. Had the Director not have said 'it'll never work', it would never have worked. ¡Ingeniería española por excelencia! -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 El 2015-09-20 a las 10:46 -0400, James Knott escribió:
On 09/20/2015 10:39 AM, Carlos E. R. wrote:
If students on room 1 should use only the AP in room 1, then you should have different SSID for each room.
That's contrary to good practice, unless there's some reason to keep the traffic for a room isolated. It's more likely the students are using the same resources, no matter which class they're in.
Otherwise, who cares to which AP they connect? The computers will connect to the best one they can find.
The guy hiding in a back corner of a class might get a better signal from another AP than the one in his room. WiFi is designed for roaming among APs. It's the responsibility of the device to switch when necessary for a better signal. This is different from the cell phone network, where the network tells a phone to check other signals and move if necessary.
My points exactly :-) - -- Cheers Carlos E. R. (from 13.1 x86_64 "Bottle" (Minas Tirith)) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iF4EAREIAAYFAlX+8/QACgkQja8UbcUWM1z+HAD/TKkKJSgueFoMLCTf5oh5Rv6l m+K+LEel1CHJy0EvY0YA/1FLe7jNeQab5OD8wdQSegkLPJtASh1hJgcbtt+WzWt+ =Tczp -----END PGP SIGNATURE-----
On 9/20/2015 7:46 AM, James Knott wrote:
That's contrary to good practice,
Who gets to be the Arbiter of that? The fact of the matter is that there are very few situations where it matters one way or the other. -- _____________________________________ ---This space for rent--- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 09/20/2015 02:47 PM, John Andersen wrote:
On 9/20/2015 7:46 AM, James Knott wrote:
That's contrary to good practice, Who gets to be the Arbiter of that?
Well, Cisco for one.
The fact of the matter is that there are very few situations where it matters one way or the other.
If you want roaming, you need the same SSID. If you use different SSIDs, then the mobile device won't change access points until the signal drops so low as to be unusable. Only when it has lost the signal will it try connecting to another AP with a different SSID. When a single SSID is used for multiple APs, then roaming should be relatively smooth. It won't be with different SSIDs. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Sun, 20 Sep 2015, James Knott wrote:
On 09/20/2015 02:47 PM, John Andersen wrote:
On 9/20/2015 7:46 AM, James Knott wrote:
That's contrary to good practice, Who gets to be the Arbiter of that?
Well, Cisco for one.
Also, common sense. ;-).
The fact of the matter is that there are very few situations where it matters one way or the other.
It matters constantly, that's why they designed it like that. It's just common sense. A single SSID offered on a wider area requires occassional switching to use the AP that's in closest range. Or has the best signal. What's so hard about that? It's not even that advanced, although it requires a little bit of logic. You could probably code it up in a day if you wanted to and you were in that position. It's really simple. Collect list of neighbouring BSSIDS. Check signal strength of current connection. When it drops below a certain treshold and there are more attractive choices available, switch. Presto. Make sure you don't switch more than once every several seconds. And you've already got an almost fool-proof algorithm.
If you want roaming, you need the same SSID. If you use different SSIDs, then the mobile device won't change access points until the signal drops so low as to be unusable. Only when it has lost the signal will it try connecting to another AP with a different SSID. When a single SSID is used for multiple APs, then roaming should be relatively smooth. It won't be with different SSIDs.
-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 9/20/2015 12:03 PM, James Knott wrote:
then the mobile device won't change access points until the signal drops so low as to be unusable.
It doesn't do that NOW, which is the whole point of this thread. Unless some manual action is taken NetworkManager does not roam. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 20/09/15 21:03, James Knott wrote:
If you want roaming, you need the same SSID. If you use different SSIDs, then the mobile device won't change access points until the signal drops so low as to be unusable.
Thanks for all your comments. We have different ssid in each room but that's not what we see. The tablets change to the next room. opensuse doesn't. Anyway: workaroud is restarting network. So is it possible to have a one tap button on that does: systemctl restart network as a user? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
"Carlos E. R." <robin.listas@telefonica.net> schreef:
El 2015-09-20 a las 16:16 +0200, buhorojo escribió:
Say 15 laptops running Linux connect first lesson of the day in room 1. They stay connected all day. When the next class arrives it takes ages, so they connect to room 2 where there are also students connected. Tablets only is no problem. We've narrowed it to linux.
If students on room 1 should use only the AP in room 1, then you should have different SSID for each room.
Otherwise, who cares to which AP they connect? The computers will connect to the best one they can find.
Geography. It's a school topic :p. If the first batch of students is logged onto "room 1" and they move to another part of the building, their link will start to weaken but other students in room 1 now have to log on to an AP in room 2. After a while you get a very bad efficiency and what's more, you might get devices that cannot connect anywhere because all available APs are out of range. It is just regular practice for a wifi device to support this. It is basically just ridiculous (once again) that NetworkManager doesn't. No need to beat around the bush about it. There is no other solution that really suffices. Now I did notice at some point in my wpa_supplicant log output that there was an automatic changing of BSSID at some point but I can be mistaken, I did not pay a lot of attention to that. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Sun, Sep 20, 2015 at 9:44 AM, Xen <list@xenhideout.nl> wrote:
It is just regular practice for a wifi device to support this. It is basically just ridiculous (once again) that NetworkManager doesn't. No need to beat around the bush about it. There is no other solution that really suffices.
I'll just leave it at this. I couldn't tell if this discussion was about switching SSIDs or BSSIDs based on signal strength. I studied and worked at a university campus with an enrollment of 60,000 people occupying a little less than a single square mile. I couldn't even start to estimate the number of access points in place to support such density. There has to be thousands of enterprise grade access points in place. Some buildings have an access point every ten to fifteen feet. Each access point runs three SSIDs which are spanned over the entire campus. I haven't dug into the code of wpa_supplicant or NetworkManager, but from my experience NetworkManager would associate with a single BSSID and wait for the signal to become unusable before disconnecting and establishing a connection with a closer and stronger BSSID. This means that I would connect to one of the SSIDs, move slightly down the hall and NetworkManager would continue to try to use the original BSSID (albeit having virtually no usable signal). NetworkManager would become so confused it required a restart. This happened on about six to seven GNU/Linux distributions. Brandon Vincent -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 El 2015-09-20 a las 10:06 -0700, Brandon Vincent escribió:
This means that I would connect to one of the SSIDs, move slightly down the hall and NetworkManager would continue to try to use the original BSSID (albeit having virtually no usable signal). NetworkManager would become so confused it required a restart. This happened on about six to seven GNU/Linux distributions.
I think that simply telling NM to disconnect from the current network, then to reconnect, works. In my home, it switched to another one sometimes. - -- Cheers Carlos E. R. (from 13.1 x86_64 "Bottle" (Minas Tirith)) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iF4EAREIAAYFAlX+9QkACgkQja8UbcUWM1z/8wD/a+B/ezo1Aj6DI8fAdl575F8u Hg8DvRiHG7BF4GZ089oA/RTd444CpeuT5VUj+UnoQcIrxLpopuQDIt9nywDhcZUn =0FBk -----END PGP SIGNATURE-----
On Sun, Sep 20, 2015 at 11:03 AM, Carlos E. R. <robin.listas@telefonica.net> wrote:
I think that simply telling NM to disconnect from the current network, then to reconnect, works. In my home, it switched to another one sometimes.
That used to work, but I think one of the issues with later versions of NetworkManager is that it doesn't like the fact that there are sometimes 20+ BSSIDs with the same SSID around me. Brandon Vincent -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 El 2015-09-20 a las 11:06 -0700, Brandon Vincent escribió:
On Sun, Sep 20, 2015 at 11:03 AM, Carlos E. R. wrote:
I think that simply telling NM to disconnect from the current network, then to reconnect, works. In my home, it switched to another one sometimes.
That used to work, but I think one of the issues with later versions of NetworkManager is that it doesn't like the fact that there are sometimes 20+ BSSIDs with the same SSID around me.
Oh. I only had two :-) - -- Cheers Carlos E. R. (from 13.1 x86_64 "Bottle" (Minas Tirith)) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iF0EAREIAAYFAlX/HJwACgkQja8UbcUWM1zyaQD4+OQ2CXvl4ySBNWU9azm0Ky5M JZxDEyeW/5oeZvwSUwD/TA0rxHJrCc7jktOyrwkeejJTXcKQIlD21L1VFTalDaY= =gz2j -----END PGP SIGNATURE-----
On 20/09/15 19:06, Brandon Vincent wrote:
On Sun, Sep 20, 2015 at 9:44 AM, Xen <list@xenhideout.nl> wrote:
It is just regular practice for a wifi device to support this. It is basically just ridiculous (once again) that NetworkManager doesn't. No need to beat around the bush about it. There is no other solution that really suffices. I'll just leave it at this. I couldn't tell if this discussion was about switching SSIDs or BSSIDs based on signal strength.
Hi I think we got knocked off course. We began the thread but don't understand where it has gone..
I studied and worked at a university campus with an enrollment of 60,000 people occupying a little less than a single square mile. I couldn't even start to estimate the number of access points in place to support such density. There has to be thousands of enterprise grade access points in place. Some buildings have an access point every ten to fifteen feet. Each access point runs three SSIDs which are spanned over the entire campus. I haven't dug into the code of wpa_supplicant or NetworkManager, but from my experience NetworkManager would associate with a single BSSID and wait for the signal to become unusable before disconnecting and establishing a connection with a closer and stronger BSSID.
This means that I would connect to one of the SSIDs, move slightly down the hall and NetworkManager would continue to try to use the original BSSID (albeit having virtually no usable signal). NetworkManager would become so confused it required a restart. This happened on about six to seven GNU/Linux distributions.
Brandon Vincent I think the conclusion is that we can't roam on Linux. We have a workaround so just need help setting it up. It's exactly the latter. We need a one tap button that restarts the network. Thanks. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Tue, Sep 22, 2015 at 10:28 AM, buhorojo <buhorojo.lcb@gmail.com> wrote:
On 20/09/15 19:06, Brandon Vincent wrote:
On Sun, Sep 20, 2015 at 9:44 AM, Xen <list@xenhideout.nl> wrote:
It is just regular practice for a wifi device to support this. It is basically just ridiculous (once again) that NetworkManager doesn't. No need to beat around the bush about it. There is no other solution that really suffices.
I'll just leave it at this. I couldn't tell if this discussion was about switching SSIDs or BSSIDs based on signal strength.
Hi I think we got knocked off course. We began the thread but don't understand where it has gone..
The conversation split based on if the SSID was the same in the 2 rooms or different. Auto-switching not working would likely only be considered a bug if they are the same.
I think the conclusion is that we can't roam on Linux. We have a workaround so just need help setting it up. It's exactly the latter. We need a one tap button that restarts the network.
Sorry, I don't do GUI customization. Hopefully someone else can help.
Thanks.
Greg -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 22/09/15 17:01, Greg Freemyer wrote:
On Tue, Sep 22, 2015 at 10:28 AM, buhorojo <buhorojo.lcb@gmail.com> wrote:
On 20/09/15 19:06, Brandon Vincent wrote:
On Sun, Sep 20, 2015 at 9:44 AM, Xen <list@xenhideout.nl> wrote:
It is just regular practice for a wifi device to support this. It is basically just ridiculous (once again) that NetworkManager doesn't. No need to beat around the bush about it. There is no other solution that really suffices. I'll just leave it at this. I couldn't tell if this discussion was about switching SSIDs or BSSIDs based on signal strength.
Hi I think we got knocked off course. We began the thread but don't understand where it has gone.. The conversation split based on if the SSID was the same in the 2 rooms or different.
Auto-switching not working would likely only be considered a bug if they are the same. Our linux laptops never change, same ssid or not.
Brandon posted this earlier so it seems to have been accepted: https://bugzilla.gnome.org/show_bug.cgi?id=737356 Just no takers yet. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 El 2015-09-22 a las 17:22 +0200, buhorojo escribió:
On 22/09/15 17:01, Greg Freemyer wrote:
The conversation split based on if the SSID was the same in the 2 rooms or different.
Auto-switching not working would likely only be considered a bug if they are the same.
Our linux laptops never change, same ssid or not.
If the SSIDs are different, then the correct behaviour is what happens now: no automatic switching to another AP. If the SSIDs are the same, automatic switching should occur when the conditions at the current AP are bad enough, like lost packages. The signal been weak, or stronger in another AP is not enough. That is, roaming. - -- Cheers Carlos E. R. (from 13.1 x86_64 "Bottle" (Minas Tirith)) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iF4EAREIAAYFAlYBg/IACgkQja8UbcUWM1ztigD6AomaDebIwpSQSTbVM1hIECdX AKp5oZqszBHDCR9qLjcA/1AH1n61BnXfyZwWfOlMz+5QFi7z4J6ofRWw+sQgixJd =Y5Lp -----END PGP SIGNATURE-----
On Sat, Sep 19, 2015 at 12:07 PM, John Andersen <jsamyth@gmail.com> wrote:
Why would you have to restart network manager?
On most distributions by default (if you are not using Wicked), NetworkManager is what is responsible for setting up and configuring network interfaces. It doesn't just provide a graphical front end. The ability to select a SSID based on its signal strength is a feature that has not yet been included yet in NetworkManager. See my original post. Brandon Vincent -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 09/19/2015 12:14 PM, Brandon Vincent wrote:
NetworkManager is what is responsible for setting up and configuring network interfaces. It doesn't just provide a graphical front end.
KDE supplies a graphical frontend for NetworkManager. We are here talking about Opensuse, not some other distribution. -- After all is said and done, more is said than done.
On Sat, Sep 19, 2015 at 12:30 PM, John Andersen <jsamyth@gmail.com> wrote:
KDE supplies a graphical frontend for NetworkManager. We are here talking about Opensuse, not some other distribution.
That graphical front end is the standard KDE applet for NetworkManager. If any logic would be implemented for automatically switching networks based on signal strength, it would be built into the core of the NetworkManager daemon. This makes it easy for UI/UX developers not to have to worry about cross-platform behavior. I don't know how much logic if any exists in the front ends for NetworkManager. Brandon Vincent -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 09/19/2015 12:52 PM, Brandon Vincent wrote:
I don't know how much logic if any exists in the front ends for NetworkManager.
Well that's the root of the problem, as best I can tell. NetworkManager doesn't have such capabilities yet. It was posted up-thread that this capability is still missing from NM, but was being worked on. I haven't seen much progress of late. -- After all is said and done, more is said than done. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 09/19/2015 04:31 PM, John Andersen wrote:
I don't know how much logic if any exists in the front ends for NetworkManager. Well that's the root of the problem, as best I can tell. NetworkManager doesn't have such capabilities yet.
Is it NetworkManager that should be handling this or something closer to the hardware? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Sat, Sep 19, 2015 at 2:15 PM, James Knott <james.knott@rogers.com> wrote:
Is it NetworkManager that should be handling this or something closer to the hardware?
Before this can be considered, one needs to consider that a lot of the wireless drivers in the kernel do not provide accurate or reliable signal strengths. The backend of NetworkManager is what should be handling this. Brandon Vincent -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Sat, 19 Sep 2015, Brandon Vincent wrote:
I don't know how much logic if any exists in the front ends for NetworkManager.
Probably not much or nothing at all. The plasma frontend also displays not any error messages; you have to look at the syslog/journalctl. [ Habitually checks the network manager icon but is using Windows :p ]. Btw, OpenSUSE 13.2 features a version below 1.0 (0.9...) but version 1.0 is available. It fixes several limitations that I know of: being able to use "cipher none" for OpenVPN and it has a IP4_GATEWAY (or IPV4_GATEWAY) variable that you can use for VPN scripts for setting up routes. Who knows what else has improved. The designers respond to mailing list messages very well. networkmanager-list@gnome.org. Not that it necessarily means much. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 19/09/15 21:30, John Andersen wrote:
On 09/19/2015 12:14 PM, Brandon Vincent wrote:
NetworkManager is what is responsible for setting up and configuring network interfaces. It doesn't just provide a graphical front end. KDE supplies a graphical frontend for NetworkManager. We are here talking about Opensuse, not some other distribution.
Hi Thanks. It's the same on lxde. The problem is it's 2 taps and you have to know the ssid. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 09/19/2015 01:06 PM, buhorojo wrote:
On 19/09/15 21:30, John Andersen wrote:
On 09/19/2015 12:14 PM, Brandon Vincent wrote:
NetworkManager is what is responsible for setting up and configuring network interfaces. It doesn't just provide a graphical front end. KDE supplies a graphical frontend for NetworkManager. We are here talking about Opensuse, not some other distribution.
Hi Thanks. It's the same on lxde. The problem is it's 2 taps and you have to know the ssid.
The problem is that its still manual, not automatic roaming. But I believe that it was posted early in the thread that automatic roaming capability is coming to NM eventually. As for knowing the SSID, typically you would, wouldn't you? In a roaming situation (multiple classrooms) its common for all the SSIDs to be the same, allowing ease of roaming. Its just that Network Manager doesn't do that on its own, as it should. (yet). -- After all is said and done, more is said than done. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 09/19/2015 03:30 PM, John Andersen wrote:
KDE supplies a graphical frontend for NetworkManager. We are here talking about Opensuse, not some other distribution.
I'm curious as to why that shows 2 vmnet8 connections. Is it on 2 bands? I just tried an experiment. I have 2 portable access points, both on 2.7 GHz, that have the same SSID and password. On KDE/openSUSE 13.1, I see only the one SSID and no way to select one of the 2 APs. On the other hand, with WiFi Analyzer on my Android phone, the SSID has a little "twisty" triange next to it and if I click on it, I see both APs listed. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 09/19/2015 02:10 PM, James Knott wrote:
On 09/19/2015 03:30 PM, John Andersen wrote:
KDE supplies a graphical frontend for NetworkManager. We are here talking about Opensuse, not some other distribution.
I'm curious as to why that shows 2 vmnet8 connections. Is it on 2 bands? I just tried an experiment. I have 2 portable access points, both on 2.7 GHz, that have the same SSID and password. On KDE/openSUSE 13.1, I see only the one SSID and no way to select one of the 2 APs. On the other hand, with WiFi Analyzer on my Android phone, the SSID has a little "twisty" triange next to it and if I click on it, I see both APs listed.
Those are not germane to this discussion as they are not WIFI access points. They are virtual adapters for VMware virtual networks with which the host (this machine) can talk to the Virtual machines. -- After all is said and done, more is said than done. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Sat, Sep 19, 2015 at 12:07 PM, John Andersen <jsamyth@gmail.com> wrote:
Why would you have to restart network manager?
Sorry John about my tone in my last response. I was letting buhorojo know that restating the "network" service would do nothing. If anything he would be restarting NetworkManager (which was what I was attempting to communicate to him) but it would only cause the system to disassociate and associate with previously known SSIDs/APs by their profile rather than signal strength. Brandon Vincent -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 El 2015-09-19 a las 12:18 -0700, Brandon Vincent escribió:
Sorry John about my tone in my last response. I was letting buhorojo know that restating the "network" service would do nothing. If anything he would be restarting NetworkManager (which was what I was attempting to communicate to him) but it would only cause the system to disassociate and associate with previously known SSIDs/APs by their profile rather than signal strength.
For some time I had two AP with the same SSID at home. When I resumed the laptop it associated often with the worst choice, and restarting network made it reevaluate and use the best. Clicking about on NM (xfce, 13.1) also worked. But there is no easy way to distinguish which AP you are actually using. - -- Cheers Carlos E. R. (from 13.1 x86_64 "Bottle" (Minas Tirith)) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iF4EAREIAAYFAlX+pC0ACgkQja8UbcUWM1y6PwEAi3xa9PmOXVL4jD25l7URtoQX cviewLIxcCL1NRqQSIwA/idZ+gOpG0O+NCfIHuLw3eCK9LjFH15kGZ6VN+LZyEas =vmf8 -----END PGP SIGNATURE-----
On 09/19/2015 03:07 PM, John Andersen wrote:
The network manager tray widget shows all available connections, and you can simply click the on you want to connect to.
If you have something different to click on, then the access points have different SSIDs, which is not the proper way to do things. For roaming to work properly, all access points on a network should have the same SSID and the mobile devices is supposed to select the one with the best signal. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 09/18/2015 04:09 PM, buhorojo wrote:
Hi We have a series of rooms with wifi. If we walk from one room to the next, a phone or an ipad will use the wifi in the new room. An opensuse 13.2 laptop doesn't do that. You connect to room one and you stay with room one all day unless you walk out of range or reboot. Is there a way we can make the opensuse change as per the phones?
We think the relevant part is NetworkManager Applet 0.9.10.0 but don't know where to start. Thanks
Are you sure you want to change the SSID? Normally, if you have more than one access point on a network, they'd all have the same SSID and password. However, each access point would have it's own BSSID, which contains the MAC address. So, as you're moving around, the BSSID would change, but the SSID wouldn't. You normally don't even see the BSSID, just the SSID. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
participants (11)
-
Brandon Vincent -
buhorojo -
Carlos E. R. -
Doug -
Greg Freemyer -
greg.freemyer＠gmail.com
-
James Knott -
John Andersen -
John M Andersen
-
Patrick Shanahan -
Xen