@zuriel

With IPv6 you have SLAAC and it looks like you don't need DHCPv6 too, actually, either one or the other. Have a look at the articles I provided in the P.S. section from my post #14
https://en.wikipedia.org/wiki/SLAAC#...uration_(SLAAC)

@kestralis

Your router looks to be an old 4/32 (4MB Flash & 32MB RAM) running OpenWRT 17 (LEDE) and I don't know how much space you have left over in the Flash for additional packages - considering tcpdump-mini. I used OpenWRT 15.x for a long time on such 4/32 routers and looking now in my notes, I found that the tcpdump-mini together with the libpcap dependency needed around 240kB (232) on OpenWRT 15.x. I moved from 15.x directly to 18.x on these 4/32 routers and I wasn't able to install tcpdump-mini anymore. I am left with 80-120kB available and some kB already used for the overlay (OpenWRT configuration).
Should you have some 240-300kB available on your router running OpenWRT 17.x, try installing tcpdump-mini and dump both WAN & LAN (bridge) at the same time, in order to understand if your ISP is triggering the reconfiguration.
tcpdump-mini installation procedure is really simple, on your router, just run:

SLAAC vs DHCPv6 is a bit complicated. You need to assign IPv6 addresses, but you also need DNS servers, a domain name, NTP server, etc. And then you need to consider that some clients don't support all of the possible methods.

I believe older Windows machines only support SLAAC for addressing, and pull the other information they need over DHCPv6.

Android devices don't support DHCPv6 at all, so DNS and everything needs to be embedded in router advertisements.

Windows 10 only got support for RDNSS (DNS in RAs) a couple of years ago.

My network does everything at once, so the Managed, Other and Auto flags are all turned on in my RAs. Clients generate an IPv6 address from the RA, then they get another one from the DHCPv6 server. They get the DNS server address from the RA, and the same address again from the DHCPv6 server. Clients that don't support everything just pay attention to the things they *do* support.

So Android devices pick up the settings they need just from the RAs, but everything else reports to the DHCPv6 server - which lets me automatically register non-Android hosts in my DNS, so connecting by name works without needing to manually assign static addresses.

1 members found this post helpful.

So it is "complicated", but not "super complicated" Thanks for the summary!
... The IPv6 adoption looks like a big mess, one more reason to ignore it and survive with IPv4 - that's me! You good people go on and adopt it!

Besides, I'm still a little confused about why there is so much hectic about the IPv4 pool exhaustion. Private and corporate LANs are under NAT (good choice anyway), there aren't that many public servers worldwide, nor that many subscriber lines permanently connected and all the mobile operators (at least here in Europe) provide you with a internal (NAT-ed) IP, and charge you extra if you need a public IPv4 IP - IPv6 for free is not "available".
Some simple math:
https://en.wikipedia.org/wiki/IPv4_a...#IP_addressing
minus
https://en.wikipedia.org/wiki/Reserved_IP_addresses
still equals almost 4 billion. That's half of the world's population can be online on public IPv4 addresses all the time.
Meaning, I guess I'll survive with IPv4 for the next decade

It's getting hectic now because address exhaustion has progressed to the point where ISPs are doing CGNAT for end users, which breaks a lot of things that ordinary people do like Xbox and PS4 gaming. It's *worse* than NAT, it's NAT behind CGNAT.

The beancounters have looked at the price of big CGNAT gear, the price of buying more IPv4 addresses and the price of deploying IPv6 and IPv6 is suddenly happening really, really quickly. You have the likes of Youtube and Netflix on IPv6, so if ISPs deploy IPv6 they can move a bunch of their traffic over to IPv6 and buy cheaper CGNAT gear.

1 members found this post helpful.