Bug 841967
| Summary: | "ip", "netstat" and "route" commands always show IPv6 cached as well as configured routes | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Phil Mayers <p.mayers> |
| Component: | kernel | Assignee: | Kernel Maintainer List <kernel-maint> |
| Status: | CLOSED NOTABUG | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 17 | CC: | gansalmon, itamar, jforbes, jonathan, kernel-maint, madhu.chinakonda, nhorman, psimerda |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2013-04-19 17:37:10 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
Phil Mayers
2012-07-20 17:31:41 UTC
Kernel 3.4.0 is considerably outdated, does this still happen with 3.5.3? It happens with kernel 3.4.7 under F16. 3.4.7 was tagged 29 Jul 2012, and the RPM built 30 Jul 2012, and the gitweb history for the stable kernel reports no obvious related changes to the net/ipv6 tree since then. Do you have a specific reason to assume it *doesn't* happen with 3.5.3? We only have a couple of F17 machines and can't take a reboot to get the new kernel in at the moment. It might be easier to try and reproduce it yourself locally if you have a 3.5.3 machine. Otherwise, we'll schedule a reboot next week and look then. ip, route and netstat have shown cached routes for quite some time now. If you just want to see configured routes you need to filter by proto, i.e.: ip -6 route list proto statc ip -6 route list proto kernel ip -6 route list proto <tableid> etc. *** Bug 736444 has been marked as a duplicate of this bug. *** |