Hmm, that's really odd. I'm sorry you haven't had a solution yet.
I have a set of test containers to test ipv6 networking. My netplan
config for a static IPv6 address is https://github.com/daxtens/ipv6
-config-demos/blob/master/static-networkd/60-ipv6.yaml and it looks a
lot like yours. It can definitely get past the next hop.
If I enter that container and dump the same info as you have:
root@static-networkd:~# ip -6 route
fd8f:1d7d:b141::/64 dev eth0 proto kernel metric 256 pref medium
fe80::/64 dev eth0 proto kernel metric 256 pref medium
default via fd8f:1d7d:b141::1 dev eth0 proto static metric 1024 pref medium
Interestingly here I'm missing all the nexthop stuff you have...
root@static-networkd:~# route -6
Kernel IPv6 routing table
Destination Next Hop Flag Met Ref Use If
fd8f:1d7d:b141::/64 [::] U 256 2 5 eth0
fe80::/64 [::] U 256 1 0 eth0
[::]/0 _gateway UG 1024 2 18 eth0
ip6-localhost/128 [::] Un 0 3 4 lo
static-networkd/128 [::] Un 0 3 20 eth0
static-networkd/128 [::] Un 0 3 8 eth0
ip6-mcastprefix/8 [::] U 256 2 76 eth0
[::]/0 [::] !n -1 1 1 lo
And again here I don't have a bunch of routes you do.
I wonder how you're ending up with the nexthop stuff. Do you have any
virtual networking stuff on your host? VMs? openvswitch? Anything else
that would mess with routes?
Regards,
Daniel
** Changed in: nplan (Ubuntu)
Assignee: MOHAMMED FAHAD MUSHAHID (89mfahad) => Daniel Axtens (daxtens)
** Changed in: nplan (Ubuntu)
Status: In Progress => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1735944
Title:
cannot route IPv6 addresses
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nplan/+bug/1735944/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
