Bug 1475432
Summary: | Windows hosts losing IPv6 gateway acquired from radvd | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Pim Zandbergen <p.zandbergen> |
Component: | radvd | Assignee: | Pavel Zhukov <pzhukov> |
Status: | CLOSED NOTABUG | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | medium | Docs Contact: | |
Priority: | unspecified | ||
Version: | 26 | CC: | code, dominik, pzhukov |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | x86_64 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | If docs needed, set a value | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2017-08-01 06:11:34 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Pim Zandbergen
2017-07-26 16:40:08 UTC
This might be related to intrinsic problems in IPv6 auto configuration protocol specifications. https://tools.ietf.org/html/draft-gont-6man-slaac-dns-config-issues-01 It is known that Windows hosts ignore the RDNSS and DNSSL configuration. This is not the issue. The issue is with Windows hosts losing the route that radvd advertises. And with Windows hosts complaining that "route limits" are being reached. However, these errors have not been seen on our network for 5 days now, without changing the radvd configuration. Also, I have not been able to reproduce this problem on other similar networks. The fact that this problem started after upgrading to F26 might have been a coincidence and may be unrelated. (In reply to Pim Zandbergen from comment #2) > It is known that Windows hosts ignore the RDNSS and DNSSL configuration. > This is not the issue. > The issue is with Windows hosts losing the route that radvd advertises. > And with Windows hosts complaining that "route limits" are being reached. > > However, these errors have not been seen on our network for 5 days now, > without changing the radvd configuration. > > Also, I have not been able to reproduce this problem on other similar > networks. Hello, Thank you for the information. Closing the bug for now. Please reopen if issue is back. > > The fact that this problem started after upgrading to F26 might have > been a coincidence and may be unrelated. |