Jacobo,
I really doubt that the DNS entry / hostname "intel-corei7-64.local" is
configured by the AGL image... But i may be wrong.
I think it's more likely a server on your side that should allocate this
address to your board, but doesn't "recognize" it (because of some
difference in the builds).
This "known_hosts warning" rings me a bell. The board certificate is
indeed regenerated (known_host is a file to store their certificate, so
you can have a warning if either the host is not known at all, or if the
certificate provided by the board doesn't match the certificate stored
in the known_hosts file).
It may give some clues to compare your local DHCP and DNS behaviour /
logs when booting Guppy, against the logs when booting Halibut... (Does
the IP of the board change ? How is done the DNS config for guppy that
make it work ?).
Hope it helps, at least a little... I must admit 'm not a DNS expert.
Johann
On 02/07/2019 12:01, Jacobo Aragunde Pérez 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
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,
_______________________________________________
automotive-discussions mailing list
automotive-discussions@xxxxxxxxxxxxxxxxxxxxxxxxx
https://lists.linuxfoundation.org/mailman/listinfo/automotive-discussions
