Nat can be disabled again for testing purpose. I m not sure to understand why
you think it should work: client send packet to 10.13.70.138 and receive
response from 192.168.195.227. How is that supposed to work?
Le 27 juillet 2017 22:01:30 GMT+02:00, Tom Eastep <[email protected]> a
écrit :
>On 07/27/2017 12:57 PM, Adam Cecile wrote:
>> Eth1 will be killed. It has been added to provide an access through
>the
>> old address logging every client so they can be fixed to use the
>proper
>> address.
>>
>> No it was not. 10.13.70.138 <http://10.13.70.138> was reachable from
>any
>> network EXCEPT 192.168.195.0/24. <http://192.168.195.0/24.>
>>
>
>Then I don't understand why it wasn't reachable from 192.168.195.0/24,
>and with the NAT in place on the central firewall, we will probably
>never know. But once eth1 is removed, clearly traffic to
>192.168.195.0/24 WILL be routed out of eth0.
>
>-Tom
>--
>Tom Eastep \ Q: What do you get when you cross a mobster with
>Shoreline, \ an international standard?
>Washington, USA \ A: Someone who makes you an offer you can't
>http://shorewall.org \ understand
> \_______________________________________________
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Shorewall-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/shorewall-users
