On 07/27/2017 08:51 PM, Tom Eastep wrote:
On 07/27/2017 10:12 AM, Adam Cécile wrote:
On 07/27/2017 06:39 PM, Tom Eastep wrote:
From the routing rules you posted above, the 'main' table is traversed
before BPR is used, and the 'main' table will route packets to
192.168.195.0 out of eth1.
Sounds like the root of the issue to me !
But do you really think that it is a problem?
-Tom
Yes because any machine from 192.168.195.0/24 network cannot use the new
10.13 address, and that the one that will stay, 192.168.195.227 must go
asap.
------------------------------------------------------------------------------
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
Shorewall-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/shorewall-users
