Bug 684142

Summary: After a few hours of inactivity ipv6 connectivity is down on dualstacked system
Product: [Fedora] Fedora Reporter: Svante Victorsson <svante.victorsson>
Component: NetworkManagerAssignee: Dan Williams <dcbw>
Status: CLOSED WONTFIX QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 13CC: dcbw
Target Milestone: ---   
Target Release: ---   
Hardware: i386   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-06-27 12:01:48 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
wireshark log on my IPv6 traffic over a couple of days none

Description Svante Victorsson 2011-03-11 09:27:02 UTC
Description of problem:
After a couple of hours of IPv6 inactivity, I have no IPv6 connectivity. Have tried several applications, such as /usr/bin/dig, both TCP and UDP queries, as well as /usr/bin/whois queries and receive time outs. After the fact that these applications time out, I tried to ping a host on the IPv6 network to check the connectivity. The ping succeeded. 

I have connectivity again.

Version-Release number of selected component (if applicable):
uname -a 2.6.34.7-66.fc13.i686.PAE #1 SMP Wed Dec 15 07:21:49 UTC 2010 i686 i686 i386 GNU/Linux

[report]$ ip -6 neigh show 
2001:2040:0:1::1 dev eth0 lladdr 00:0a:f3:32:77:00 router DELAY

How reproducible:
Wait for a couple of hours and my IPv6 connectivity is down.
PING is working however TCP/UDP is not.
TCP/UDP is not getting my network connectivity to go up, but ICMP (ping6) makes it go up.

Steps to Reproduce:
1. wait about 3 to 4 hours of inactivity
2. try to resolve dns with /usr/bin/dig or queries some /usr/bin/whois or /usr/bin/ssh with time out results.
3. ping a host on v6 net. such as ping6 2001:470:1:18::2
4. connectivity is up and running as normal.

5. wait about 3 to 4 hours of inactivity
6. try TCP/UDP application with time out result
7. ping6
8. connectivity is up and running as normal.
9.......
  
Actual results:
Every now and then I receiver time outs due to lack of ipv6 connectivity.
Very annoying.

Expected results:
it should be stable and running smoothly

Additional info:
I'm not sure witch module to report to - kernel or network.
Please let me know if a post to wrong module.

If you need more networks logs. I can provide - let me know.

Comment 1 Svante Victorsson 2011-03-11 09:45:46 UTC
Created attachment 483674 [details]
wireshark log on my IPv6 traffic over a couple of days

this log i showing my IPv6 activities over a couple of days.
I discovered 7 times that my network connectivity is down.
Sun mar  6 00:30:47 CET 2011
Sun mar  6 11:31:11 CET 2011
Mon mar  7 00:31:35 CET 2011
Mon mar  7 15:32:00 CET 2011
Tue mar  8 08:32:24 CET 2011
Wed mar  9 03:32:49 CET 2011 
Thu mar 10 00:33:13 CET 2011

After I performed ping6 network is up and applications(dig, whois, ssh) is working as expected.

Comment 2 Bug Zapper 2011-05-30 11:02:28 UTC
This message is a reminder that Fedora 13 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 13.  It is Fedora's policy to close all
bug reports from releases that are no longer maintained.  At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '13'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 13's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 13 is end of life.  If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora please change the 'version' of this 
bug to the applicable version.  If you are unable to change the version, 
please add a comment here and someone will do it for you.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events.  Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Comment 3 Bug Zapper 2011-06-27 12:01:48 UTC
Fedora 13 changed to end-of-life (EOL) status on 2011-06-25. Fedora 13 is 
no longer maintained, which means that it will not receive any further 
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of 
Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.