Hello,
We're changing offices and I need to set up two servers connected over a VPN.
One server has a public IP, "1.2.3.4"
The other server runs a service @ internal IP address "10.0.0.2:1234"
I want to give access @ 1.2.3.4:1234 and transparently 'tunnel' (don't know if
that's the right word)
On Tue, Sep 29, 2020 at 08:54:42PM +, JadoNena via Shorewall-users wrote:
> Hello,
>
> We're changing offices and I need to set up two servers connected over a VPN.
>
> One server has a public IP, "1.2.3.4"
>
> The other server runs a service @ internal IP address "10.0.0.2:1234"
>
> I want
> You need DNAT, as described here:
>
> https://shorewall.org/two-interface.htm#DNAT
Ok. That is what I started with.
There is no advice or example there for how to get that traffic through the VPN
to the back end server.
Can you help with the rules?
My test for this working is to
telnet -4
On Tue, Sep 29, 2020 at 09:51:45PM +, JadoNena via Shorewall-users wrote:
> > You need DNAT, as described here:
> >
> > https://shorewall.org/two-interface.htm#DNAT
>
>
> Ok. That is what I started with.
>
> There is no advice or example there for how to get that traffic through the
> VPN t
> > telnet: connect to address 1.2.3.4: Connection refused
>
> You are not providing sufficient information to be able to conclusively
> identify the problem. However, it seems like you either do not have IP
> forwarding enabled on the Shorewall machine (seems unlikely) or there is
> a missing rout
