Bug 250942
Summary: | IPv6 setup: fix default IPv6 address to IPV6ADDR in case of IPV6ADDR_SECONDARIES are used | ||||||||
---|---|---|---|---|---|---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Peter Bieringer <pb> | ||||||
Component: | initscripts | Assignee: | Bill Nottingham <notting> | ||||||
Status: | CLOSED WONTFIX | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||
Severity: | medium | Docs Contact: | |||||||
Priority: | low | ||||||||
Version: | 7 | CC: | denis, pekkas, russ+bugzilla-redhat, rvokal | ||||||
Target Milestone: | --- | ||||||||
Target Release: | --- | ||||||||
Hardware: | All | ||||||||
OS: | Linux | ||||||||
Whiteboard: | |||||||||
Fixed In Version: | Doc Type: | Bug Fix | |||||||
Doc Text: | Story Points: | --- | |||||||
Clone Of: | Environment: | ||||||||
Last Closed: | 2007-08-06 21:48:32 UTC | Type: | --- | ||||||
Regression: | --- | Mount Type: | --- | ||||||
Documentation: | --- | CRM: | |||||||
Verified Versions: | Category: | --- | |||||||
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||
Cloudforms Team: | --- | Target Upstream Version: | |||||||
Embargoed: | |||||||||
Attachments: |
|
Description
Peter Bieringer
2007-08-05 19:32:23 UTC
Created attachment 160718 [details]
Patch to fix the address order
This is all just horribly, horribly, wrong. Moreover, the upstream state of this seems to be crap: 1) there's no good way to set policy in the kernel 2) the 'policy' that's there could conceivably change randomly 3) when asked, all the information I see says that they're looking on moving it to policy based routing... with no further follow up. Pending anything appearing as in #3, closing WONTFIX. Bill, I can understand your position, but this won't help in current situations. One additional question: how using policy based routing with e.g. pinning the src address for default route to a "wished" one, when default route is autoconfigured by receiving a router advertisement? BTW: looks unlike to IPv4, the src can be specified, but is not supported by kernel (at least 2.6.20-1.2952.fc6): # ip -6 route add default via 2001:db8::1 src 2001:db8::2 # ip -6 route |grep ^default default via 2001:db8::1 dev eth1 metric 1024 expires 21334312sec mtu 1500 advmss 1440 hoplimit 4294967295 (In reply to comment #3) > Bill, I can understand your position, but this won't help in current situations. I realize it's not much help, but I don't see how we can reliably code any sort of fix when the only data we have to go on is 'the internal implementation appears to take the last address added in kernel-X.Y.Z'; that's not a standard, that's not something we can configure if it changes, and even the upstream IPv6 working group (AFAICT) declares the kernel behavior broken. I can add a kernel version check before doing the hack, so it's limited to known "buggy" version. After release of a new kernel (which happen more often in Fedora, but never in RHEL minor releases), we can run checks and if behavior hasn't changed, update the version in initscripts. The delay caused would be acceptable for Fedora users imho, for RHEL users I see no problems, because the next version to check (RHEL6) is currently still far away. No, the point is that attempting to reorder and rejigger how interfaces are added based on a kernel version is just ugly, even if there are version checks. This really needs to get fixed properly in the upstream kernel. I fully agree that this needs to be fixed in upstream kernel, but I'm unsure, that Red Hat would backport this fix to RHEL4 (2.6.9) and RHEL5 (2.6.18). For at least this releases, I could create a better workaround which adds IPV6ADDR as last address and the seconaries before. Created attachment 161112 [details]
Different method, depending on used kernel version
This patch do not remove/readd IPV6ADDR, it checks kernel version instead and
add IPV6ADDR as last one, if kernel behavior of "reverse order" is known.
Version check needs an update all the time for Fedora, but for RHEL4 it should
be well enough.
|