NetworkManager connection priority - a question
As I understand it NetworkManager makes connections according to the following priority order (but correct me if I am wrong!): Highest priority is given to a functioning wired connection. If (1) is not available, then connection is made to a wireless AP that is defined or that has been connected to before. If (2) is not available, then connection is made to any available wireless AP. In my home LAN I have two wireless access points and here is where the problem lies. The main servers and primary AP are upstairs. Downstairs is a second wireless AP that I can choose to have the same or different SSID as the priimary, but the channel they operate on is different. I have only run this with wireless G at the present time (before trying later with wireless N) So when a laptop running F14 is switched on downstairs there is a strong wireless signal from the secondary AP downstairs, and a weaker (but usable) wireless signal from the upstairs AP. NetworkManager appears not to be able to make a firm decision to connect to the strong downstairs AP and keeps trying to switch back and forth between to the two available APs despite the difference in strength between the signals from the two APs. This appears to be the same behaviour whether or not the two AP's have the same SSID or different SSIDs. The only way I can keep the connection stable is to make the connection to the upstairs AP not connect automatically. It would be very nice to be able to tell NM to connect to the stronger of the two AP signals as priority and not keep trying to switch between the two - but I can't find any way to make NM do this? i.e. in my original list of connection priority near the top of this post if there are two available wireless APs with defined or pre-existing connection setups then it appears (unless I am wrong) that NM has no internal rule to prioritise the stronger signal, or to set this as a user config somewhere. The net result (forgive the pun - it is only just after the New Year!) - is that there are not infrequent brief network pauses as NM retries the other AP. Can anyone offer advice on resolving this or should this be a bugzilla report? (upstream?) Thanks -- mike c -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: Is there a NetworkManager issue in Rawhide?
On 01/07/2011 08:33 PM, Jim Bevier wrote: Yes, I am seeing the same thing. I am using todays updates on I686 system. Jim snip I assume you are using systemd...so, where do you believe the problem lies? I looked thru the systemd and networkmanager bzs, but didn't see anything that looked relevant. Regards, OldFart -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: NetworkManager connection priority - a question
On Sat, 2011-01-08 at 15:28 +, mike cloaked wrote: As I understand it NetworkManager makes connections according to the following priority order (but correct me if I am wrong!): [...] Is this a problem specific to F15 or Rawhide? If not, general questions about Fedora should go to the Users list. poc -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: NetworkManager connection priority - a question
On Sat, Jan 8, 2011 at 4:44 PM, Patrick O'Callaghan pocallag...@gmail.com wrote: On Sat, 2011-01-08 at 15:28 +, mike cloaked wrote: As I understand it NetworkManager makes connections according to the following priority order (but correct me if I am wrong!): [...] Is this a problem specific to F15 or Rawhide? If not, general questions about Fedora should go to the Users list. poc In principle this is about f14 (and all versions prior!) where I have tested this - but I suspect that these issues are also relevant to f15/rawhide unless changes have been made to the NM and/or wpa+supplicant code between f14 release and now - which I expect has not happened. Hence this is likely to be relevant to f15 and to rawhide I expect? -- mike c -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: NetworkManager connection priority - a question
On Sat, 2011-01-08 at 17:38 +, mike cloaked wrote: On Sat, Jan 8, 2011 at 4:44 PM, Patrick O'Callaghan pocallag...@gmail.com wrote: On Sat, 2011-01-08 at 15:28 +, mike cloaked wrote: As I understand it NetworkManager makes connections according to the following priority order (but correct me if I am wrong!): [...] Is this a problem specific to F15 or Rawhide? If not, general questions about Fedora should go to the Users list. poc In principle this is about f14 (and all versions prior!) where I have tested this - but I suspect that these issues are also relevant to f15/rawhide unless changes have been made to the NM and/or wpa+supplicant code between f14 release and now - which I expect has not happened. Hence this is likely to be relevant to f15 and to rawhide I expect? Maybe, maybe not. If you aren't testing it, how would you know? If you want to bring up a long-standing issue with NM's functionality, which affects users of current versions as well as (possibly) future ones, the appropriate place would seem to be the Users list. Since the Users list is also more populous than this one, you may also get more response. poc -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: NetworkManager connection priority - a question
On Sat, Jan 08, 2011 at 02:18:19PM -0430, Patrick O'Callaghan wrote: In principle this is about f14 (and all versions prior!) where I have tested this - but I suspect that these issues are also relevant to f15/rawhide unless changes have been made to the NM and/or wpa+supplicant code between f14 release and now - which I expect has not happened. Hence this is likely to be relevant to f15 and to rawhide I expect? Maybe, maybe not. If you aren't testing it, how would you know? If you want to bring up a long-standing issue with NM's functionality, which affects users of current versions as well as (possibly) future ones, the appropriate place would seem to be the Users list. Since the Users list is also more populous than this one, you may also get more response. Or the upstream NetworkManager list: http://mail.gnome.org/mailman/listinfo/networkmanager-list -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: NetworkManager connection priority - a question
On Sat, Jan 8, 2011 at 7:23 PM, Chuck Anderson c...@wpi.edu wrote: Maybe, maybe not. If you aren't testing it, how would you know? If you want to bring up a long-standing issue with NM's functionality, which affects users of current versions as well as (possibly) future ones, the appropriate place would seem to be the Users list. Since the Users list is also more populous than this one, you may also get more response. Or the upstream NetworkManager list: http://mail.gnome.org/mailman/listinfo/networkmanager-list -- OK thanks. -- mike c -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Fedora 14 updates-testing report
The following Fedora 14 Security updates need testing: https://admin.fedoraproject.org/updates/wireshark-1.4.2-2.fc14 https://admin.fedoraproject.org/updates/ccid-1.4.0-2.fc14 https://admin.fedoraproject.org/updates/pcsc-lite-1.6.4-3.fc14 https://admin.fedoraproject.org/updates/subversion-1.6.15-1.fc14 https://admin.fedoraproject.org/updates/perl-Convert-UUlib-1.34-1.fc14 https://admin.fedoraproject.org/updates/pyfribidi-0.10.0-1.fc14 https://admin.fedoraproject.org/updates/Django-1.2.4-1.fc14 https://admin.fedoraproject.org/updates/feh-1.10.1-1.fc14 https://admin.fedoraproject.org/updates/socat-1.7.1.3-1.fc14 https://admin.fedoraproject.org/updates/mod_auth_mysql-3.0.0-12.fc14 https://admin.fedoraproject.org/updates/perl-CGI-Simple-1.112-2.fc14 https://admin.fedoraproject.org/updates/exim-4.72-2.fc14 The following Fedora 14 Critical Path updates have yet to be approved: https://admin.fedoraproject.org/updates/psmisc-22.13-6.fc14 https://admin.fedoraproject.org/updates/dosfstools-3.0.9-4.fc14 https://admin.fedoraproject.org/updates/openldap-2.4.23-5.fc14 https://admin.fedoraproject.org/updates/policycoreutils-2.0.83-33.6.fc14 https://admin.fedoraproject.org/updates/selinux-policy-3.9.7-20.fc14 https://admin.fedoraproject.org/updates/xorg-x11-drv-geode-2.11.10-1.fc14 The following builds have been pushed to Fedora 14 updates-testing 389-admin-1.1.14-1.fc14 OpenLP-1.9.4-1.fc14 belier-1.2-4.fc14 byobu-3.21-1.fc14 glom-1.16.2-1.fc14 identicurse-0.6.2-1.fc14 kradio4-4.0.2-1.fc14 lastfmlib-0.4.0-2.fc14 libgda-4.2.2-2.fc14 loggerhead-1.18-1.fc14 pidgin-musictracker-0.4.22-1.fc14 python-rhsm-0.94.12-1.fc14 python-sleekxmpp-1.0-0.7.beta2.fc14 subdownloader-2.0.14-1.fc14 supybot-notify-0.2.1-1.fc14 tito-0.3.0-1.fc14 Details about builds: 389-admin-1.1.14-1.fc14 (FEDORA-2011-0268) 389 Administration Server (admin) Update Information: The 1.1.14 release - a couple of crash bug fixes ChangeLog: * Wed Jan 5 2011 Rich Megginson rmegg...@redhat.com - 1.1.14-1 - 1.1.14 release - Bug 664671 - Admin server segfault when full SSL access (http+ldap+console) required - Bug 638511 - dirsrv-admin crashes at startup with SELinux enabled References: [ 1 ] Bug #664671 - Admin server segfault when full SSL access (http+ldap+console) required https://bugzilla.redhat.com/show_bug.cgi?id=664671 [ 2 ] Bug #638511 - dirsrv-admin segfaults if selinux is enforced https://bugzilla.redhat.com/show_bug.cgi?id=638511 OpenLP-1.9.4-1.fc14 (FEDORA-2011-0261) Open source Church presentation and lyrics projection application Update Information: New Release tracking Alpha 4 upstream ChangeLog: * Sat Jan 8 2011 Tim Bentley timbent...@openlp.org - 1.9.4-1 - Alpha 4 release build belier-1.2-4.fc14 (FEDORA-2011-0266) Generates scripts allowing you to chain many ssh connections Update Information: Initial import References: [ 1 ] Bug #548795 - Review Request: belier - Generates scripts allowing you to chain many ssh connections https://bugzilla.redhat.com/show_bug.cgi?id=548795 byobu-3.21-1.fc14 (FEDORA-2011-0250) Light-weight, configurable window manager built upon GNU screen Update Information: new version released ChangeLog: * Sat Jan 8 2011 Jan Klepek jan.klepek at, gmail.com - 3.21-1 - new release * Sat Dec 18 2010 Jan Klepek jan.klepek at, gmail.com - 3.20-2 - upgrade to 3.20 + some patches References: [ 1 ] Bug #634542 - byobu-3.21 is available
Fedora 13 updates-testing report
The following Fedora 13 Security updates need testing: https://admin.fedoraproject.org/updates/pcsc-lite-1.5.5-5.fc13 https://admin.fedoraproject.org/updates/ccid-1.3.11-2.fc13 https://admin.fedoraproject.org/updates/wireshark-1.2.13-2.fc13 https://admin.fedoraproject.org/updates/evince-2.30.3-2.fc13 https://admin.fedoraproject.org/updates/dbus-1.2.24-2.fc13 https://admin.fedoraproject.org/updates/subversion-1.6.15-1.fc13 https://admin.fedoraproject.org/updates/perl-Convert-UUlib-1.34-1.fc13 https://admin.fedoraproject.org/updates/pyfribidi-0.10.0-1.fc13 https://admin.fedoraproject.org/updates/Django-1.2.4-1.fc13 https://admin.fedoraproject.org/updates/feh-1.10.1-1.fc13 https://admin.fedoraproject.org/updates/mod_auth_mysql-3.0.0-12.fc13 https://admin.fedoraproject.org/updates/perl-CGI-Simple-1.112-2.fc13 The following Fedora 13 Critical Path updates have yet to be approved: https://admin.fedoraproject.org/updates/dosfstools-3.0.9-3.fc13 https://admin.fedoraproject.org/updates/attr-2.4.44-4.fc13 https://admin.fedoraproject.org/updates/livecd-tools-13.1-1.fc13 https://admin.fedoraproject.org/updates/selinux-policy-3.7.19-80.fc13 https://admin.fedoraproject.org/updates/libical-0.46-2.fc13 https://admin.fedoraproject.org/updates/pm-utils-1.2.6.1-4.fc13 https://admin.fedoraproject.org/updates/mash-0.5.20-1.fc13 https://admin.fedoraproject.org/updates/openldap-2.4.21-11.fc13 https://admin.fedoraproject.org/updates/nss-3.12.7-4.fc13,nss-util-3.12.7-2.fc13,nss-softokn-3.12.7-3.fc13,nspr-4.8.6-1.fc13 https://admin.fedoraproject.org/updates/xorg-x11-drv-openchrome-0.2.904-7.fc13 The following builds have been pushed to Fedora 13 updates-testing 389-admin-1.1.14-1.fc13 belier-1.2-4.fc13 byobu-3.21-1.fc13 kradio4-4.0.2-1.fc13 pidgin-musictracker-0.4.22-1.fc13 python-sleekxmpp-1.0-0.7.beta2.fc13 subdownloader-2.0.14-1.fc13 subversion-1.6.15-1.fc13 tito-0.3.0-1.fc13 Details about builds: 389-admin-1.1.14-1.fc13 (FEDORA-2011-0251) 389 Administration Server (admin) Update Information: The 1.1.14 release - a couple of crash bug fixes ChangeLog: * Wed Jan 5 2011 Rich Megginson rmegg...@redhat.com - 1.1.14-1 - 1.1.14 release - Bug 664671 - Admin server segfault when full SSL access (http+ldap+console) required - Bug 638511 - dirsrv-admin crashes at startup with SELinux enabled References: [ 1 ] Bug #664671 - Admin server segfault when full SSL access (http+ldap+console) required https://bugzilla.redhat.com/show_bug.cgi?id=664671 [ 2 ] Bug #638511 - dirsrv-admin segfaults if selinux is enforced https://bugzilla.redhat.com/show_bug.cgi?id=638511 belier-1.2-4.fc13 (FEDORA-2011-0263) Generates scripts allowing you to chain many ssh connections Update Information: Initial import References: [ 1 ] Bug #548795 - Review Request: belier - Generates scripts allowing you to chain many ssh connections https://bugzilla.redhat.com/show_bug.cgi?id=548795 byobu-3.21-1.fc13 (FEDORA-2011-0265) Light-weight, configurable window manager built upon GNU screen Update Information: new version released ChangeLog: * Sat Jan 8 2011 Jan Klepek jan.klepek at, gmail.com - 3.21-1 - new release * Sat Dec 18 2010 Jan Klepek jan.klepek at, gmail.com - 3.20-2 - upgrade to 3.20 + some patches References: [ 1 ] Bug #634542 - byobu-3.21 is available https://bugzilla.redhat.com/show_bug.cgi?id=634542 [ 2 ] Bug #656852 - [abrt] byobu-3.4-2.fc14: byobu-config:377:writewindows:IOError: [Errno 2] No such file or directory: '/home/costa/.byobu/windows' https://bugzilla.redhat.com/show_bug.cgi?id=656852 [ 3 ] Bug #666845 - [abrt] byobu-3.4-2.fc14: byobu-config:340:writestatus:IOError: [Errno 2] No existe el fichero o el directorio: '/home/bass/.byobu/status' https://bugzilla.redhat.com/show_bug.cgi?id=666845
