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] IPv6, RA and static IPv6 assignment
- Previous message (by thread): [atlas] IPv6, RA and static IPv6 assignment
- Next message (by thread): [atlas] IPv6, RA and static IPv6 assignment
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Philip Homburg
philip.homburg at ripe.net
Sat Sep 14 00:01:26 CEST 2013
On 2013/09/13 22:27 , neitzel at marshlabs.gaertner.de wrote: > A related issue, not mentioned on this list so far: > > I'm v6-multi-homed at home with > > 2a00:1030:100::/48 > 2a00:1030:1004:1000::/56 > > and RA-announce two prefixes/gateways on the probe's net. It's a > matter of luck whether the probe auto-configures its primary address > to the prefix I'd prefer (the one also used in the static prescription). > (That's not specific to the ATLAS probe -- a lot of my gear is > non-deterministic in this respect.) > > At my home I have 4 IPv6 prefixes (2 from xs4all, HE, and 6to4). The best way to retain some sort of sanity is to make sure that all but one are deprecated. Alternatively, make sure that all just work and that it doesn't matter which one is used. The main problem there is reverse DNS. Philip
- Previous message (by thread): [atlas] IPv6, RA and static IPv6 assignment
- Next message (by thread): [atlas] IPv6, RA and static IPv6 assignment
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]