Bug 139237 - System is loosing ipv6 autoconf'ed address
Summary: System is loosing ipv6 autoconf'ed address
Keywords:
Status: CLOSED CANTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 3
Hardware: i686
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Dave Jones
QA Contact: Brian Brock
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2004-11-14 11:35 UTC by Ulrich Kiermayr
Modified: 2015-01-04 22:12 UTC (History)
3 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2005-10-03 00:06:53 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Ulrich Kiermayr 2004-11-14 11:35:10 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.5)
Gecko/20041111 Firefox/1.0

Description of problem:
The system loosing an ipv6 address/route distributed via autoconf
after the lifetime. this worked with fedora core 2.

Interestingly when I start tcpdump, I see the Router Advertisements,
and the it starts working. Not using tcpdump once => not working.

I suppose this has something to do with the acceping/receiving of
multicast frames.

Version-Release number of selected component (if applicable):
kernel-2.6.9-1.667

How reproducible:
Always

Steps to Reproduce:
1. Boot the box
2. IPv6 address there
3. Wait for the address lifetime
4. address gone
    

Expected Results:  The Lifetime timers should be updated every time a
new RA is received

Additional info:

Comment 1 Ulrich Kiermayr 2004-11-14 13:05:35 UTC
It seem to be cured by setting the device into promiscous mode for a
sufficently long period of time (longer than the ra-interval is enough):

ifconfig $DEVICE promisc && sleep $INT && ifconfig $DEVICE -promisc


Comment 2 Dave Jones 2005-07-15 19:28:09 UTC
An update has been released for Fedora Core 3 (kernel-2.6.12-1.1372_FC3) which
may contain a fix for your problem.   Please update to this new kernel, and
report whether or not it fixes your problem.

If you have updated to Fedora Core 4 since this bug was opened, and the problem
still occurs with the latest updates for that release, please change the version
field of this bug to 'fc4'.

Thank you.

Comment 3 Dave Jones 2005-10-03 00:06:53 UTC
This bug has been automatically closed as part of a mass update.
It had been in NEEDINFO state since July 2005.
If this bug still exists in current errata kernels, please reopen this bug.

There are a large number of inactive bugs in the database, and this is the only
way to purge them.

Thank you.


Note You need to log in before you can comment on or make changes to this bug.