Created attachment 572767 [details] /var/log/messages It seems that, with the latest kernel, my network connection (Ethernet 100BaseT) is unstable: The connection is "disconnected" every 10 minutes interval according to NetworkManager (with a notification on screen). I'm using kernel-3.3.0-4.fc16.x86_64 NetworkManager-0.9.2-1.fc16.x86_64. My network interface is a 03:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168B PCI Express Gigabit Ethernet controller (rev 02) My computer is connected to a FreeBox v5 ADSL router, which provides "native" IPv6 broadband access.
Created attachment 572778 [details] log of a a tcpdump ip6 session
please see bz 785772. Upgrading to the latest NM in rawhide fixes this issue.
I'm using Fedora 16. Installing NetworkManager from Rawhide require too much dependencies to be installed alone safely. Is it possible to have a test update package ?
http://koji.fedoraproject.org/koji/taskinfo?taskID=3936339 There you go, thats the rawhide NetworkManager built for f16. If you don't want to install that, you can also set your NM IPv6 configuration for all your interfaces to 'ignore'. That should also fix the problem.
(In reply to comment #4) > http://koji.fedoraproject.org/koji/taskinfo?taskID=3936339 > > There you go, thats the rawhide NetworkManager built for f16. > Thanks a lot for the packages. I tried to install them but updated NetworkManager-gnome is missing.
Created attachment 573150 [details] NetworkManager install log (In reply to comment #5) > > I tried to install them but updated NetworkManager-gnome is missing. Here's the log if needed.
Thanks, not sure whats going on there. I'll have to figure that out. The spec file isn't explicitly Required:-ing that package. While I figure it out, please just set the interface settings for the interface in questions for IPv6 to Ignore or Disable, that will provide an equally good solution.
(In reply to comment #5) > (In reply to comment #4) > > http://koji.fedoraproject.org/koji/taskinfo?taskID=3936339 > > > > There you go, thats the rawhide NetworkManager built for f16. > > > > Thanks a lot for the packages. > > I tried to install them but updated NetworkManager-gnome is missing. Please try F16 update here (it's not in stable at the time of this posting) http://koji.fedoraproject.org/koji/buildinfo?buildID=310135
I also have the same problem, but the updated NetworkManager doesn't seem to help: # yum info NetworkManager Installed Packages Name : NetworkManager Arch : x86_64 Epoch : 1 Version : 0.9.4 Release : 1.git20120328.fc16 Size : 6.7 M Repo : installed From repo : updates-testing Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168B PCI Express Gigabit Ethernet controller (rev 02) I have a "Freebox v6" ADSL router.
Created attachment 574435 [details] /var/log/messages After installing the provided packages, I'm still having the problem. See this in the log. Additionally, I'm hitting bug #799591 .
Did you all make sure you're configuration for ipv6 in NM hadn't reverted to automatic or dhcp?
(In reply to comment #11) > Did you all make sure you're configuration for ipv6 in NM hadn't reverted to > automatic or dhcp? After installing the provided package here, I've checked that ipv6 configuration is in "automatic" mode. And it's still in "automatic" mode.
no, I'm asking if it wasn't in automatic mode previously. If its in automatic now, you need to move it to ignore or disabled mode. the rawhide NM has fixed this problem for some, but others still need to explicitly disable NM's ipv6 handling if they use SLAAC at the moment.
(In reply to comment #13) > no, I'm asking if it wasn't in automatic mode previously. If its in automatic > now, you need to move it to ignore or disabled mode. the rawhide NM has fixed > this problem for some, but others still need to explicitly disable NM's ipv6 > handling if they use SLAAC at the moment. If "ignore" or "disable" is still required, the updated NM packages are not fixing the problem as expected. So I'm going to switch from "automatic" (the current and previous mode) to "ignore" which was proven to workaround the problem.
As noted above some people have this problem automatically fixed when using the latest NM, others dont. I'm still trying to figure out what the difference between the two is. Given that this thread seems to contain people in the latter group, I'll reassign this over to NM for a closer look.
*** This bug has been marked as a duplicate of bug 785772 ***