Hello:
I had three linux (one 32 bit: 192.168.1.33 the other two and 64 bit) machines on a router with dynamic dhcp. The router (Zyxel) assigns ip addresses based on mac address.It always run perfectly, slogin and ssh, both in between the three machine or outside mainframes.

Recently I gave hospitality to a Windows 2000 machine, which could reach internet and could be seen on the internal network. It gave me no major problems, except for inducing changes in the internal ip addresses according to which machine was started first.

Now the Windows 2000 machine has taken the ip address of the 32 bit linux machine, which was left with the former ip address of the Windows 2000 machine. slogin to 192.168.1.33 finds no route, while

francesco@tya64:~$ slogin 192.168.1.34
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
@ WARNING: REMOTE HOST IDENTIFICATION HAS CHANGED! @
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
IT IS POSSIBLE THAT SOMEONE IS DOING SOMETHING NASTY!
Someone could be eavesdropping on you right now (man-in-the-middle attack)!
It is also possible that the RSA host key has just been changed.
The fingerprint for the RSA key sent by the remote host is
32:67:30:c6:84:27:2c:54:ff:9d:5c:d7:61:fd:9c:95.
Please contact your system administrator.
Add correct host key in /home/francesco/.ssh/known_hosts to get rid of this message.
Offending key in /home/francesco/.ssh/known_hosts:1
RSA host key for 192.168.1.34 has changed and you have requested strict checking.
Host key verification failed.
francesco@tya64:~$

Although the modem did not allow me to change the ip address of the intruding Windows 2000 machine, I understand the message (I should think behind, because I interconnected the machines long ago). However, how to prevent the Windows 2000 machine to intrude once the network is put in order? You should assume that I can't give the Windows 2000 machine a farewell.

Thanks for help
francesco pietra

If you set dhcp reservations on your router this problem shouldn't have occurred, unless I'm misunderstanding what you are saying.

I would either set static ip addresses or use dhcp reservations, then remove the offending key from known_hosts once you are sure you're connecting to the correct machine

cheers

Remove line 1 from /home/francesco/.ssh/known_hosts and then verify that nothing nefarious has really happened (after removing it, you'll be able to ssh to it again.)

Thanks, also to previous subscriber. Removed the 1st line as you suggested from the 64bit machine which found difficulties in connecting to the 32bit machine, everything run fine among all three machines. All that in spite of a wrong situation as viewed from AdvancedSetup ... Network ....LAN ...ClientList as concerns the "ligth-on" machines

1 ligth-on 192.168.1.33 00:02:44:A8:E9E Reserve OK (deb32)

2 ligth-on 192.168.1.36 00:30:48:57O:76 Reserve NO (deb64)

3 ligth-on 192.168.1.37 00:E0:81:571:BB Reserve OK (tya64)

4 ligth-on 192.168.1.39 00:30:48:57O:76 Reserve NO (Windows 2000)



As you can see, the Win 2000 machine has the MAC address of deb64. If I detach the Win 2000 machine from the router, line 4 above disappears. Reconnecting Win 2000 to the modem, only the three linux machines are "lighth-on".

I tried unsuccessfully to modify "Reserve" from the router. Also, I found no way to either reserving dhcp or setting static ip addresses. In my hands, the ip addresses are assigned by the router. I must recall that I have dynamic dhcp. If I go to

AdvancedSetup ... Network .. LAN ... DHCP-Setup, what is sees is

that the IP pool address is to 192.168.1.33 (deb32).


If I go to AdvancedSetup ... Network .. LAN ...IP, what is seen is:

IP adress 192.168.1.1 (which is the one of the modem).

Well, probably I always had this situation.Now I am able to talk from one machine to another one. Sorry from being unable to do better.

Thanks

francesco

Moved: This thread is more suitable in Security and has been moved accordingly to help your question get the exposure it deserves.