Re: NM removes default route installed by zebra

On Mon, 2018-03-26 at 11:37 -0400, Brian J. Murrell wrote:
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.

Yeah, that's true. If you set ipv6.may-fail=TRUE, and IPv4 completes
first, then NM will consider the device activation as complete.

So, you need ipv6.may-fail=TRUE for that, but then if IPv6 autoconf
fails, the connection goes down. You cannot configure this
independently in NM currently, although it might make sense in some

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
is on IPv4 only.

Maybe. If you run a routing protocol in addition. But commonly you get
both the addresses and the routes from autoconf (or DHCPv4), they
usually go together.
But OK, for static addresses that's more true (except, NM will always
add the device route for each address).

probably not. IPv6 Neighbour discovery times out.

Yes, indeed.  I have discovered that my router was not answering
discovery requests.  I have since fixed that.  But that might have
why that discovery was timing out.

I don't know what zebra is or does.

Zebra is a routing software package that provides TCP/IP based
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

Zebra doesn't configure network devices.  It manages routing

One should be able to use one tool (NM) to manage network interface
addressing and another (Zebra) to manage routing.

that is true for the most part. But if the NetworkManager connection
goes down, it takes everything with it.

But in this case, it seems Zebra is not restoring the default route
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.

If you set ipv6.never-default=yes, NM would never add a default route.
But it also would never remove it. So, that might be useful. However,
as said, when the device goes down, that doesn't matter again.

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
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
this profile and creating a new one.

But we have not yet identified what the correct configuration is yet.

if the profile is already all set to your liking, then good. That just
wasn't clear.


Attachment: signature.asc
Description: This is a digitally signed message part

[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]