Re: Route from LAN to Hercules

On Sun, 19 Jan 2020 23:39:11 +0700
"Robin Atwood [email protected] [hercules-390]"
<[email protected]> wrote:

> 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.

OK, I found the problem. There was a pre-routing rule in iptables on the server that
I hadn't noticed that needed to be updated to the current IP addresses. It
now is:

 # iptables -t nat -L -n
Chain PREROUTING (policy ACCEPT)
target     prot opt source               destination         
DNAT       tcp  --  0.0.0.0/0            0.0.0.0/0            tcp dpt:23 to:192.168.100.12

and the telnet sessions suddenly came up. :)

Thanks to everyone who tried to help
Robin