[2.0a1] network provisioningserver should parse ipv6 routes

[LaMont Jones]

src/provisioningserver/utils/iproute.py:get_ip_route runs "/sbin/ip route", which gets it ipv4 routes. Note also that the output of "/sbin/ip -6 route" is slightly different, so the parser will need to be updated to handle it better.

on my machine:

# ip route show scope global
default via 192.168.132.1 dev br0 onlink
# ip -6 route show scope global
2601:282:8100:3500::/64 dev br0 proto kernel metric 256 expires 293sec pref medium
2601:282:8100:3580::/64 dev br1 proto kernel metric 256 pref medium
2601:282:8100:35a0::/64 dev br2 proto kernel metric 256 pref medium
fe80::/64 dev br0 proto kernel metric 256 pref medium
fe80::/64 dev br1 proto kernel metric 256 pref medium
fe80::/64 dev br2 proto kernel metric 256 pref medium
default via fe80::1 dev br0 proto ra metric 1024 expires 23sec hoplimit 64 pref low

(with -6, "scope global" does not strip directly connected networks) A nexthop router on fe80::/16 is always reachable, even though it's not the same subnet as the IP on the interface: it needs to be handled as a special case for all subnets on the device where such a route is declared (default or otherwise).

[Mike Pontillo (mpontillo)]

Compares to IPv4, I think it's less important that MAAS gathers default routes for IPv6 interfaces from the rack controller. Since IPv6 has stateless auto-configuration built into the protocol, which will allow nodes to automatically discover their default router.

Also, since the current code only looks at IPv4 routes, it could be argued that this is not (yet) a bug. ;-)

[Adam Collard (adam-collard)]

This bug has not seen any activity in the last 6 months, so it is being automatically closed.

If you are still experiencing this issue, please feel free to re-open.

MAAS Team