On 3/31/2014 1:07 PM, Tom Eastep wrote: > On 3/31/2014 10:48 AM, İlker Aktuna wrote: >> >> >> -----Original Message----- >> From: Tom Eastep [mailto:[email protected]] >> Sent: Monday, March 31, 2014 1:18 AM >> To: [email protected] >> Subject: Re: [Shorewall-users] multi ISP - port based routing >> >> On 3/30/2014 2:16 PM, İlker Aktuna wrote: >>> >>>> >>>> Btw, my Shorewall configuration works by tracling the pakets on both >>>> ISP connections. So if a connection is made through ppp1, all packets >>>> of the same session go through that interface. Why doesn't this work >>>> for packets incoming to that interface ? >>>> >>> >>>> It does work that way. >>> >>> What do you mean ? >> >>> For a provider with the 'track' option (either explicitly specified or via >>> TRACK_PROVIDERS=Yes in shorewall.conf), then connections initiated from the >>> net through that provider, then outgoing packets for that connection are >>> sent through the provider's interface. >> >> But for this example, it doesn't work. What am I missing ? >> (sorry but I really don't understand) > > If you have changed your configuration since you sent me the last dump, > please send another one.
And please collect the dump using 'bash /sbin/shorewall dump' so that I can see the contents of the routing tables. The version of 'dash' on your system broke Shorewall's reporting of the routing table contents' (a workaround was addded to Shorewall in version 4.5.2.3). -Tom -- Tom Eastep \ When I die, I want to go like my Grandfather who Shoreline, \ died peacefully in his sleep. Not screaming like Washington, USA \ all of the passengers in his car http://shorewall.net \________________________________________________
signature.asc
Description: OpenPGP digital signature
------------------------------------------------------------------------------
_______________________________________________ Shorewall-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/shorewall-users
