Re: Reciving multiple RAs causes NetworkManager to storm the network with RSes



Hi,


On Thu, 2019-02-14 at 07:01 -0500, Brian J. Murrell wrote:
On Thu, 2019-02-14 at 07:49 +0100, Thomas Haller via networkmanager-

It's not clear to me what you mean.

Do you mean, that the many RA received at NetworkManager cause
NetworkManager to send too frequent RS (in turn, repeating a
vicious
cycle)?

That's exactly how I understand the description from the author of
the
software on the router that is sending the RAs, yes:

https://github.com/openwrt/odhcpd/issues/122#issuecomment-459263681

OK, makes sense.


Also, NM only sends RS based on timeouts, not based on RAs that it
receives [1].

Assuming no bugs, of course.  Such as could the receiving of the
multiple RAs perhaps be causing the timeout to get reset, etc.?

How/when does the logging in send_rs_timeout:

https://cgit.freedesktop.org/NetworkManager/NetworkManager/tree/src/ndisc/nm-ndisc.c?id=2c881b8064e1cb5b227e5a3c61abfe95c6ddd05a#n711

supposed to get logged?

In 1.10.2-16.el7_5, that code looks pretty similar. NetworkManager
should either log

    "router solicitation sent"

or

    "failure sending router solicitation: ...

for every RS that gets send.


Possibly the logging message was suppressed by journald's ratelimiting
(as the journal would tell you, if that's the case). Make sure to
disable rate-limiting, see [1].


[1] https://cgit.freedesktop.org/NetworkManager/NetworkManager/tree/contrib/fedora/rpm/NetworkManager.conf#n28


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]