On Thu, 2019-01-31 at 06:46 -0500, Brian J. Murrell wrote:
On Thu, 2019-01-24 at 17:15 -0500, Brian J. Murrell wrote:On Tue, 2019-01-22 at 16:25 -0500, Brian J. Murrell wrote:Seems I already had level=TRACE set.Was that debug useful?So, it seems this behaviour is more harmful to the network than just spamming a log on the NM host. It's causing a message storm with the router that is sending the multiple RAs in that NM is sending RS messages in response to the RAs crushing the router with RS messages. Given that, can any more importance be put on this issue?
Hi Brian, 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)? I wouldn't see that from the log. There are no log lines about additional router solicitations sent by NetworkManager. Also, NM only sends RS based on timeouts, not based on RAs that it receives [1]. can you clarify what you think is the harmful behavior? Also, does tcpdump/wireshark show that NM sends too many RS? [1] https://cgit.freedesktop.org/NetworkManager/NetworkManager/tree/src/ndisc/nm-ndisc.c?id=2c881b8064e1cb5b227e5a3c61abfe95c6ddd05a#n698 best, Thomas
Attachment:
signature.asc
Description: This is a digitally signed message part