Re: multiple RAs spamming log with policy: set 'enp2s0' (enp2s0) as default for IPv6 routing and DNS



On Tue, 2019-01-22 at 08:50 -0500, Brian J. Murrell wrote:
My router is (now) sending multiple RAs instead of aggregating all
prefixes/routes into a single RA as such:

Soliciting ff02::2 (ff02::2) on pc_bridge...

Hop limit                 :           64 (      0x40)
Stateful address conf.    :           No
Stateful other conf.      :           No
Mobile home agent         :           No
Router preference         :       medium
Neighbor discovery proxy  :           No
Router lifetime           :            0 (0x00000000) seconds
Reachable time            :  unspecified (0x00000000)
Retransmit time           :  unspecified (0x00000000)
 Source link-layer address: 6C:B0:CE:F5:1E:4A
 MTU                      :         1500 bytes (valid)
 Prefix                   : fd31:aeb1:48df::/64
  On-link                 :          Yes
  Autonomous address conf.:          Yes
  Valid time              :     infinite (0xffffffff)
  Pref. time              :     infinite (0xffffffff)
 Route                    : fd31:aeb1:48df::/48
  Route preference        :       medium
  Route lifetime          :     infinite (0xffffffff)
 Recursive DNS server     : fd31:aeb1:48df::2
  DNS server lifetime     :         6000 (0x00001770) seconds
 from fe80::6eb0:ceff:fef5:1e4a

Hop limit                 :           64 (      0x40)
Stateful address conf.    :           No
Mobile home agent         :           No
Router preference         :       medium
Neighbor discovery proxy  :           No
Router lifetime           :         1800 (0x00000708) seconds
Reachable time            :  unspecified (0x00000000)
Retransmit time           :  unspecified (0x00000000)
 Source link-layer address: 6C:B0:CE:F5:1E:4A
 MTU                      :         1500 bytes (valid)
 Prefix                   : 2001:1234:5678:a700::/64
  On-link                 :          Yes
  Autonomous address conf.:          Yes
  Valid time              :        84531 (0x00014a33) seconds
  Pref. time              :        41331 (0x0000a173) seconds
 Route                    : 2001:1234:5678:a700::/56
  Route preference        :       medium
  Route lifetime          :        84531 (0x00014a33) seconds
 Recursive DNS server     : fd31:aeb1:48df::1
  DNS server lifetime     :         6000 (0x00001770) seconds
 from fe80::6eb0:ceff:fef5:1e4a

But now that it's going this NetworkManager-1.10.2-16.el7_5.x86_64 is
spamming the log as such:

Jan 22 08:49:40 server NetworkManager[1842]:
<info>  [1548164980.5807] policy: set 'enp2s0' (enp2s0) as default
for IPv6 routing and DNS
Jan 22 08:49:42 server NetworkManager[1842]:
<info>  [1548164982.0102] policy: set 'enp2s0' (enp2s0) as default
for IPv6 routing and DNS
Jan 22 08:49:42 server NetworkManager[1842]:
<info>  [1548164982.5751] policy: set 'enp2s0' (enp2s0) as default
for IPv6 routing and DNS
Jan 22 08:49:43 server NetworkManager[1842]:
<info>  [1548164983.2225] policy: set 'enp2s0' (enp2s0) as default
for IPv6 routing and DNS
Jan 22 08:49:43 server NetworkManager[1842]:
<info>  [1548164983.5056] policy: set 'enp2s0' (enp2s0) as default
for IPv6 routing and DNS
Jan 22 08:49:44 server NetworkManager[1842]:
<info>  [1548164984.7597] policy: set 'enp2s0' (enp2s0) as default
for IPv6 routing and DNS
Jan 22 08:49:45 server NetworkManager[1842]:
<info>  [1548164985.4752] policy: set 'enp2s0' (enp2s0) as default
for IPv6 routing and DNS
Jan 22 08:49:46 server NetworkManager[1842]:
<info>  [1548164986.1900] policy: set 'enp2s0' (enp2s0) as default
for IPv6 routing and DNS
Jan 22 08:49:46 server NetworkManager[1842]:
<info>  [1548164986.8223] policy: set 'enp2s0' (enp2s0) as default
for IPv6 routing and DNS
Jan 22 08:49:47 server NetworkManager[1842]:
<info>  [1548164987.5415] policy: set 'enp2s0' (enp2s0) as default
for IPv6 routing and DNS
Jan 22 08:49:47 server NetworkManager[1842]:
<info>  [1548164987.5820] policy: set 'enp2s0' (enp2s0) as default
for IPv6 routing and DNS
Jan 22 08:49:47 server NetworkManager[1842]:
<info>  [1548164987.7178] policy: set 'enp2s0' (enp2s0) as default
for IPv6 routing and DNS
Jan 22 08:49:47 server NetworkManager[1842]:
<info>  [1548164987.8289] policy: set 'enp2s0' (enp2s0) as default
for IPv6 routing and DNS
Jan 22 08:49:48 server NetworkManager[1842]:
<info>  [1548164988.2436] policy: set 'enp2s0' (enp2s0) as default
for IPv6 routing and DNS
Jan 22 08:49:48 server NetworkManager[1842]:
<info>  [1548164988.9381] policy: set 'enp2s0' (enp2s0) as default
for IPv6 routing and DNS
Jan 22 08:49:49 server NetworkManager[1842]:
<info>  [1548164989.1140] policy: set 'enp2s0' (enp2s0) as default
for IPv6 routing and DNS
Jan 22 08:49:49 server NetworkManager[1842]:
<info>  [1548164989.8361] policy: set 'enp2s0' (enp2s0) as default
for IPv6 routing and DNS
Jan 22 08:49:49 server NetworkManager[1842]:
<info>  [1548164989.9141] policy: set 'enp2s0' (enp2s0) as default
for IPv6 routing and DNS
Jan 22 08:49:51 server NetworkManager[1842]:
<info>  [1548164991.3413] policy: set 'enp2s0' (enp2s0) as default
for IPv6 routing and DNS
Jan 22 08:49:51 server NetworkManager[1842]:
<info>  [1548164991.5886] policy: set 'enp2s0' (enp2s0) as default
for IPv6 routing and DNS
Jan 22 08:49:51 server NetworkManager[1842]:
<info>  [1548164991.6961] policy: set 'enp2s0' (enp2s0) as default
for IPv6 routing and DNS

Thoughts?


Hi,


that's odd, because NM should only log when the value actually changes.
At <info> level it's not clear whether that is the case. Can you enable
debug logging? (See [1]).

As workaround (for the flodding) you can disable the "CORE" domain with
"INFO" level. See also [1].

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


best,
Thomas

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]