Re: Route from LAN to Hercules

On Sun, 19 Jan 2020 09:57:03 -0600
"Harold Grovesteen [email protected] [hercules-390]"
<[email protected]> wrote:

> Typically this problem is a missing route from the LAN device to the
> Hercules guest IP address via the Hercules host IP address.
> 
> This is not a server problem but a device problem.  Packets require
> routes on both ends of the connection to make it.  In  this case the
> IP addresses involved are the Hercules guest (not the host) and LAN
> device with the telnet client.
> 
> There are numerous variations on this theme, but it boils down to the
> same issue: getting the IP packets from the LAN devise to the Hercules
> guest.
> 
> Harold Grovesteen
Harold-
Thanks for replying, I seem to remember you helping me out before. :)
The thing is I have a route from the LAN device to the Hercules guest, I
issued:

route add 192.168.100.12 gw 192.168.100.2

and I can ping and traceroute the Hercules guest from the LAN. Are you
saying I need a route from the guest back to the LAN device?

And no, this is me messing around at home, not the day job!

Thanks
Robin