While trying to add all mobiles into the home LAN #IPv6 it comes out that LineageOS/Android only supports #SLAAC and not #DHCPv6. 
Looks like we will keep the mobiles on #IPv4 till there is a solution. I want full control over addressing clients so SLAAC is no option in the LAN. Otherwise I would need a extra VLAN for mobiles activating SLAAC within this VLAN. Not good.
Looks like we will keep the mobiles on #IPv4 till there is a solution. I want full control over addressing clients so SLAAC is no option in the LAN. Otherwise I would need a extra VLAN for mobiles activating SLAAC within this VLAN. Not good.
goetz 🚲
Als Antwort auf KMJ 🇦🇹 • • •KMJ 🇦🇹
Als Antwort auf goetz 🚲 • • •goetz 🚲
Als Antwort auf KMJ 🇦🇹 • • •@lucasmz
You can only control the whole /64 subnet per routing. The devices get there configuration with the RA / RDNSS or with stateless #DHCPv6, but no static addresses for mobile devices, as it is best practice using temp addresses.
Monitoring should happen with Neighbor Discovery and also implement RA Guard etc.
academy.ripe.net/enrol/index.p…
RIPE NCC Access - RIPE Network Coordination Centre
academy.ripe.netKMJ 🇦🇹
Als Antwort auf goetz 🚲 • • •Litchralee_v6
Als Antwort auf KMJ 🇦🇹 • • •@goetz @lucasmz I can understand a need to pass DHCP options -- except DNS, since RDNSS exists now -- but the security aspect would suggest already having the ability to monitor unexpected L2 traffic, such as for uninvited devices. But in that case, that same capability would also be sufficient to discover SLAAC self-assigned addresses, even when privacy extensions are enabled. SDN does exactly this, coupled with per-user VLANs, but that's a bit much.
Are you sure DHCPv6 is indicated here?
KMJ 🇦🇹
Unbekannter Ursprungsbeitrag • • •Harald Hannelius
Als Antwort auf KMJ 🇦🇹 • • •KMJ 🇦🇹
Unbekannter Ursprungsbeitrag • • •Fully degoogled but rooted here but will checkout for a foss dhcp6client.
@goetz
KMJ 🇦🇹
Unbekannter Ursprungsbeitrag • • •