On 07/09/2019 11:24, Ralph Corderoy wrote:
Hi Peter,
Victor gave a method of stopping the warning, but Hamish was on the
right track of using different IP addresses.
Even though I did this that Victor suggested, it still gave me the keygen
error, so therefore perhaps I didn't do it right.
P.
Many times when I try to log-in to a Raspberry Pi via SSH I get the
following message:
...
ECDSA host key for 192.168.1.9 has changed and you have requested
strict checking.
What operating system is running your ‘ssh 192.168.1.9’? If Linux,
I expect it has support for multicast DNS and you should be able to do
‘ssh raspberrypi.local’ instead; the default hostname(1) in Raspbian
being ‘raspberrypi’ and ‘local’ being a pseudo top-level domain
reserved for mDNS: https://en.wikipedia.org/wiki/.local
You may find the first ssh or ‘ping raspberrypi.local’ doesn't work,
but it doesn't from the second on. This is just the time-out used being
shorter than the time taken by the system to get a reply to its broadcast.
For some reason the pi I tried had the name in the hosts file of 'raspberrypi-4'
and ssh seemed to connect to the pi then, but would not accept the password at
all, so this didn't work at all.
Maybe I should try 'ssh -l pi raspberrypi-4.local' ? - That worked.
I think I will follow what it says in the article and name each pi for what the
function is.
If that works, you can give each of your Raspbian installations a
different hostname that's meaningful, e.g. ‘coupe’ for your RC car
that doesn't stop.
https://bloggerbrothers.com/2017/01/08/name-your-pis-with-mdns-forget-the-ips-with-zeroconf/
has more detail. I haven't tried what I suggested, or what's in that
article, but think the theory's correct.
The avahi-daemon mentioned in the article is already running on the kubuntu
linux system.
Cheers,
Peter
--
Next meeting: BEC, Bournemouth, Tuesday, 2019-10-01 20:00
Check to whom you are replying
Meetings, mailing list, IRC, ... http://dorset.lug.org.uk/
New thread, don't hijack: mailto:dorset@mailman.lug.org.uk
