On Mon, 2018-03-26 at 16:24 +0200, Thomas Haller wrote:
++ ipv6.may-fail = FALSE set ipv6.may-fail to yes, if you want that the connection stays up without IPv6.
I don't want the connection to be considered up until IPv6 configuration has happened. Other things start on the machine that require the interface to have IPv6 addressing in place.
here you say "statically assigned". Below you say "that defeats the purpose of using a dynamic routing protocol".
Statically assigned IP addresses and dynamic routing protocols are orthogonal. You can run a dynamic routing protocol while statically assigning IP addresses. Moreover the dynamic routing in this situation is on IPv4 only.
probably not. IPv6 Neighbour discovery times out.
Yes, indeed. I have discovered that my router was not answering router discovery requests. I have since fixed that. But that might have been why that discovery was timing out.
I don't know what zebra is or does.
https://en.wikipedia.org/wiki/GNU_Zebra Zebra is a routing software package that provides TCP/IP based routing services with routing protocols support such as RIP, OSPF and BGP.
It's a bad idea to have two programs (NetworkManager and zebra(?)) configuring the same networking device.
Zebra doesn't configure network devices. It manages routing [tables]. One should be able to use one tool (NM) to manage network interface addressing and another (Zebra) to manage routing. But in this case, it seems Zebra is not restoring the default route it gets from OSPF if/when NM tears down the interface during initial configuration. I will experiment and see if I can reproduce this outside of system booting.
What you want.
NM to manage the interface addressing.
What does zebra do?
Manage the routing tables.
(e.g. the bogus ::2 token).
Why is the ::2 token bogus? How does one configure the host portion of the IP address(es) constructed from the IPv6 router advertisement's prefixes to be a static value if it's not with the token?
I think you should fix the configuration, simpliest by just deleting this profile and creating a new one.
But we have not yet identified what the correct configuration is yet. b.
Attachment:
signature.asc
Description: This is a digitally signed message part