Re: cannot add profiles for wired connections or connect to wireless after upgrading to 0.9.8.6
- Original Message - > From: "Mehmet Giritli" > To: networkmanager-list@gnome.org > Sent: Sunday, October 13, 2013 1:26:40 PM > Subject: cannot add profiles for wired connections or connect to wireless > after upgrading to 0.9.8.6 > > > Hi, > > I use gentoo and this problem was reported by me to the gentoo bugzilla. > But devs over there could not really figure out what the problem is, > hence this email. Please always provide a link when referring to external sources. > Oct 12 12:56:24 mordor NetworkManager[13390]: Error parsing file > '/etc/NetworkManager/NetworkManager.conf': No such file or directory This is non-fatal, afaik. > Oct 12 12:56:24 mordor NetworkManager[13390]: Error parsing file > '/etc/NetworkManager/NetworkManager.conf': No such file or directory Should be non-fatal as well (but should be reported as there's no need to read the file twice nor to report the error twice. I wonder whether that happens with git master. > Oct 12 12:56:24 mordor NetworkManager[13390]:keyfile: > parsing .keep_net-misc_networkmanager-0 ... > Oct 12 12:56:24 mordor NetworkManager[13390]: Connection failed to > verify: (unknown) Non-fatal, but NetworkManager shouldn't IMO read that file. > Oct 12 12:56:24 mordor NetworkManager[13390]: Error parsing file > '/etc/NetworkManager/NetworkManager.conf': No such file or directory Duplicate once again, non-fatal. > Oct 12 12:56:24 mordor NetworkManager[13390]: monitoring kernel > firmware directory '/lib/firmware'. > Oct 12 12:56:24 mordor NetworkManager[13390]: WiFi hardware radio > set enabled > Oct 12 12:56:24 mordor dbus-daemon[371]: dbus[371]: [system] > Successfully activated service 'org.freedesktop.NetworkManager' Now NetworkManager is ready! It has no connections, though, according to the logs. > Oct 12 12:56:24 mordor NetworkManager[13390]: Added default wired > connection 'Wired connection 1' A desktopy behavior of adding a default auto wired configuration at runtime... > state change: unmanaged -> unavailable (reason 'managed') [10 20 2] > Oct 12 12:56:24 mordor NetworkManager[13390]: (eth1): preparing > device. > Oct 12 12:56:24 mordor NetworkManager[13390]: (eth1): > deactivating device (reason 'managed') [2] Looks OK. > Oct 12 12:56:24 mordor NetworkManager[13390]: Added default wired > connection 'Wired connection 1' > for /sys/devices/pci:00/:00:09.0/:05:00.0/net/eth1 > Oct 12 12:56:24 mordor NetworkManager[13390]: Unknown setting > '802-3-ethernet' Sounds like the auto-generated connection fails to provide correct settings. please file a bug report for that with http://bugzilla.gnome.org/ and don't forget to specify the version of NetworkManager there. Please link it with the Gentoo bug in both directions. The rest are just consequences of the problem noted here. 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)
- Original Message - > From: "Matthieu Baerts" > To: "networkmanager-list" > 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: cannot add profiles for wired connections or connect to wireless after upgrading to 0.9.8.6
On Mon, 2013-10-14 at 03:32 -0400, Pavel Simerda wrote: > - Original Message - > > From: "Mehmet Giritli" > > To: networkmanager-list@gnome.org > > Sent: Sunday, October 13, 2013 1:26:40 PM > > Subject: cannot add profiles for wired connections or connect to wireless > > after upgrading to 0.9.8.6 > > > > > > Hi, > > > > I use gentoo and this problem was reported by me to the gentoo bugzilla. > > But devs over there could not really figure out what the problem is, > > hence this email. > > Please always provide a link when referring to external sources. Will do in the bug report, but here it is anyway: https://bugs.gentoo.org/show_bug.cgi?id=487496 > > Oct 12 12:56:24 mordor NetworkManager[13390]: Added default wired > > connection 'Wired connection 1' > > for /sys/devices/pci:00/:00:09.0/:05:00.0/net/eth1 > > Oct 12 12:56:24 mordor NetworkManager[13390]: Unknown setting > > '802-3-ethernet' > > Sounds like the auto-generated connection fails to provide correct settings. > please file a bug report for that with http://bugzilla.gnome.org/ and don't > forget to specify the version of NetworkManager there. Please link it with > the Gentoo bug in both directions. The rest are just consequences of the > problem noted here. > What I also wonder and affects me bady is that I can't even go back to 0.9.8.4! So my desktop is very inconvenient to use. I get the same errors once I go back. I was using that version without any problems until I tried to upgrade. So I am kind of surprised to see that this is not working until the problem is solved with 0.9.8.6. Any idea about that? Thanks. Output from NM 0.9.8.4: NetworkManager[19124]: NetworkManager (version 0.9.8.4) is starting... NetworkManager[19124]: Read config file /etc/NetworkManager/NetworkManager.conf NetworkManager[19124]: WEXT support is enabled NetworkManager[19124]:SCPlugin-Ifnet: Initializing! NetworkManager[19124]:SCPlugin-Ifnet: management mode: managed NetworkManager[19124]:SCPlugin-Ifnet: Loading connections NetworkManager[19124]:SCPlugin-Ifnet: guessed connection type (eth0) = 802-3-ethernet NetworkManager[19124]:SCPlugin-Ifnet: update_connection_setting_from_config_block: name:eth0, id:eth0, uuid: a1a5b3d2-2e82-bbd6-f878-d26feacc2c7d NetworkManager[19124]: Unknown setting '802-3-ethernet' NetworkManager[19124]:SCPlugin-Ifnet: Found error: base setting GType not found NetworkManager[19124]:SCPlugin-Ifnet: Connection verified eth0:0 NetworkManager[19124]:SCPlugin-Ifnet: guessed connection type (0x4875736579696E2047697269746C6920283830322E31316E29) = 802-11-wireless NetworkManager[19124]:SCPlugin-Ifnet: update_connection_setting_from_config_block: name:0x4875736579696E2047697269746C6920283830322E31316E29, id:Huseyin Giritli (802.11n), uuid: 9876f9e8-8052-47f3-9cff-30c209265a31 NetworkManager[19124]:SCPlugin-Ifnet: Using mode: infrastructure NetworkManager[19124]:SCPlugin-Ifnet: wireless_setting added for 0x4875736579696E2047697269746C6920283830322E31316E29 NetworkManager[19124]:SCPlugin-Ifnet: updating wireless security settings (0x4875736579696E2047697269746C6920283830322E31316E29). NetworkManager[19124]: Unknown setting '802-11-wireless' NetworkManager[19124]:SCPlugin-Ifnet: Found error: base setting GType not found NetworkManager[19124]:SCPlugin-Ifnet: Connection verified 0x4875736579696E2047697269746C6920283830322E31316E29:0 NetworkManager[19124]:SCPlugin-Ifnet: guessed connection type (eth1) = 802-3-ethernet NetworkManager[19124]:SCPlugin-Ifnet: update_connection_setting_from_config_block: name:eth1, id:eth1, uuid: 6f1799c8-61ef-3437-6e02-156b71030428 NetworkManager[19124]: Unknown setting '802-3-ethernet' NetworkManager[19124]:SCPlugin-Ifnet: Found error: base setting GType not found NetworkManager[19124]:SCPlugin-Ifnet: Connection verified eth1:0 NetworkManager[19124]:SCPlugin-Ifnet: Hostname updated to: mordor NetworkManager[19124]:SCPlugin-Ifnet: Initialzation complete! NetworkManager[19124]: Loaded plugin ifnet: (C) 1999-2010 Gentoo Foundation, Inc. To report bugs please use bugs.gentoo.org with [networkmanager] or [qiaomuf] prefix. NetworkManager[19124]: Loaded plugin keyfile: (c) 2007 - 2010 Red Hat, Inc. To report bugs please use the NetworkManager mailing list. NetworkManager[19124]:SCPlugin-Ifnet: getting unmanaged specs... NetworkManager[19124]:SCPlugin-Ifnet: (25646464) ... get_connections. NetworkManager[19124]:SCPlugin-Ifnet: (25646464) connections count: 0 NetworkManager[19124]:keyfile: parsing .keep_net-misc_networkmanager-0 ... NetworkManager[19124]: Connection failed to verify: (unknown) NetworkManager[19124]:keyfile: error: invalid or missing connection property '(null)/connection setting not found' NetworkManager[19124]:SCPlugin-Ifnet: getting unmanaged specs... NetworkManager[19124]: monitoring kernel firmware directory '/lib/firmware'. NetworkManager[19124]: WiFi hard
Re: cannot add profiles for wired connections or connect to wireless after upgrading to 0.9.8.6
One thing I notice comparing the 0.9.8.4 and 0.9.8.6 output is that in 0.9.8.4 it's loading the ifnet plugin, but in 0.9.8.6 it isn't. This suggests some sort of packaging problem; you need to have an /etc/NetworkManager/NetworkManager.conf containing [main] plugin=ifnet -- Dan ___ networkmanager-list mailing list networkmanager-list@gnome.org https://mail.gnome.org/mailman/listinfo/networkmanager-list
cannot add profiles for wired connections or connect to wireless after upgrading to 0.9.8.6
Hi, I use gentoo and this problem as reported by me to the gentoo bugzilla. But devs over there could not really figure out what the problem is, hence this email. Recently I upgraded from 0.9.8.4 to 0.9.8.6 and as a result I can not use nm at all. The problem is that I can not add a profile (clicking Add in the add profile window has no effect) or even connect to a wireless network. I can see my devices and wifi aps but turning them on or selecting aps has no effect. I tried removing the /etc/NetworkManager dir entirely but it had no effect. I've been using nm for a long time and this is the first time I am facing such a problem. Here are the logs I have: Oct 12 12:56:24 mordor dbus-daemon[371]: dbus[371]: [system] Activating via systemd: service name='org.freedesktop.NetworkManager' unit='dbus-org.freedesktop.NetworkManager.service' Oct 12 12:56:24 mordor dbus[371]: [system] Activating via systemd: service name='org.freedesktop.NetworkManager' unit='dbus-org.freedesktop.NetworkManager.service' Oct 12 12:56:24 mordor NetworkManager[13390]: NetworkManager (version 0.9.8.6) is starting... Oct 12 12:56:24 mordor NetworkManager[13390]: Read config file /etc/NetworkManager/NetworkManager.conf Oct 12 12:56:24 mordor NetworkManager[13390]: WEXT support is enabled Oct 12 12:56:24 mordor NetworkManager[13390]: Error parsing file '/etc/NetworkManager/NetworkManager.conf': No such file or directory Oct 12 12:56:24 mordor NetworkManager[13390]: Loaded plugin keyfile: (c) 2007 - 2010 Red Hat, Inc. To report bugs please use the NetworkManager mailing list. Oct 12 12:56:24 mordor NetworkManager[13390]: Error parsing file '/etc/NetworkManager/NetworkManager.conf': No such file or directory Oct 12 12:56:24 mordor NetworkManager[13390]:keyfile: parsing .keep_net-misc_networkmanager-0 ... Oct 12 12:56:24 mordor NetworkManager[13390]: Connection failed to verify: (unknown) Oct 12 12:56:24 mordor NetworkManager[13390]:keyfile: error: invalid or missing connection property '(null)/connection setting not found' Oct 12 12:56:24 mordor NetworkManager[13390]: Error parsing file '/etc/NetworkManager/NetworkManager.conf': No such file or directory Oct 12 12:56:24 mordor NetworkManager[13390]: monitoring kernel firmware directory '/lib/firmware'. Oct 12 12:56:24 mordor NetworkManager[13390]: WiFi hardware radio set enabled Oct 12 12:56:24 mordor dbus-daemon[371]: dbus[371]: [system] Successfully activated service 'org.freedesktop.NetworkManager' Oct 12 12:56:24 mordor dbus[371]: [system] Successfully activated service 'org.freedesktop.NetworkManager' Oct 12 12:56:24 mordor NetworkManager[13390]: WiFi enabled by radio killswitch; enabled by state file Oct 12 12:56:24 mordor NetworkManager[13390]: WWAN enabled by radio killswitch; enabled by state file Oct 12 12:56:24 mordor NetworkManager[13390]: WiMAX enabled by radio killswitch; enabled by state file Oct 12 12:56:24 mordor NetworkManager[13390]: Networking is enabled by state file Oct 12 12:56:24 mordor NetworkManager[13390]: failed to allocate link cache: (-10) Operation not supported Oct 12 12:56:24 mordor NetworkManager[13390]: (eth0): carrier is OFF Oct 12 12:56:24 mordor NetworkManager[13390]: (eth0): new Ethernet device (driver: 'r8169' ifindex: 2) Oct 12 12:56:24 mordor NetworkManager[13390]: (eth0): exported as /org/freedesktop/NetworkManager/Devices/0 Oct 12 12:56:24 mordor NetworkManager[13390]: (eth0): device state change: unmanaged -> unavailable (reason 'managed') [10 20 2] Oct 12 12:56:24 mordor NetworkManager[13390]: (eth0): bringing up device. Oct 12 12:56:24 mordor NetworkManager[13390]: (eth0): preparing device. Oct 12 12:56:24 mordor NetworkManager[13390]: (eth0): deactivating device (reason 'managed') [2] Oct 12 12:56:24 mordor NetworkManager[13390]: Added default wired connection 'Wired connection 1' for /sys/devices/pci:00/:00:07.0/:04:00.0/net/eth0 Oct 12 12:56:24 mordor NetworkManager[13390]: Unknown setting '802-3-ethernet' Oct 12 12:56:24 mordor NetworkManager[13390]: plugin provided invalid connection: '(null)' / 'base setting GType not found' invalid: 2 Oct 12 12:56:24 mordor NetworkManager[13390]: failed to allocate link cache: (-10) Operation not supported Oct 12 12:56:24 mordor NetworkManager[13390]: (eth1): carrier is ON Oct 12 12:56:24 mordor NetworkManager[13390]: (eth1): new Ethernet device (driver: 'r8169' ifindex: 3) Oct 12 12:56:24 mordor NetworkManager[13390]: (eth1): exported as /org/freedesktop/NetworkManager/Devices/1 Oct 12 12:56:24 mordor NetworkManager[13390]: (eth1): device state change: unmanaged -> unavailable (reason 'managed') [10 20 2] Oct 12 12:56:24 mordor NetworkManager[13390]: (eth1): preparing device. Oct 12 12:56:24 mordor NetworkManager[13390]: (eth1): deactivating device (reason 'managed') [2] Oct 12 12:56:24 mordor NetworkManager[13390]: Added default wired connection 'Wired connection 1' for /sys/devices/pci:00/:00:09.0/:05:00.0/net/eth1 Oct 12 12:56:24 m
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" > > To: "networkmanager-list" > > 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: cannot add profiles for wired connections or connect to wireless after upgrading to 0.9.8.6
On Mon, 2013-10-14 at 08:28 -0400, Dan Winship wrote: > One thing I notice comparing the 0.9.8.4 and 0.9.8.6 output is that in > 0.9.8.4 it's loading the ifnet plugin, but in 0.9.8.6 it isn't. This > suggests some sort of packaging problem; you need to have an > /etc/NetworkManager/NetworkManager.conf containing > > [main] > plugin=ifnet > Hi Dan, As mentioned here: https://bugs.gentoo.org/show_bug.cgi?id=487496 (comment 1) "The update to 0.9.8.6 changed the settings backend from ifnet to keyfile for systemd users." I think Gentoo devs decided to change it that way. If I add ifnet then I get: Could not load plugin 'ifnet': /usr/lib64/NetworkManager/libnm-settings-plugin-ifnet.so: cannot open shared object file: No such file or directory I guess gentoo does not even compile it anymore for 0.9.8.6 and onwards... But is my problem really about that? Running 0.9.8.4 with ifnet exhibits the same problem I mentioned before with 0.9.8.6 using keyfile plugin. > -- Dan > ___ > networkmanager-list mailing list > networkmanager-list@gnome.org > https://mail.gnome.org/mailman/listinfo/networkmanager-list > ___ 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
