Thanks for all the input. I didn’t want to mess this thread if it was different issue, but it seems to me it may have the same root cause. I learn IPv6 as I go, so apologize for any eventual nonsenses
Here is my further observation:
- ULA is pointless for me, I have turned it off completely.
- SLAAC is pointless for me, I have turned it off completely.
Please, how do you assign those addresses to clients? By DHCP reservations [Static Leases http://192.168.1.1/cgi-bin/luci/admin/network/dhcp as described below] ?
I don’t think it makes a difference, since the issue is in both cases with “short” IPv6 addesses provided by DHCPv6. I do not use SLAAC but it should not affect it.
If I turn on Stateless [details below], the
Windows10 [Pro, 1903, all default settings] machines get those “long” addresses as well, such as:
IPv6 Address. . . . . . . . . . . : 2a01:510:abcd:efff::55
IPv6 Address. . . . . . . . . . . : 2a01:510:abcd:efff:5932:d895:ea8:7695
Temporary IPv6 Address. . . . . . : 2a01:510:abcd:efff:5d0f:3800:a5b3:74e5
After router reboot:
2a01:510:abcd:efff::55 is lost
2a01:510:abcd:efff:5932:d895:ea8:7695 is good
2a01:510:abcd:efff:5d0f:3800:a5b3:74e5 gets changed to
2a01:510:abcd:efff:5413:5b52:5d54:dc54 for example
Without reboot it does not get the :55 back even after 5 hours
ipconfig /renew does not acquire ::55 back
After Windows machine reboot it gets
2a01:510:abcd:efff::55 back again
After LAN cable unplugged for 5 mins and plugged back, it gets the ::55 immediately.
SLAAC [stateless, the long addresses, based on RA and MAC] I don’t want. What I only need is the short = statefull address provided by DHCPv6.
- When I turn the DHCPv6-Service off, the client only get [from RA] two long IPv6 - static one [MAC based] and temporary one [privacy extension].
- When I turn the DHCPv6-Service on and DHCPv6-Mode Stateless only, the client gets all three IPv6 as shown above, but the ::55 changes to ::6f4 and gets different after every reboot.
- When I turn the DHCPv6-Service on and DHCPv6-Mode Stateless+Statefull, the client gets all three IPv6 as shown above, and keeps the ::55, probably forever.
- When I turn the DHCPv6-Service on and DHCPv6-Mode Statefull only, the client gets only the ::55 one, and seems to keep it forever. If I want to have the ::55 reserved always for the client, I can go to DHCP [http://192.168.1.1/cgi-bin/luci/admin/network/dhcp] and make Static Leases for it. That will make following record to
option name 'test'
option dns '1'
option mac '00:15:5D:01:0A:15'
option duid '0001000125c516e600155d010a15'
option ip '10.1.1.88'
option hostid '88'
It will make sure this will always be the same:
IPv6 Address. . . . . . . . . . . : 2a01:510:abcd:efff::88
IPv4 Address. . . . . . . . . . . : 10.1.1.88
Another way is to hardcode all addresses manually on the clients. Not recommeded though.
My understanding is, the ISP does not have anything to do with it, they only provide Prefix Delegated and thats it. It is the Omnia who is providing clients with RA, and Stateless/Statefull DHVP6 out of the Prefix. Right?
IPv6 suffix on http://192.168.1.1/cgi-bin/luci/admin/network/network/lan only affects the address of the very own router’s LAN interface, not any clients.
That’s exactly what I have done.
I played with all combinations of ND Proxy and Relay, it did not do anything or it only broke things completely.
I have no experience with DS-LITE, I saw that only in UPC network at my friends’ home, but the cable modem/router provided by UPC did not have any configuration variability, almost everything is hidden to customers.
My own conclusion so far - because everything else work just fine, I have to live with required Windows restart after every Omnia reboot…