<div dir="ltr"><div class="gmail_extra"><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">In ubuntu, an attempt to connect using pi@raspberrypi.local fails with<br>
ssh: Could not resolve hostname raspberrypi.local: Name or service not<br>
known<br>
$ssh -6 pi@raspberrypi.local<br>
ssh: Could not resolve hostname raspberrypi.local: Name or service not<br>
known<br>
<br>
Curiously, an attempt with the IPv6 address fails, but with Connection<br>
refused.<br>
<br>
$ ssh -6 pi@fe80::3d6e:a03a:33b8:12f5%<wbr>enp0s20u9u1u3<br>
ssh: connect to host fe80::3d6e:a03a:33b8:12f5%<wbr>enp0s20u9u1u3 port 22:<br>
Connection refused<br>
<br>
<br>
$ ifconfig<br>
eno1: flags=4099<UP,BROADCAST,<wbr>MULTICAST> mtu 1500<br>
ether 94:de:80:6d:24:1c txqueuelen 1000 (Ethernet)<br>
RX packets 0 bytes 0 (0.0 B)<br>
RX errors 0 dropped 0 overruns 0 frame 0<br>
TX packets 0 bytes 0 (0.0 B)<br>
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0<br>
device interrupt 20 memory 0xf3600000-f3620000<br>
<br>
enp0s20u9u1u3: flags=4163<UP,BROADCAST,<wbr>RUNNING,MULTICAST> mtu 1500<br>
inet6 fe80::3d6e:a03a:33b8:12f5 prefixlen 64 scopeid<br>
0x20<link><br>
ether f6:38:64:f8:7e:a4 txqueuelen 1000 (Ethernet)<br>
RX packets 14 bytes 1937 (1.9 KB)<br>
RX errors 1 dropped 0 overruns 0 frame 1<br>
TX packets 101 bytes 16782 (16.7 KB)<br>
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0<br>
<br>
enp3s0: flags=4163<UP,BROADCAST,<wbr>RUNNING,MULTICAST> mtu 1500<br>
inet 192.168.1.13 <snip><br>
<br>
lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536<br>
<snip><br>
<br>
$ssh -6 pi@raspberrypi.local<br>
ssh: Could not resolve hostname raspberrypi.local: Name or service not<br>
known<br>
<br>
$ ssh -6 pi@fe80::3d6e:a03a:33b8:12f5%<wbr>enp0s20u9u1u3<br>
ssh: connect to host fe80::3d6e:a03a:33b8:12f5%<wbr>enp0s20u9u1u3 port 22:<br>
Connection refused<br></blockquote><div><br></div><div>If all these commands are ran on your ubuntu desktop computer, the last ssh command is attempting ssh to your localhost, not the remote pi card. Try to manually type in the ipv6 local scope address of the remote pi card (but include the %xxx data, since local scope addresses require that to be present).</div><div><br></div><div>The mdns/avahi part I can not answer for, since I have never used it. But you claim that it should work, since windows and os-x computers automatically can fint the PI card, so it is something with the ubuntu desktop machine that has the issue. Which avahi/mdns packages do you have installed, and are the daemon running?</div><div><br></div><div><br></div><div> --</div><div><br></div><div>Stian Skjelstad</div></div>
</div></div>