This archive is retained to ensure existing URLs remain functional. It will not contain any emails sent to this mailing list after July 1, 2024. For all messages, including those sent before and after this date, please visit the new location of the archive at https://mailman.ripe.net/archives/list/ripe-atlas@ripe.net/
[atlas] Probe DHCPv6 support
- Next message (by thread): [atlas] A new year's break for the probes
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
ripe at brite.cz
ripe at brite.cz
Thu Jan 2 11:46:43 CET 2020
+1 for DHCP6 support Cheers Jiri ______________________________________________________________ > Od: "Aleksi Pirttimaa" <aleksipirttimaa at protonmail.com> > Komu: "ripe-atlas at ripe.net" <ripe-atlas at ripe.net> > Datum: 02.01.2020 10:16 > Předmět: [atlas] Probe DHCPv6 support > >Hi! > >I recently received my v4 probe and I'm very happy with it. But unfortunately it doesn't support DHCPv6. I present a practical reason for implementing a DHCPv6 client on the probe. > >You see, my ISP doesn't send router advertisements with the prefix for stateless autoconfiguration set, and instead DHCPv6 must be used. > >I believe their decision could have something to do with the fact that the regulating body here requires ISP's to prevent IP address spoofing in consumer plans. And to meet that requirement my ISP may be using a feature similar to Cisco's IP source guard, where switch ports and/or mac addresses are passively associated to leased ip's or prefixes, breaking SLAAC. Unfortunately they hate letting consumers talk with their engineers so it's difficult to speculate this further. > >For now, I've put a stateful firewall appliance in front of the probe which provides SLAAC, it works just fine. > >Do you think a DHCPv6 client should be implemented? > >
- Next message (by thread): [atlas] A new year's break for the probes
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]