I'm trying to set a static IPV6 address for an interface so that it matches the one set in DNS. I have the following lines in ifcfg-eth0: IPV6INIT=yes IPV6ADDR=2001:630:200:4240:219:d1ff:fe92:aeb3 If I restart the networking I get the following in dmesg: eth0: duplicate address detected! I also get two IPV6 addresses in ifconfig: eth0 Link encap:Ethernet HWaddr 00:1C:C0:7A:E4:99 inet addr:131.111.68.219 Bcast:131.111.255.255 Mask:255.255.0.0 inet6 addr: 2001:630:200:4240:219:d1ff:fe92:aeb3/64 Scope:Global inet6 addr: 2001:630:200:4240:21c:c0ff:fe7a:e499/64 Scope:Global inet6 addr: fe80::21c:c0ff:fe7a:e499/64 Scope:Link The rules here say we're only supposed to be using IPV6 addresses defined in DNS on our system, but Fedora likes to create another one based on the MAC number of the interface. I've tried setting IPV6_ROUTER and IPV6_AUTOCONF to no, but this doesn't help. I've also tried setting IPV6_DEFAULTGW. The system seems to be responding to pings on both of the IPV6 addresses. Version-Release number of selected component (if applicable): initscripts-8.86.3-1.x86_64
I can't reproduce this on rawhide; I get the link local address, but not two global addresses. Do you have a full IPv6 infrastructure (RA, etc.)?
I think we have a full IPV6 infrastructure. I'll have to check with the network admins here and try out the Fedora 12 beta.
Please let us know any news about. -- Fedora BugZappers Team Member
This message is a reminder that Fedora 10 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 10. 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 '10'. 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 10'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 10 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
I've tested this on Fedora 12 and it still gets two IPV6 addresses. I'm now communicating with the network people here to see whether the network infrastructure is the problem.
This message is a reminder that Fedora 12 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 12. 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 '12'. 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 12'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 12 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
I've verified this problem is still present in F14 x86-64. With an IPV6ADDR specified in ifcfg-eth0, the system gets both that address and the auto-generated one.
Interesting, if I start up the system with the following in ifcfg-eth0 DEVICE="eth0" BOOTPROTO="static" DNS1="131.111.68.35" GATEWAY="131.111.68.62" HWADDR="00:0E:0C:A2:22:CC" IPADDR="131.111.69.39" IPV6INIT="yes" NETMASK="255.255.0.0" NM_CONTROLLED="no" ONBOOT="yes" IPV6ADDR=2001:630:200:4240:20e:cff:dead:beef IPV6_ROUTER=no IPV6_AUTOCONF=no I get two IPV6 addresses in ifconfig: eth0 Link encap:Ethernet HWaddr 00:0E:0C:A2:22:CC inet addr:131.111.69.39 Bcast:131.111.255.255 Mask:255.255.0.0 inet6 addr: 2001:630:200:4240:20e:cff:dead:beef/64 Scope:Global inet6 addr: 2001:630:200:4240:20e:cff:fea2:22cc/64 Scope:Global inet6 addr: fe80::20e:cff:fea2:22cc/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 If I then do a "service network restart", the network only gets one address: eth0 Link encap:Ethernet HWaddr 00:0E:0C:A2:22:CC inet addr:131.111.69.39 Bcast:131.111.255.255 Mask:255.255.0.0 inet6 addr: fe80::20e:cff:fea2:22cc/64 Scope:Link inet6 addr: 2001:630:200:4240:20e:cff:dead:beef/64 Scope:Global UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
This message is a notice that Fedora 14 is now at end of life. Fedora has stopped maintaining and issuing updates for Fedora 14. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At this time, all open bugs with a Fedora 'version' of '14' have been closed as WONTFIX. (Please note: Our normal process is to give advanced warning of this occurring, but we forgot to do that. A thousand apologies.) Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, feel free to reopen this bug and simply change the 'version' to a later Fedora version. Bug Reporter: Thank you for reporting this issue and we are sorry that we were unable to fix it before Fedora 14 reached 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, you are encouraged to click on "Clone This Bug" (top right of this page) and open it against that version of Fedora. 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