ipv6 – Announce ULA path to Cisco switches by way of SLAAC

I’ve bother with Cisco switches (particularly the CBS350 sequence if that issues) and native IPv6 routing. I run an x86 OpenWrt as router. Its ULA prefix is fd8e:3a8c:273b::/48 which is distributed as a number of /64 prefixes to downstream interfaces. The router’s DHCP configurations for its administration interface are as observe:

config dhcp 'administration'
    choice interface 'administration'
    choice dhcpv4 'server'
    choice begin '112'
    choice restrict '15'
    choice ra 'server' # allow Router Commercial
    choice ra_slaac '1' # announce SLAAC for a prefix (that's, set the A flag in RA messages)
    record ra_flags 'none' # set neither M flag nor O flag
    choice ra_dns '1' # RFC 8106
    choice dhcpv6 'disabled' # disables DHCPv6 server on this interface to make use of SLAAC completely

I plugged a Home windows PC into this subnet, and it will probably obtain the ULA route fd8e:3a8c:273b::/48 simply nice:

Lively Routes:
If  Metric  Community Vacation spot                         Gateway
1   331     ::1/128                                     On-link
19  356     fd8e:3a8c:273b::/48                         fe80::f292:1cff:fe5b:208b
19  356     fd8e:3a8c:273b:80::/64                      On-link
19  356     fd8e:3a8c:273b:80:90:e5cb:a7cb:a2ab/128     On-link
19  356     fd8e:3a8c:273b:80:ee0d:20ae:6531:b8ae/128   On-link
19  356     fe80::/64                                   On-link
19  356     fe80::ef0d:f73b:2b:a5f2/128                 On-link
1   331     ff00::/8                                    On-link
19  356     ff00::/8                                    On-link

On the Cisco change, I take advantage of the next instructions:

cisco(config)#interface vlan 1
cisco(config-if)#ipv6 tackle autoconfig # 'autoconfig' means SLAAC whereas 'dhcp' means DHCPv6

I have no idea why it couldn’t obtain (or autoconfigure) the ULA route:

cisco#present ipv6 route

Codes: > - Finest
            I - ICMP Redirect, S - Static, C - Linked,
            ND - Router Commercial
[d/m]: d - route's distance, m - route's metric

IPv6 Forwarding is disabled

IPv6 Routing Desk - 1 entries

 ND> fd8e:3a8c:273b:80::/64 [0/0]
        by way of :: VLAN 1

I attempted to set a static path to the ULA subnet and it failed:

cisco(config)#ipv6 route fd8e:3a8c:273b::/48 fd8e:3a8c:273b:1::1 # this the the router IPv6 tackle
IPv6 nexthop tackle fd8e:3a8c:273b:1::1 shouldn't be legitimate

I had to make use of the link-local tackle of the router administration interface (fe80::f292:1cff:fe5b:208b) to get it completed:

cisco(config)#ipv6 route fd8e:3a8c:273b::/48 fe80::f292:1cff:fe5b:208bpercentvlan1 vlan1 1
cisco(config)#exit
cisco#present ipv6 route

Codes: > - Finest
            I - ICMP Redirect, S - Static, C - Linked,
            ND - Router Commercial
[d/m]: d - route's distance, m - route's metric

IPv6 Forwarding is disabled

IPv6 Routing Desk - 2 entries

    S> fd8e:3a8c:273b::/48 [1/1]
        by way of fe80::f292:1cff:fe5b:208b VLAN 1
    ND> fd8e:3a8c:273b:80::/64 [0/0]
        by way of :: VLAN 1

Can somebody assist me perceive why the Cisco change didn’t obtain a ULA path to subnet fd8e:3a8c:273b::/48 (whereas the Home windows PC did), and why setting a static route utilizing the router tackle fd8e:3a8c:273b:1::1 failed?

P.S: I simply discovered that my CCTV cameras behave the identical method because the Cisco did: they’ll autoconfigure their IPv6 addresses utilizing the marketed prefix and EUI-64. No path to the /48 subnet was auto-configured although, therefore they might not be reached from different native subnets. I think they lack help for some kind of IPv6 normal.