Re: spamming router with router solicitations

On Sat, May 25, 2019 at 03:47:37PM -0400, Brian J. Murrell wrote:
On Sat, 2019-05-25 at 08:52 +0200, Beniamino Galvani via
networkmanager-list wrote:

Hi, it is not NM sending those RS.

But they stop as soon as I stop NM.

If it were, you would see in the
journal messages like:

  ndisc[0x55a43c15e0e0,"ens9"]: router solicitation sent

I'm not in a position to argue that point, but if the storm can be
stopped and started by stopping and starting NM, that's pretty strong
evidence that NM is doing it, wouldn't you agree?

Are you sure you don't have other daemons like systemd-networkd or
something else active which are racing with NM? From logs it is pretty
clear that NM is sending exactly one router solicitation at:

 May 25 15:42:55 NetworkManager[10973]: <debug> [1558813375.1729] 
ndisc[0x55a336c550e0,"enp2s0"]: router solicitation sent

However it could be that NM is configuring the kernel in a wrong way.

I see from the log that you set a IPv6 token; can you please try
without it if it makes any difference?

But that machine needs to have a predictable, easily remembered
address, which it does not get without a token.

In any case, as a debugging step, I did disable it and restart NM and
the storm did not start up with it.  When I re-enabled the token again
and restarted NM, the storm started when it started, so it does seem to
be related to using a token.

Also, please attach a log from
the beginning of the profile activation.

There is no "profile activation" because this is a headless server,
hence the reason for the token.  I'll attach the NM log from the time
it is started up.  Hopefully that provides what you are looking for.

Yes, it is ok. Note that you can force a new activation of a
connection with:

 nmcli connection up $con_name

where $con_name if the name of the connection obtained through:

 nmcli connection show

In your case the connection name is equal to the device name -
enp2s0. The reactivation is useful to apply changes after modifying a
connection without the need to restart NM or reboot.

Can you also attach the output of

 nmcli connection show enp2s0



Attachment: signature.asc
Description: PGP signature

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