On 07/27/2017 12:38 PM, Adam Cecile wrote: > No NAT anywhere (actually there s one in the central firewall to make > packet coming from 192.168.195 to 10.13 looking like coming from 10.13 > so shorewall machine answer back through eth0, but thats a workaround > because I couldn't get PBR doing what I want). >
So when 192.168.195.227 "goes away", what will the configuration of eth1 look like? And, before the NAT was added on the central firewall, did connections from 192.168.195.0/24 to 10.13.70.138 work, even though the routing was assymetric? -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 \_______________________________________________
signature.asc
Description: OpenPGP digital signature
------------------------------------------------------------------------------ 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
