Re: Annoying bug in NM1.0.0-8
On 04/21/2015 01:31 PM, Chris Murphy wrote: It may be some weir interaction between the router and NM. I'm using dd-wrt on the router. What about you, danofsatx? Chris Murphy My router is a Motorola NVG589 Uverse Gateway. I tracked my issue down - it is a change in how firewalld processed my direct rules. I'm not exactly sure what happened during fedup, but I stopped firewalld, flushed the IPTables rules, and restarted firewalld, and it appears to have reprocessed my rules properly. -- Dan Mossor Systems Engineer at Large Fedora KDE WG | Fedora QA Team | Fedora Server SIG Fedora Infrastructure Apprentice FAS: dmossor IRC: danofsatx San Antonio, Texas, USA -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: Annoying bug in NM1.0.0-8
On Sun, 2015-04-19 at 15:36 -0600, Chris Murphy wrote: On Sun, Apr 19, 2015 at 2:57 PM, Dan Mossor danofs...@gmail.com wrote: I've noticed something else,also - I can't get F22 to see my wired interface to compare with wireless to see if I can narrow it down some more. The GUI applet simply won't activate the interface, and nmcli tells me Error: Connection activation failed: Connection 'Home' is not available on the device enp4s0 at this time. I'm not having that problem, I can connect to wired but it's not used. The laptop continues to use wireless unless I turn wireless off, then it falls back to wired. But this behavior isn't new, as far as I know it's always worked this (incorrrect) way. -- Chris Murphy All works for me with the wired and wireless interfaces , I use OpenWrt on my router. Regards, Paul. -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: Annoying bug in NM1.0.0-8
On 22.04.2015 12:29, Pavlo Rudyi wrote: On Sun, 2015-04-19 at 15:36 -0600, Chris Murphy wrote: On Sun, Apr 19, 2015 at 2:57 PM, Dan Mossor danofs...@gmail.com wrote: I've noticed something else,also - I can't get F22 to see my wired interface to compare with wireless to see if I can narrow it down some more. The GUI applet simply won't activate the interface, and nmcli tells me Error: Connection activation failed: Connection 'Home' is not available on the device enp4s0 at this time. I'm not having that problem, I can connect to wired but it's not used. The laptop continues to use wireless unless I turn wireless off, then it falls back to wired. But this behavior isn't new, as far as I know it's always worked this (incorrrect) way. -- Chris Murphy All works for me with the wired and wireless interfaces , I use OpenWrt on my router. Regards, Paul. Although it has a funky date, there's no problemos with: DD-WRT v24-sp2 std (c) 2015 NewMedia-NET GmbH Release: 04/01/15 (SVN revision: 26635) == _______ _ _ _ | _ \| _ \ \ \ / / _ \_ _| __ _|___ \| || | || | || ||\ \ /\ / /| |_) || | \ \ / / __) | || |_ ||_| ||_||_\ V V / | _ | |\ V / / __/|__ _| |___/|___/ \_/\_/ |_| \_\|_| \_/ |_| |_| DD-WRT v24-sp2 http://www.dd-wrt.com == BusyBox v1.23.2 (2015-04-01 08:53:35 CEST) built-in shell (ash) ash-es to ash-es, dust to dust -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: Annoying bug in NM1.0.0-8
It may be some weir interaction between the router and NM. I'm using dd-wrt on the router. What about you, danofsatx? Chris Murphy -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: Annoying bug in NM1.0.0-8
On Sun, 2015-04-19 at 20:17 -0500, Dan Mossor wrote: Ok, my wired networking problem has been hashed out - it was a physical layer issue. That led me to discovering that the problem is worse than I feared, it exists on wired networking also, and can't be tied to Intel drivers since both systems I tested this on have either a Qualcomm Atheros or Realtek gigabit ethernet NIC. I have filed a bug. https://bugzilla.redhat.com/show_bug.cgi?id=1213194 Weird. I haven't seen this issue at all. Feduped to F22 a few days ago and everything appears to work fine. I haven't noticed a network issue at all. Have you checked journalctl to see if there are any errors there? NetworkManager-1.0.0-8.fc22.x86_64 btw, rsyslog.org appears down: http://isup.me/rsyslog.org The other sites worked just fine. 00:19.0 Ethernet controller: Intel Corporation Ethernet Connection I217-LM (rev 05) -- Thanks, Regards, Ankur Sinha FranciscoD http://fedoraproject.org/wiki/User:Ankursinha signature.asc Description: This is a digitally signed message part -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: Annoying bug in NM1.0.0-8
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 04/21/15 22:39, Ankur Sinha wrote: Weird. I haven't seen this issue at all. Feduped to F22 a few days ago I've not seen any problems either. I've got both a fresh F22 B3 install and a Fedup from F21. - -- If you can't laugh at yourself, others will gladly oblige. -BEGIN PGP SIGNATURE- Version: GnuPG v2 iEYEARECAAYFAlU2ZasACgkQ4JnKjVbCBvrW5gCfSS/4txE1iT3rPz7D108X0Zvh 4awAn35wAnHy1J3YbFFQhSLTT57QRGr6 =6bNw -END PGP SIGNATURE- -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: Annoying bug in NM1.0.0-8
On Sun, Apr 19, 2015 at 2:57 PM, Dan Mossor danofs...@gmail.com wrote: I've noticed something else,also - I can't get F22 to see my wired interface to compare with wireless to see if I can narrow it down some more. The GUI applet simply won't activate the interface, and nmcli tells me Error: Connection activation failed: Connection 'Home' is not available on the device enp4s0 at this time. I'm not having that problem, I can connect to wired but it's not used. The laptop continues to use wireless unless I turn wireless off, then it falls back to wired. But this behavior isn't new, as far as I know it's always worked this (incorrrect) way. -- Chris Murphy -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: Annoying bug in NM1.0.0-8
On 04/19/2015 05:54 PM, Scott Robbins wrote: On Sun, Apr 19, 2015 at 03:36:11PM -0600, Chris Murphy wrote: On Sun, Apr 19, 2015 at 2:57 PM, Dan Mossor danofs...@gmail.com wrote: I've noticed something else,also - I can't get F22 to see my wired interface to compare with wireless to see if I can narrow it down some more. The GUI applet simply won't activate the interface, and nmcli tells me Error: Connection activation failed: Connection 'Home' is not available on the device enp4s0 at this time. I'm not having that problem, I can connect to wired but it's not used. The laptop continues to use wireless unless I turn wireless off, then it falls back to wired. But this behavior isn't new, as far as I know it's always worked this (incorrrect) way. Isn't that a NetworkManager, rather than Fedora, thing? DISCLAIMER--I usually remove NetworkManager and then, if I have a machine that uses both wired and wireless, don't set my network to start on boot as what I want to use changes, depending upon the situation. NetworkManager has come a long way since the days of randomly resetting your connections. I thought it was fairly solid at the 0.9 release, and use it on just about every system now including my servers. The Cockpit integration with NetworkManager has made it dead easy and nearly failproof, and nmcli is in a powerful tool in it's own right. However, the usefulness of 1.0 is suspect at this point. I can only get to half of the internet, which is basically useless (IMHO). -- Dan Mossor, RHCSA Systems Engineer Fedora Server WG | Fedora KDE WG | Fedora QA Team Fedora Infrastructure Apprentice FAS: dmossor IRC: danofsatx San Antonio, Texas, USA -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: Annoying bug in NM1.0.0-8
On Sun, Apr 19, 2015 at 9:20 AM, Dan Mossor danofs...@gmail.com wrote: Greetings, folks. I and at least one other individual have noticed an annoying bug with NetworkManager-1.0.0-8.fc22.x86_64 but we aren't sure of the root cause so we can't legitimately file a BZ on it yet. The issue we're seeing is that with a fully updated Fedora 22 Beta system, once NM is in operation for a bit it starts to loose connectivity. Not total connectivity, but partial. I'm having the same experience, which is sometimes networking works for some thing some of the time sometimes. Google searches work, logging in to sites like outlook.com works, but then hangs when email is to be downloaded or sent. If I reboot the same hardware to OS X the problems don't happen. If I reboot Fedora 22, it might be fixed for a short while, or it might misbehave right away. I can't figure out the pattern. -- Chris Murphy -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: Annoying bug in NM1.0.0-8
On 04/19/2015 02:21 PM, Chris Murphy wrote: On Sun, Apr 19, 2015 at 9:20 AM, Dan Mossor danofs...@gmail.com wrote: Greetings, folks. I and at least one other individual have noticed an annoying bug with NetworkManager-1.0.0-8.fc22.x86_64 but we aren't sure of the root cause so we can't legitimately file a BZ on it yet. The issue we're seeing is that with a fully updated Fedora 22 Beta system, once NM is in operation for a bit it starts to loose connectivity. Not total connectivity, but partial. I'm having the same experience, which is sometimes networking works for some thing some of the time sometimes. Google searches work, logging in to sites like outlook.com works, but then hangs when email is to be downloaded or sent. If I reboot the same hardware to OS X the problems don't happen. If I reboot Fedora 22, it might be fixed for a short while, or it might misbehave right away. I can't figure out the pattern. I've rebooted this machine many, many times due to unrelated kded5 crashes, but the problem has not once gone away since it appeared. I've noticed something else,also - I can't get F22 to see my wired interface to compare with wireless to see if I can narrow it down some more. The GUI applet simply won't activate the interface, and nmcli tells me Error: Connection activation failed: Connection 'Home' is not available on the device enp4s0 at this time. So, I seem to have a multitude of issues, the core component of which seems to be NetworkManager. -- Dan Mossor Systems Engineer at Large Fedora KDE WG | Fedora QA Team | Fedora Server SIG Fedora Infrastructure Apprentice FAS: dmossor IRC: danofsatx San Antonio, Texas, USA -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: Annoying bug in NM1.0.0-8
On Sun, Apr 19, 2015 at 03:36:11PM -0600, Chris Murphy wrote: On Sun, Apr 19, 2015 at 2:57 PM, Dan Mossor danofs...@gmail.com wrote: I've noticed something else,also - I can't get F22 to see my wired interface to compare with wireless to see if I can narrow it down some more. The GUI applet simply won't activate the interface, and nmcli tells me Error: Connection activation failed: Connection 'Home' is not available on the device enp4s0 at this time. I'm not having that problem, I can connect to wired but it's not used. The laptop continues to use wireless unless I turn wireless off, then it falls back to wired. But this behavior isn't new, as far as I know it's always worked this (incorrrect) way. Isn't that a NetworkManager, rather than Fedora, thing? DISCLAIMER--I usually remove NetworkManager and then, if I have a machine that uses both wired and wireless, don't set my network to start on boot as what I want to use changes, depending upon the situation. -- Scott Robbins PGP keyID EB3467D6 ( 1B48 077D 66F6 9DB0 FDC2 A409 FA54 EB34 67D6 ) gpg --keyserver pgp.mit.edu --recv-keys EB3467D6 -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: Annoying bug in NM1.0.0-8
On 04/19/2015 10:20 AM, Dan Mossor wrote: Greetings, folks. I and at least one other individual have noticed an annoying bug with NetworkManager-1.0.0-8.fc22.x86_64 but we aren't sure of the root cause so we can't legitimately file a BZ on it yet. The issue we're seeing is that with a fully updated Fedora 22 Beta system, once NM is in operation for a bit it starts to loose connectivity. Not total connectivity, but partial. For example, I can run a search on Google for anything and get back the usual tens or hundreds of results. but on a single page of results I can only successfully open 2 or 3 of them. Specifically, a few sites I'm noticing I can no longer reach: https://www.happyassassin.net/ http://docs.kde.org http://mirrors.rpmfusion.org http://rsyslog.org However, all Fedora Project, Red Hat CentOS and GNOME links work just fine. Pages from the Stack Exchange family of sites are hit and miss, but mostly miss. Also, it is only http traffic - I can hit these sites with ftp, ssh or rsync where supported. I have tried using Chrome, Firefox, Konquerer, ReKonq, wget and curl and get the same result every time. To aid in troubleshooting, I am providing a link to the pcap [0] of my wget attempt against the RPM Fusion mirror site - it's disappointing, really. The only commonality I've discovered among the affected systems is that they are using Intel wireless adapters. Specifically in my case, a Centrino 2230 and a Centrino 2200. The other user I mentioned earlier indicated that he believed the fault may lie in the routing tables, but I have not confirmed or ruled this out yet - I'm still shooting in the dark. I know it is not network issues at large, as on this network I have other devices - Android, ChromeOS, and Windows 8.1 devices - that all work fine. In fact, on one of my affected systems, it was working just fine on F21 and NM 0.9.10 before I updated it to F22 last night with fedup. This points directly to F22 being at fault, but like I mentioned, I don't know if it is NetworkManager or Intel Wireless drivers. Thoughts? Concerns? Criticisms? Dan [0] http://goo.gl/qG76ey - a shortened link to Google Drive, full link: https://drive.google.com/open?id=0ByM4hcGUETFIS0RBLW8wMU5UOFUauthuser=0 Ok, my wired networking problem has been hashed out - it was a physical layer issue. That led me to discovering that the problem is worse than I feared, it exists on wired networking also, and can't be tied to Intel drivers since both systems I tested this on have either a Qualcomm Atheros or Realtek gigabit ethernet NIC. I have filed a bug. https://bugzilla.redhat.com/show_bug.cgi?id=1213194 -- Dan Mossor, RHCSA Systems Engineer Fedora Server WG | Fedora KDE WG | Fedora QA Team Fedora Infrastructure Apprentice FAS: dmossor IRC: danofsatx San Antonio, Texas, USA -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Annoying bug in NM1.0.0-8
Greetings, folks. I and at least one other individual have noticed an annoying bug with NetworkManager-1.0.0-8.fc22.x86_64 but we aren't sure of the root cause so we can't legitimately file a BZ on it yet. The issue we're seeing is that with a fully updated Fedora 22 Beta system, once NM is in operation for a bit it starts to loose connectivity. Not total connectivity, but partial. For example, I can run a search on Google for anything and get back the usual tens or hundreds of results. but on a single page of results I can only successfully open 2 or 3 of them. Specifically, a few sites I'm noticing I can no longer reach: https://www.happyassassin.net/ http://docs.kde.org http://mirrors.rpmfusion.org http://rsyslog.org However, all Fedora Project, Red Hat CentOS and GNOME links work just fine. Pages from the Stack Exchange family of sites are hit and miss, but mostly miss. Also, it is only http traffic - I can hit these sites with ftp, ssh or rsync where supported. I have tried using Chrome, Firefox, Konquerer, ReKonq, wget and curl and get the same result every time. To aid in troubleshooting, I am providing a link to the pcap [0] of my wget attempt against the RPM Fusion mirror site - it's disappointing, really. The only commonality I've discovered among the affected systems is that they are using Intel wireless adapters. Specifically in my case, a Centrino 2230 and a Centrino 2200. The other user I mentioned earlier indicated that he believed the fault may lie in the routing tables, but I have not confirmed or ruled this out yet - I'm still shooting in the dark. I know it is not network issues at large, as on this network I have other devices - Android, ChromeOS, and Windows 8.1 devices - that all work fine. In fact, on one of my affected systems, it was working just fine on F21 and NM 0.9.10 before I updated it to F22 last night with fedup. This points directly to F22 being at fault, but like I mentioned, I don't know if it is NetworkManager or Intel Wireless drivers. Thoughts? Concerns? Criticisms? Dan [0] http://goo.gl/qG76ey - a shortened link to Google Drive, full link: https://drive.google.com/open?id=0ByM4hcGUETFIS0RBLW8wMU5UOFUauthuser=0 -- Dan Mossor, RHCSA Systems Engineer Fedora Server WG | Fedora KDE WG | Fedora QA Team Fedora Infrastructure Apprentice FAS: dmossor IRC: danofsatx San Antonio, Texas, USA -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
