ssh concepts for IP-adresses; dialin to several LANs

I'm administrating about 12 LANs of customers (in future
about 50). I dial in by telephone line (ISDN) and login
with ssh. I programmed the dialin interface with dynamical
IP adresses. I get another IP with each customer (e.g.
192.168.10.200, .201, .202, ...). I programmed another
IP for each LAN because otherwise ssh claims:

4857: @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@ @@@@@@@@@
4857: @ WARNING: REMOTE HOST IDENTIFICATION HAS CHANGED! @
4857: @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@ @@@@@@@@@
4857: IT IS POSSIBLE THAT SOMEONE IS DOING SOMETHING NASTY!
4857: Someone could be eavesdropping on you right now (man-in-the-middle attack)!
4857: It is also possible that the RSA host key has just been changed.
4857: The fingerprint for the RSA key sent by the remote host is
c5:a6:64:5a:bb:3c:1e:5f:fd:5f:ea:db:2b:6e:37:16.
4857: Please contact your system administrator.
4857: Add correct host key in /home/gerlach/.ssh/known_hosts to get rid of this message.
4857: Offending key in /home/gerlach/.ssh/known_hosts:30
4857: RSA host key for 192.168.10.99 has changed and you have requested strict checking.
4857: Host key verification failed.

Are there some concepts that allow the *same* IP with each LAN?

tia
Ekkard

On 2004-09-03, Ekkard Gerlach <(E-Mail Removed)> wrote:
> I'm administrating about 12 LANs of customers (in future
> about 50). I dial in by telephone line (ISDN) and login
> with ssh. I programmed the dialin interface with dynamical
> IP adresses. I get another IP with each customer (e.g.
> 192.168.10.200, .201, .202, ...). I programmed another
> IP for each LAN because otherwise ssh claims:
>
> 4857: @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@ @@@@@@@@@
> 4857: @ WARNING: REMOTE HOST IDENTIFICATION HAS CHANGED! @
> 4857: @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@ @@@@@@@@@
> [snipped]
>
> Are there some concepts that allow the *same* IP with each LAN?
>
Unfortunately not, a others will notice there is no 'support' for different
SSH deamons running on different ports, and those ports are port forwarded to
other hosts.

All I can suggest is you use the 'IgnoreUserKnownHosts yes' in your
ssh_config file.

This should be perfectly safe (if you check your fingerprints). You might
find your self better off (I have not tried this though) if you fill your
/etc/hosts with entries and then use a 'hostname' to connect to the machine,
this hopefully will work, I could be wrong though.

Cheers

Alex