Re: ipv6 RA: dhcp-level managed

On Fri, 2019-01-04 at 07:19 -0500, Brian J. Murrell wrote:
I see the following message in the debug for NM:

Jan 04 07:02:19 server NetworkManager[1138]: <debug>
[1546603339.8846] ndisc[0x5592e10188c0,"enp2s0"]:   dhcp-level

You're not mistaken about the interpretation of those fields, but...

While NM was running, is it possible there was a previous RA that had
"stateful other conf" (eg the M/managed flag) set? To avoid ping-pong
with RA changes or multiple router advertisements from different
routers NM will cache the "most managed" level.


Which I presume is what leads to:

 1138 ?        Ssl   16:39 /usr/sbin/NetworkManager --no-daemon
26196 ?        S      0:00  \_ /sbin/dhclient -d -q -6 -N -sf
/usr/libexec/nm-dhcp-helper -pf /var/run/ -lf

But what in the following RA contents:

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           :         1800 (0x00000708) seconds
Reachable time            :  unspecified (0x00000000)
Retransmit time           :  unspecified (0x00000000)
 Source link-layer address: D4:6E:0E:64:62:B6
 MTU                      :         1500 bytes (valid)
 Prefix                   : 2001:1234:525e:a700::/64
  On-link                 :          Yes
  Autonomous address conf.:          Yes
  Valid time              :        81098 (0x00013cca) seconds
  Pref. time              :        37898 (0x0000940a) seconds
 Route                    : 2001:456:1d:6f8::/64
  Route preference        :       medium
  Route lifetime          :     infinite (0xffffffff)
 Route                    : 2607:1234:f00f:cd00::/56
  Route preference        :       medium
  Route lifetime          :        81173 (0x00013d15) seconds
 Route                    : 2001:1234:525e:a700::/56
  Route preference        :       medium
  Route lifetime          :        81098 (0x00013cca) seconds
 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::d66e:eff:fe64:62b6

is leading NM to believe that it should be running dhclient?  AFAIK,
have configured this subnet to be autoconfiguration only, which I
suspect is what the "Stateful * conf. : No" is, but I could very well
be mistaken about the interpretation of those fields.


networkmanager-list mailing list
networkmanager-list gnome org

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