ipv6 slaac problems

search terms:
- slaac debugging linux
- slaac "prefix not used" no ip address
- slaac prefix "no ipv6 address"

- "Stateful other conf"


net.ipv6.conf.eth2.accept_ra = 1
net.ipv6.conf.eth2.accept_ra_defrtr = 0
net.ipv6.conf.eth2.accept_ra_pinfo = 0
net.ipv6.conf.eth2.accept_ra_rt_info_max_plen = 0

https://askubuntu.com/questions/652766/ipv6-slaac-icmpv6-router-advertisments-are-ignored-by-wlan1-interface


 ndisc6 gathers a few diagnostic tools for IPv6 networks including:
  - ndisc6, which performs ICMPv6 Neighbor Discovery in userland,
  - rdisc6, which performs ICMPv6 Router Discovery in userland,
  - rltraceroute6, a UDP/ICMP IPv6 implementation of traceroute,
  - tcptraceroute6, a TCP/IPv6-based traceroute implementation,
  - tcpspray6, a TCP/IP Discard/Echo bandwidth meter,
  - addrinfo, easy script interface for hostname and address resolution,
  - dnssort, DNS sorting script.



root@gpc-rom:~# LC_ALL=C rdisc6 eth2
Soliciting ff02::2 (ff02::2) on eth2...

Hop limit                 :           64 (      0x40)
Stateful address conf.    :           No
Stateful other conf.      :          Yes
Mobile home agent         :           No
Router preference         :       medium
Neighbor discovery proxy  :           No
Router lifetime           :         1800 (0x00000708) seconds
Reachable time            :  unspecified (0x00000000)
Retransmit time           :  unspecified (0x00000000)
 Prefix                   : 2a02:238:f065::/48
  On-link                 :          Yes
  Autonomous address conf.:          Yes
  Valid time              :        86400 (0x00015180) seconds
  Pref. time              :        14400 (0x00003840) seconds
 Recursive DNS server     : 2a02:238:f065::1
  DNS server lifetime     :          600 (0x00000258) seconds
 DNS search list          : mogic.company 
  DNS search list lifetime:          600 (0x00000258) seconds
 MTU                      :         1500 bytes (valid)
 Source link-layer address: 52:B8:45:B5:6B:33
 from fe80::50b8:45ff:feb5:6b33


cweiske@gpc-rom:~$ nmcli device show eth2

root@gpc-rom:~# nmcli monitor
root@gpc-rom:~# nmcli general logging level DEBUG domains ALL

$ jourctrl


NetworkManager[1297]: <debug> platform-linux: sysctl: setting '/proc/sys/net/ipv6/conf/eth2/accept_ra' to '1' (current value is '0')
NetworkManager[1297]: <debug> platform-linux: sysctl: setting '/proc/sys/net/ipv6/conf/eth2/accept_ra_defrtr' to '0' (current value is identical)
NetworkManager[1297]: <debug> platform-linux: sysctl: setting '/proc/sys/net/ipv6/conf/eth2/accept_ra_pinfo' to '0' (current value is identical)
NetworkManager[1297]: <debug> platform-linux: sysctl: setting '/proc/sys/net/ipv6/conf/eth2/accept_ra_rtr_pref' to '0' (current value is identical)


NetworkManager[1297]: <debug> ndisc[0x559bf34acd40,"eth2"]: router solicitation sent
NetworkManager[1297]: <debug> ndisc[0x559bf34acd40,"eth2"]: scheduling router solicitation retry in 4 seconds.
NetworkManager[1297]: <debug> ndisc-lndp[0x559bf34acd40,"eth2"]: processing libndp events
NetworkManager[1297]: <debug> ndisc-lndp[0x559bf34acd40,"eth2"]: received router advertisement at 6554
NetworkManager[1297]: <debug> ndisc[0x559bf34acd40,"eth2"]: scheduling next now/lifetime check: 1800 seconds
NetworkManager[1297]: <debug> ndisc[0x559bf34acd40,"eth2"]: neighbor discovery configuration changed [dGRSD]:
NetworkManager[1297]: <debug> ndisc[0x559bf34acd40,"eth2"]:   dhcp-level otherconf
NetworkManager[1297]: <debug> ndisc[0x559bf34acd40,"eth2"]:   gateway fe80::50b8:45ff:feb5:6b33 pref medium exp 1799,9981
NetworkManager[1297]: <debug> ndisc[0x559bf34acd40,"eth2"]:   route 2a02:238:f065::/48 via :: pref medium exp 86399,9981
NetworkManager[1297]: <debug> ndisc[0x559bf34acd40,"eth2"]:   dns_server 2a02:238:f065::1 exp 7199,9981
NetworkManager[1297]: <debug> ndisc[0x559bf34acd40,"eth2"]:   dns_domain mogic.company exp 7199,9981



RFC 4861

      M              1-bit "Managed address configuration" flag.  When
                     set, it indicates that addresses are available via
                     Dynamic Host Configuration Protocol [DHCPv6].

                     If the M flag is set, the O flag is redundant and
                     can be ignored because DHCPv6 will return all
                     available configuration information.

      O              1-bit "Other configuration" flag.  When set, it
                     indicates that other configuration information is
                     available via DHCPv6.  Examples of such information
                     are DNS-related information or information on other
                     servers within the network.

        Note: If neither M nor O flags are set, this indicates that no
        information is available via DHCPv6.


64 bit präfix war das problem
48 war vorher, mit 64 gehts