wouldn't you just ssh using a lan ip?
i don't like using letters, so i'll explain with numbers:
machine a (192.168.0.2) ------+\
> (192.168.0.1) - gateway - (24.xx.xxx.xx)
machine b (192.168.0.3) ------+/
ssh into (a) from the internet using ssh -p 22 24.xx.xxx.xx
ssh into (b) from the internet using ssh -p 2222 24.xx.xxx.xx
and ssh into (b) from (a) using ssh -p 2222 192.168.0.3
why bother routing your traffic out onto the internet if you don't have to?
On November 6, 2002 04:50 pm, christopher j bottaro wrote:
> ok,
> i got computer A running sshd listening for connections on port a, i got
> computer B running sshd listening for connections on port b. both are
> behind a hardware firewall that forwards stuff on port a to computer A and
> stuff on port b to computer B. the hardware firewall is also my gateway.
> lets call my ip address X.
>
> now the problem is sshing from a single machine to both computers A and B.
> consider sshing to computer A:
> ssh -p a X
> yes to creating a key in known_hosts for ip address X
> now if i issue the following command to get into computer B:
> ssh -p b X
> ssh bombs out with a failure message about the RSA host key has changed.
> obviously cuz computers A and B are different machines, but known_hosts has
> one key entry for both of them (cuz they share the same ip address).
>
> what can i do about this? i don't like having to delete stuff outta
> known_hosts every time i wanna ssh into a different one of my home
> computers.
>
> thanks,
> christopher
--
redhat-list mailing list
unsubscribe mailto:redhat-list-request@;redhat.com?subject=unsubscribe
https://listman.redhat.com/mailman/listinfo/redhat-list
