Re: Only using masquerading on internet facing server

2019-03-14 Thread john doe
On 3/14/2019 1:58 PM, Stefan Monnier wrote: >> Does it help understanding what I'm trying to do? > > It just confirms what I guessed. Did you try my suggestion? > Thanks to Your answer and the one by "Dan Purgert " I now have the bit I was missing; add routing on server a to let server a know abo

Re: Only using masquerading on internet facing server

2019-03-14 Thread rhkramer
On Thursday, March 14, 2019 04:26:06 AM john doe wrote: > By the answers in this thread, I guess I need to explane what I have and > what I'm trying to do. As someone observing from the peanut gallery, it would help me if the explanation was a little less detailed -- sort of an overview. Let me

Re: Only using masquerading on internet facing server

2019-03-14 Thread Stefan Monnier
> Does it help understanding what I'm trying to do? It just confirms what I guessed. Did you try my suggestion? Stefan

Re: Only using masquerading on internet facing server

2019-03-14 Thread Dan Purgert
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Joe wrote: > On Thu, 14 Mar 2019 09:26:06 +0100 > john doe wrote: >> [...] >> By the answers in this thread, I guess I need to explane what I have >> and what I'm trying to do. >> >> [...] >> >> For now both server (a and b) are responsible for MA

Re: Only using masquerading on internet facing server

2019-03-14 Thread Joe
On Thu, 14 Mar 2019 09:26:06 +0100 john doe wrote: > On 3/13/2019 1:39 PM, Stefan Monnier wrote: > >> Ip range on server a: 172.17.232.0/24 > >> IP range on server b: 192.168.3.0/24 > > > > That's very vague. > > But I'll assume that your "server b" has an address 172.17.232.NN > > on one netwo

Re: Only using masquerading on internet facing server

2019-03-14 Thread mick crane
On 2019-03-14 08:26, john doe wrote: On 3/13/2019 1:39 PM, Stefan Monnier wrote: Ip range on server a: 172.17.232.0/24 IP range on server b: 192.168.3.0/24 That's very vague. But I'll assume that your "server b" has an address 172.17.232.NN on one network interface and 192.168.3.1 on another.

Re: Only using masquerading on internet facing server

2019-03-14 Thread john doe
On 3/13/2019 1:39 PM, Stefan Monnier wrote: >> Ip range on server a: 172.17.232.0/24 >> IP range on server b: 192.168.3.0/24 > > That's very vague. > But I'll assume that your "server b" has an address 172.17.232.NN > on one network interface and 192.168.3.1 on another. > >> If I enable MASQUERADIN

Re: Only using masquerading on internet facing server

2019-03-13 Thread Stefan Monnier
> Ip range on server a: 172.17.232.0/24 > IP range on server b: 192.168.3.0/24 That's very vague. But I'll assume that your "server b" has an address 172.17.232.NN on one network interface and 192.168.3.1 on another. > If I enable MASQUERADING on server b everything works as expected but as > soo

Only using masquerading on internet facing server

2019-03-13 Thread john doe
Hi, I have one internet facing server that is doing masquerading (server a). Behind that server I have an other server (server b). Server a is the only one server that should do NAT . Ip range on server a: 172.17.232.0/24 IP range on server b: 192.168.3.0/24 I have configured server a to MASQUE