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?
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. Cheers, b.
Attachment:
NM.log
Description: Text Data
Attachment:
signature.asc
Description: This is a digitally signed message part