Re: WiFi: Problem with Entreprise networks (with multiple routers)
On mar, 2013-10-22 at 09:43 -0500, Dan Williams wrote: On Tue, 2013-10-22 at 13:51 +0200, Matthieu Baerts wrote: On lun, 2013-10-14 at 19:49 +0200, Matthieu Baerts wrote: On lun, 2013-10-14 at 12:20 -0500, Dan Williams wrote: On Mon, 2013-10-14 at 18:39 +0200, Matthieu Baerts wrote: Hello Dan and thank you for this answer, On Mon, 2013-10-14 at 09:41 -0500, Dan Williams wrote: This problem is most definitely a supplicant issue. The supplicant roams too aggressively, even if the currently associated access point has a very good signal. We've patched that in Fedora, but as you indicate, your kernel wifi driver is also not working correctly when reporting signal strength. Thank you for these details! Do you know if it's possible to configure wpa_supplicant (via NM or not) to be less aggressive but without having to patch it? (or to force it to not switch between access points?). I know that we can force wpa_supplication to try to connect to a specific access point (by using the mac address) but it's not what I want: I don't want to change the settings each time I want to connect to a different access point of this network. Correct, you want to keep roaming enabled, and that's not possible (obviously) when locking to a specific access point. There a few things that will make this better: 1) Apply the following patch to your wpa_supplicant, which will make the problem much better but http://pkgs.fedoraproject.org/cgit/wpa_supplicant.git/tree/rh837402-less-aggressive-roaming.patch 2) Apply the following commit to your NetworkManager packages, which requests that the supplicant scan for roaming a little less often: http://cgit.freedesktop.org/NetworkManager/NetworkManager/commit/?id=dd9cf657ef1f9d5909dad2eb697098715325fecf 3) Wait for some upstream changes to the supplicant, which will include *some* form of the above patch, as well as one I posted upstream to request the supplicant not to roam as a result of an information-only scan that NetworkManager periodically does. Thank you for these patches, I'll have a look asap! (but I'm not sure I'll be able to test it soon) Thank you, I confirm that it's much better with these patches! Obviously all these fixes depend on the kernel driver also reporting the signal strength correctly... Yes... Due to this problem with my drivers, I'm using this setting: bgscan = simple:30:-65:9000 But do you have any idea how I can use this setting without patching each new version of NM? NM uses -65 already in NetworkManager 0.9.8.4 and later. Which drivers are you using again? If they are in-tree ones, it would be much easier to get them fixed. Yes, you're right, I'll try to report this bug asap! I'm using rtl8192se module. That combined with the changes for periodic scanning not causing a roam (which was just applied upstream to wpa_supplicant) should help immensely. Yes I hope, good news :) Thank you for you help! Regards, Matt signature.asc Description: This is a digitally signed message part ___ networkmanager-list mailing list networkmanager-list@gnome.org https://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: WiFi: Problem with Entreprise networks (with multiple routers)
On sun, 2013-10-27 at 19:44 +0100, Matthieu Baerts wrote: On mar, 2013-10-22 at 09:43 -0500, Dan Williams wrote: NM uses -65 already in NetworkManager 0.9.8.4 and later. Which drivers are you using again? If they are in-tree ones, it would be much easier to get them fixed. Yes, you're right, I'll try to report this bug asap! Done! If someone else has this problem, he can track it there: https://bugzilla.kernel.org/show_bug.cgi?id=63881 signature.asc Description: This is a digitally signed message part ___ networkmanager-list mailing list networkmanager-list@gnome.org https://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: WiFi: Problem with Entreprise networks (with multiple routers)
On lun, 2013-10-14 at 19:49 +0200, Matthieu Baerts wrote: On lun, 2013-10-14 at 12:20 -0500, Dan Williams wrote: On Mon, 2013-10-14 at 18:39 +0200, Matthieu Baerts wrote: Hello Dan and thank you for this answer, On Mon, 2013-10-14 at 09:41 -0500, Dan Williams wrote: This problem is most definitely a supplicant issue. The supplicant roams too aggressively, even if the currently associated access point has a very good signal. We've patched that in Fedora, but as you indicate, your kernel wifi driver is also not working correctly when reporting signal strength. Thank you for these details! Do you know if it's possible to configure wpa_supplicant (via NM or not) to be less aggressive but without having to patch it? (or to force it to not switch between access points?). I know that we can force wpa_supplication to try to connect to a specific access point (by using the mac address) but it's not what I want: I don't want to change the settings each time I want to connect to a different access point of this network. Correct, you want to keep roaming enabled, and that's not possible (obviously) when locking to a specific access point. There a few things that will make this better: 1) Apply the following patch to your wpa_supplicant, which will make the problem much better but http://pkgs.fedoraproject.org/cgit/wpa_supplicant.git/tree/rh837402-less-aggressive-roaming.patch 2) Apply the following commit to your NetworkManager packages, which requests that the supplicant scan for roaming a little less often: http://cgit.freedesktop.org/NetworkManager/NetworkManager/commit/?id=dd9cf657ef1f9d5909dad2eb697098715325fecf 3) Wait for some upstream changes to the supplicant, which will include *some* form of the above patch, as well as one I posted upstream to request the supplicant not to roam as a result of an information-only scan that NetworkManager periodically does. Thank you for these patches, I'll have a look asap! (but I'm not sure I'll be able to test it soon) Thank you, I confirm that it's much better with these patches! Obviously all these fixes depend on the kernel driver also reporting the signal strength correctly... Yes... Due to this problem with my drivers, I'm using this setting: bgscan = simple:30:-65:9000 But do you have any idea how I can use this setting without patching each new version of NM? Regards, Matt signature.asc Description: This is a digitally signed message part ___ networkmanager-list mailing list networkmanager-list@gnome.org https://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: WiFi: Problem with Entreprise networks (with multiple routers)
On Tue, 2013-10-22 at 13:51 +0200, Matthieu Baerts wrote: On lun, 2013-10-14 at 19:49 +0200, Matthieu Baerts wrote: On lun, 2013-10-14 at 12:20 -0500, Dan Williams wrote: On Mon, 2013-10-14 at 18:39 +0200, Matthieu Baerts wrote: Hello Dan and thank you for this answer, On Mon, 2013-10-14 at 09:41 -0500, Dan Williams wrote: This problem is most definitely a supplicant issue. The supplicant roams too aggressively, even if the currently associated access point has a very good signal. We've patched that in Fedora, but as you indicate, your kernel wifi driver is also not working correctly when reporting signal strength. Thank you for these details! Do you know if it's possible to configure wpa_supplicant (via NM or not) to be less aggressive but without having to patch it? (or to force it to not switch between access points?). I know that we can force wpa_supplication to try to connect to a specific access point (by using the mac address) but it's not what I want: I don't want to change the settings each time I want to connect to a different access point of this network. Correct, you want to keep roaming enabled, and that's not possible (obviously) when locking to a specific access point. There a few things that will make this better: 1) Apply the following patch to your wpa_supplicant, which will make the problem much better but http://pkgs.fedoraproject.org/cgit/wpa_supplicant.git/tree/rh837402-less-aggressive-roaming.patch 2) Apply the following commit to your NetworkManager packages, which requests that the supplicant scan for roaming a little less often: http://cgit.freedesktop.org/NetworkManager/NetworkManager/commit/?id=dd9cf657ef1f9d5909dad2eb697098715325fecf 3) Wait for some upstream changes to the supplicant, which will include *some* form of the above patch, as well as one I posted upstream to request the supplicant not to roam as a result of an information-only scan that NetworkManager periodically does. Thank you for these patches, I'll have a look asap! (but I'm not sure I'll be able to test it soon) Thank you, I confirm that it's much better with these patches! Obviously all these fixes depend on the kernel driver also reporting the signal strength correctly... Yes... Due to this problem with my drivers, I'm using this setting: bgscan = simple:30:-65:9000 But do you have any idea how I can use this setting without patching each new version of NM? NM uses -65 already in NetworkManager 0.9.8.4 and later. Which drivers are you using again? If they are in-tree ones, it would be much easier to get them fixed. That combined with the changes for periodic scanning not causing a roam (which was just applied upstream to wpa_supplicant) should help immensely. Dan ___ networkmanager-list mailing list networkmanager-list@gnome.org https://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: WiFi: Problem with Entreprise networks (with multiple routers)
- Original Message - From: Matthieu Baerts matt...@gmail.com To: networkmanager-list networkmanager-list@gnome.org Sent: Thursday, October 10, 2013 6:23:03 PM Subject: WiFi: Problem with Entreprise networks (with multiple routers) Hello, Firstly, thank you for developing and maintaining NetworkManager! I'm using NetworkManager on my campus' WiFi (WPA2 Enterprise with PEAP and MSCHAPv2) and I've a problem only with this network: after a few time, I'm disconnected or I'm still connected but I can no longer ping a random server. Note I'm not the only one which is using NM and which has this problem. I don't have any other OS on my computer but it seems there are less problem when using another OS (e.g. MacOSX) or another network manager (e.g. Wicd). I suspect that NM often switches from a router to another one (there are always a few WiFi routers around me with the same name and using the same network) and my drivers, my WiFi card and/or the routers/network don't support that. It's more about multiple access points than multiple routers, then? If I'm just next to a router (when the signal level is ~100%), it seems that I don't have this problem. Also, I think that my WiFi driver doesn't detect very well the quality/signal level of non connected routers (many routers have a signal level of 100% even if they are not next to me). Is there a way to configure NM to be less aggressive when switching between routers? (e.g. only switch if we're about to be disconnected and not just to have the router with the higher signal level?) Or an option to just disable this feature? (I didn't find any option about that, sorry if I miss something!) Sounds more like wpa_supplicant or the driver. You'd have to know what exactly you expect from NetworkManager, i.e. how exactly its communication to wpa_supplicant differs from that of Wicd. I'm not a Wi-Fi guru, though. Cheers, Pavel ___ networkmanager-list mailing list networkmanager-list@gnome.org https://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: WiFi: Problem with Entreprise networks (with multiple routers)
On Mon, 2013-10-14 at 03:36 -0400, Pavel Simerda wrote: - Original Message - From: Matthieu Baerts matt...@gmail.com To: networkmanager-list networkmanager-list@gnome.org Sent: Thursday, October 10, 2013 6:23:03 PM Subject: WiFi: Problem with Entreprise networks (with multiple routers) Hello, Firstly, thank you for developing and maintaining NetworkManager! I'm using NetworkManager on my campus' WiFi (WPA2 Enterprise with PEAP and MSCHAPv2) and I've a problem only with this network: after a few time, I'm disconnected or I'm still connected but I can no longer ping a random server. Note I'm not the only one which is using NM and which has this problem. I don't have any other OS on my computer but it seems there are less problem when using another OS (e.g. MacOSX) or another network manager (e.g. Wicd). I suspect that NM often switches from a router to another one (there are always a few WiFi routers around me with the same name and using the same network) and my drivers, my WiFi card and/or the routers/network don't support that. It's more about multiple access points than multiple routers, then? If I'm just next to a router (when the signal level is ~100%), it seems that I don't have this problem. Also, I think that my WiFi driver doesn't detect very well the quality/signal level of non connected routers (many routers have a signal level of 100% even if they are not next to me). Is there a way to configure NM to be less aggressive when switching between routers? (e.g. only switch if we're about to be disconnected and not just to have the router with the higher signal level?) Or an option to just disable this feature? (I didn't find any option about that, sorry if I miss something!) Sounds more like wpa_supplicant or the driver. You'd have to know what exactly you expect from NetworkManager, i.e. how exactly its communication to wpa_supplicant differs from that of Wicd. I'm not a Wi-Fi guru, though. This problem is most definitely a supplicant issue. The supplicant roams too aggressively, even if the currently associated access point has a very good signal. We've patched that in Fedora, but as you indicate, your kernel wifi driver is also not working correctly when reporting signal strength. Dan ___ networkmanager-list mailing list networkmanager-list@gnome.org https://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: WiFi: Problem with Entreprise networks (with multiple routers)
Hello and thank you for this answer, On lun, 2013-10-14 at 03:36 -0400, Pavel Simerda wrote: - Original Message - I suspect that NM often switches from a router to another one (there are always a few WiFi routers around me with the same name and using the same network) and my drivers, my WiFi card and/or the routers/network don't support that. It's more about multiple access points than multiple routers, then? Yes, you're right, sorry! If I'm just next to a router (when the signal level is ~100%), it seems that I don't have this problem. Also, I think that my WiFi driver doesn't detect very well the quality/signal level of non connected routers (many routers have a signal level of 100% even if they are not next to me). Is there a way to configure NM to be less aggressive when switching between routers? (e.g. only switch if we're about to be disconnected and not just to have the router with the higher signal level?) Or an option to just disable this feature? (I didn't find any option about that, sorry if I miss something!) Sounds more like wpa_supplicant or the driver. You'd have to know what exactly you expect from NetworkManager, i.e. how exactly its communication to wpa_supplicant differs from that of Wicd. I'm not a Wi-Fi guru, though. Yes, I want to know how exactly its communication to wpa_supplicant differs from that of Wicd. Or if we can configure wpa_supplicant to not switch between access points (and if yes, if it's possible to configure NM to use this option) Regards, Matt signature.asc Description: This is a digitally signed message part ___ networkmanager-list mailing list networkmanager-list@gnome.org https://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: WiFi: Problem with Entreprise networks (with multiple routers)
Hello Dan and thank you for this answer, On Mon, 2013-10-14 at 09:41 -0500, Dan Williams wrote: This problem is most definitely a supplicant issue. The supplicant roams too aggressively, even if the currently associated access point has a very good signal. We've patched that in Fedora, but as you indicate, your kernel wifi driver is also not working correctly when reporting signal strength. Thank you for these details! Do you know if it's possible to configure wpa_supplicant (via NM or not) to be less aggressive but without having to patch it? (or to force it to not switch between access points?). I know that we can force wpa_supplication to try to connect to a specific access point (by using the mac address) but it's not what I want: I don't want to change the settings each time I want to connect to a different access point of this network. Regards, Matt signature.asc Description: This is a digitally signed message part ___ networkmanager-list mailing list networkmanager-list@gnome.org https://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: WiFi: Problem with Entreprise networks (with multiple routers)
On Mon, 2013-10-14 at 18:39 +0200, Matthieu Baerts wrote: Hello Dan and thank you for this answer, On Mon, 2013-10-14 at 09:41 -0500, Dan Williams wrote: This problem is most definitely a supplicant issue. The supplicant roams too aggressively, even if the currently associated access point has a very good signal. We've patched that in Fedora, but as you indicate, your kernel wifi driver is also not working correctly when reporting signal strength. Thank you for these details! Do you know if it's possible to configure wpa_supplicant (via NM or not) to be less aggressive but without having to patch it? (or to force it to not switch between access points?). I know that we can force wpa_supplication to try to connect to a specific access point (by using the mac address) but it's not what I want: I don't want to change the settings each time I want to connect to a different access point of this network. Correct, you want to keep roaming enabled, and that's not possible (obviously) when locking to a specific access point. There a few things that will make this better: 1) Apply the following patch to your wpa_supplicant, which will make the problem much better but http://pkgs.fedoraproject.org/cgit/wpa_supplicant.git/tree/rh837402-less-aggressive-roaming.patch 2) Apply the following commit to your NetworkManager packages, which requests that the supplicant scan for roaming a little less often: http://cgit.freedesktop.org/NetworkManager/NetworkManager/commit/?id=dd9cf657ef1f9d5909dad2eb697098715325fecf 3) Wait for some upstream changes to the supplicant, which will include *some* form of the above patch, as well as one I posted upstream to request the supplicant not to roam as a result of an information-only scan that NetworkManager periodically does. Obviously all these fixes depend on the kernel driver also reporting the signal strength correctly... Dan ___ networkmanager-list mailing list networkmanager-list@gnome.org https://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: WiFi: Problem with Entreprise networks (with multiple routers)
On lun, 2013-10-14 at 12:20 -0500, Dan Williams wrote: On Mon, 2013-10-14 at 18:39 +0200, Matthieu Baerts wrote: Hello Dan and thank you for this answer, On Mon, 2013-10-14 at 09:41 -0500, Dan Williams wrote: This problem is most definitely a supplicant issue. The supplicant roams too aggressively, even if the currently associated access point has a very good signal. We've patched that in Fedora, but as you indicate, your kernel wifi driver is also not working correctly when reporting signal strength. Thank you for these details! Do you know if it's possible to configure wpa_supplicant (via NM or not) to be less aggressive but without having to patch it? (or to force it to not switch between access points?). I know that we can force wpa_supplication to try to connect to a specific access point (by using the mac address) but it's not what I want: I don't want to change the settings each time I want to connect to a different access point of this network. Correct, you want to keep roaming enabled, and that's not possible (obviously) when locking to a specific access point. There a few things that will make this better: 1) Apply the following patch to your wpa_supplicant, which will make the problem much better but http://pkgs.fedoraproject.org/cgit/wpa_supplicant.git/tree/rh837402-less-aggressive-roaming.patch 2) Apply the following commit to your NetworkManager packages, which requests that the supplicant scan for roaming a little less often: http://cgit.freedesktop.org/NetworkManager/NetworkManager/commit/?id=dd9cf657ef1f9d5909dad2eb697098715325fecf 3) Wait for some upstream changes to the supplicant, which will include *some* form of the above patch, as well as one I posted upstream to request the supplicant not to roam as a result of an information-only scan that NetworkManager periodically does. Thank you for these patches, I'll have a look asap! (but I'm not sure I'll be able to test it soon) Obviously all these fixes depend on the kernel driver also reporting the signal strength correctly... Yes... I'm currently connected to an access point. iwlist gives me a list of 40 access points (each access point has 5 virtual interfaces). All non-connected access points have a quality of 70/70 and a signal level of 10 dBm. On the other hand, all 5 virtual interfaces of the current connected access point have a quality of 58/70 and a signal level of -52 dBm... So I guess your patch for NM should help me! Matt signature.asc Description: This is a digitally signed message part ___ networkmanager-list mailing list networkmanager-list@gnome.org https://mail.gnome.org/mailman/listinfo/networkmanager-list
WiFi: Problem with Entreprise networks (with multiple routers)
Hello, Firstly, thank you for developing and maintaining NetworkManager! I'm using NetworkManager on my campus' WiFi (WPA2 Enterprise with PEAP and MSCHAPv2) and I've a problem only with this network: after a few time, I'm disconnected or I'm still connected but I can no longer ping a random server. Note I'm not the only one which is using NM and which has this problem. I don't have any other OS on my computer but it seems there are less problem when using another OS (e.g. MacOSX) or another network manager (e.g. Wicd). I suspect that NM often switches from a router to another one (there are always a few WiFi routers around me with the same name and using the same network) and my drivers, my WiFi card and/or the routers/network don't support that. If I'm just next to a router (when the signal level is ~100%), it seems that I don't have this problem. Also, I think that my WiFi driver doesn't detect very well the quality/signal level of non connected routers (many routers have a signal level of 100% even if they are not next to me). Is there a way to configure NM to be less aggressive when switching between routers? (e.g. only switch if we're about to be disconnected and not just to have the router with the higher signal level?) Or an option to just disable this feature? (I didn't find any option about that, sorry if I miss something!) Or do you have any ideas to know what's the problem exactly? Regards, Matt signature.asc Description: This is a digitally signed message part ___ networkmanager-list mailing list networkmanager-list@gnome.org https://mail.gnome.org/mailman/listinfo/networkmanager-list
