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] Strange IPv6 problem with Atlas
- Previous message (by thread): [atlas] Strange IPv6 problem with Atlas
- Next message (by thread): [atlas] Strange IPv6 problem with Atlas
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Philip Homburg
philip.homburg at ripe.net
Mon Oct 1 21:56:35 CEST 2012
On 10/1/12 21:50 , Max Grobecker wrote: > My routing advertisements are currently looking like that: > > fe80::225:90ff:fe92:2478 > ff02::1: [icmp6 sum ok] ICMP6, router > advertisement, length 64 > hop limit 64, Flags [none], pref medium, router lifetime 1800s, > reachable time 0s, retrans time 0s > prefix info option (3), length 32 (4): 2a02:a00:e000:b:e6::/96, Flags > [onlink, auto, router], valid time 86400s, pref. time 14400s > mtu option (5), length 8 (1): 1400 > source link-address option (1), length 8 (1): 00:25:90:92:24:78 > > > A /96 is not according the specs. For SLAAC on ethernet you need to have a /64.
- Previous message (by thread): [atlas] Strange IPv6 problem with Atlas
- Next message (by thread): [atlas] Strange IPv6 problem with Atlas
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]