[atlas] Strange IPv6 problem with Atlas

On Tue, Oct 2, 2012 at 4:56 AM, Philip Homburg <philip.homburg at ripe.net>wrote:

> > 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.
>

Agreed. This will not work.

That said - why is SSH trying to communicate over IPv6 with a link-local
address in the first place? getaddrinfo should be ranking the global IPv4
address above the link-local IPv6 address and thus causing SSH to prefer
IPv4...
-------------- next part --------------
An HTML attachment was scrubbed...
URL: </ripe/mail/archives/ripe-atlas/attachments/20121002/7d7178a0/attachment.html>