On Tue, Oct 2, 2012 at 4:56 AM, Philip Homburg <span dir="ltr">&lt;<a href="mailto:philip.homburg@ripe.net" target="_blank">philip.homburg@ripe.net</a>&gt;</span> wrote:<br><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">

<div class="im">&gt; fe80::225:90ff:fe92:2478 &gt; ff02::1: [icmp6 sum ok] ICMP6, router<br>
&gt; advertisement, length 64<br>
&gt;  hop limit 64, Flags [none], pref medium, router lifetime 1800s,<br>
&gt; reachable time 0s, retrans time 0s<br>
&gt;  prefix info option (3), length 32 (4): 2a02:a00:e000:b:e6::/96, Flags<br>
&gt; [onlink, auto, router], valid time 86400s, pref. time 14400s<br>
&gt;  mtu option (5), length 8 (1):  1400<br>
&gt;  source link-address option (1), length 8 (1): 00:25:90:92:24:78<br><br>
</div>A /96 is not according the specs. For SLAAC on ethernet you need to have<br>
a /64.<br>
</blockquote></div><br><div>Agreed. This will not work.</div><div><br></div><div>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...</div>