Fixing the routing/addressing problem created by these routers was easy to fix on my Windows XP laptop by rebooting the laptop. I didn't want to reboot my Linux boxes and tried to figure out how to undo the routing changes caused by the router advertisements. "route" failed in my attempts to remove the /64 blocks. I ultimately got rid of the routing problems by rebooting the Linux systems.
My questions:
- What is the recommended set-up for Linux servers which are not set-up as routers? In my opinion, allowing a server to add addresses/routing every time a router starts advertising rogue addressing blocks is dangerous and should be avoided.
-- How is an IPv6 default route added in Debian?
-- Various resources maintain that adding a default route in Linux is problematic and should be avoided. Is this still the case in general and/or with Linux?
- How does one recover from receiving a router advertisement from a rogue router without rebooting the Debian Linux system?
-- Are there any IPv6-specific limitations in the "route" command?
-- Are there any lower-level ways of removing IPv6 routes without "route"?
- Finally, a general question which perhaps isn't appropriate for this list, but I'm interested in the scope of the problem. One of the engineers who introduced a rogue router argued that allowing a router to confuse the IPv6 network with router advertisements is a major flaw in the protocol. Is this engineer's statement valid or is protocol just fine and the implementation broken?
Bill Cerveny Internet2
