Hi Stephane, I'm doing it right now and @ you in the ticket. Thank you (and everyone else!) for taking a look. Best, -- Jacobo Aragunde Software Engineer at Igalia On 2/7/19 14:42, Stephane Desneux wrote: > Resolution of .local domain is done through mDNS (nothing directly related to > DHCP server or local DNS). > > On Linux platforms, the avahi daemon is usually responsible for implementing > mDNS (client part as well as server part: mDNS means 'multicast DNS' => both > sides are usually needed). > > AFAICS, avahi just "disappeared" from the distro: > > Guppy 7.0.3: > avahi-daemon aarch64 0.6.32 > avahi-dev aarch64 0.6.32 > libavahi-client3 aarch64 0.6.32 > libavahi-common3 aarch64 0.6.32 > libavahi-core7 aarch64 0.6.32 > libavahi-glib1 aarch64 0.6.32 > libavahi-gobject0 aarch64 0.6.32 > > Master: > libavahi-client3 aarch64 0.7 > libavahi-common3 aarch64 0.7 > libavahi-glib1 aarch64 0.7 > > Maybe it was pulled by default in 'rocko' and not in 'thud'. In any case, this > is easy to solve. > > Please file a Jira ticket for that missing package. > > Best regards, > --- > Stephane Desneux - CTO - IoT.bzh > stephane.desneux@xxxxxxx - www.iot.bzh > > On 02/07/2019 13:07, Jan-Simon Moeller wrote: >> Hi Jacobo! >> >> I think the name resolution is done by your local router (dhcp server). >> Now I don't know if or what changed, but during the dhcp handshake >> the dhcp server would get to know the hostname of the board and >> then update the router's dns. >> Why this does not work atm I can't tell. >> >> Best, >> Jan-Simon >> On Tue, Jul 2, 2019 at 12:03 PM Jacobo Aragunde Pérez <jaragunde@xxxxxxxxxx >> <mailto:jaragunde@xxxxxxxxxx>> wrote: >> >> Hi, Johann, >> >> thanks for answering! >> >> The ssh daemon is running, I can still ssh into the board provided that >> I know the IP address (checking the local DHCP server log, for example). >> >> The error I get is just "Could not resolve hostname": >> >> $ ssh root@intel-corei7-64.local >> ssh: Could not resolve hostname intel-corei7-64.local: Name or service >> not known >> $ ssh root@192.168.1.16 <mailto:root@192.168.1.16> >> Last login: Tue Jul 2 09:00:06 2019 from 192.168.1.13 >> intel-corei7-64:~# >> >> If I simply swap the card with a Guppy image, the first command would >> work (minus the known_hosts warning). >> >> Best, >> -- >> Jacobo Aragunde >> Software Engineer at Igalia >> >> >> On 2/7/19 10:38, Johann Cahier wrote: >> > Hello Jacobo, >> > >> > >> > As far as I know, there were no modification done, lately, in SSH server >> > configuration... So, it should still work as with previous versions. >> > >> > >> > What is the error you are exactly facing ? Are you able to ping >> > intel-corei7-64.local address ? >> > >> > Are you able to connect to serial console ? If so, is the SSH server >> > running (systemctl status sshd) ? >> > >> > >> > Thanks in advance for your feedback ! >> > >> > Johann. >> > >> > >> > On 29/06/2019 11:37, Jacobo Aragunde Pérez wrote: >> >> Hi, >> >> >> >> with my default setup at home, I always could ssh into an AGL board >> >> simply by its host name, like: `ssh root@intel-corei7-64.local` >> >> >> >> This doesn't work in Halibut images (no changes in my network >> >> equipment). Am I the only one? Do you know if anything has changed in >> >> that regard? >> >> >> >> Best, >> > >> _______________________________________________ >> automotive-discussions mailing list >> automotive-discussions@xxxxxxxxxxxxxxxxxxxxxxxxx >> <mailto:automotive-discussions@xxxxxxxxxxxxxxxxxxxxxxxxx> >> https://lists.linuxfoundation.org/mailman/listinfo/automotive-discussions >> >> >> _______________________________________________ >> automotive-discussions mailing list >> automotive-discussions@xxxxxxxxxxxxxxxxxxxxxxxxx >> https://lists.linuxfoundation.org/mailman/listinfo/automotive-discussions >> > _______________________________________________ automotive-discussions mailing list automotive-discussions@xxxxxxxxxxxxxxxxxxxxxxxxx https://lists.linuxfoundation.org/mailman/listinfo/automotive-discussions