@kronicd Unless android has implemented DHCPv6 and nobody is talking about it, no, no it’s not. It would still need me to route the entire /64 to one network after all for SLAAC.
Unless you’re suggesting I install more-specific routes on the other networks? maybe a /65 or /66 on them? But in that case, wouldn’t the main network, with it’s full /64 prefix, have issues reaching those other hosts… hmm. Unless I deploy it with ULA addresses too. And treat the GUA addresses as just for internet connectivity.
Might still have to NAT66 it for other networks that may see android devices…
Might experiment with it once my opnsense box arrives I guess. Don’t want to muck around with that on openwrt.
I just wish I got like a /60 at least.
I suppose tunnelling to a VPS is one option, but I’d rather use NAT66 over that because it’d have better throughput/latency.
@kronicd Unless android has implemented DHCPv6 and nobody is talking about it, no, no it’s not. It would still need me to route the entire /64 to one network after all for SLAAC.
Unless you’re suggesting I install more-specific routes on the other networks? maybe a /65 or /66 on them? But in that case, wouldn’t the main network, with it’s full /64 prefix, have issues reaching those other hosts… hmm. Unless I deploy it with ULA addresses too. And treat the GUA addresses as just for internet connectivity.
Might still have to NAT66 it for other networks that may see android devices…
Might experiment with it once my opnsense box arrives I guess. Don’t want to muck around with that on openwrt.
I just wish I got like a /60 at least.
I suppose tunnelling to a VPS is one option, but I’d rather use NAT66 over that because it’d have better throughput/latency.