Hi, Raquel. Thanks, there are indeed a couple of messages, not sure if related: Jul 02 13:11:19 intel-corei7-64 systemd-tmpfiles[139]: [/etc/tmpfiles.d/connman_resolvconf.conf:1] Line references path below legacy directory /var/run/, updating /var/run/connman → /run/connman; please update the tmpfiles.d/ drop-in file accordingly. Jul 02 13:11:38 intel-corei7-64 connmand[643]: Failed to set domainname to home I will open a ticket, as requested by Stephane. Best, -- Jacobo Aragunde Software Engineer at Igalia On 2/7/19 13:19, Raquel Medina wrote: > > > On Tue, Jul 2, 2019 at 1:09 PM Jan-Simon Moeller > <jsmoeller@xxxxxxxxxxxxxxxxxxx <mailto:jsmoeller@xxxxxxxxxxxxxxxxxxx>> > 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? > > > Hi Jacobo, > Have you checked the journal to test whether there are any issues logged > by avahi /connman? > > best, > raquel > > >> > >> 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 > <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