On 02/16/2016 02:23 PM, Steve Wray wrote: > Hi, > I have an existing, working example of policy routing and I'd like to > see if its possible to implement this in Shorewall. > > ip rule ls shows: > > 0: from all lookup local > 0: from xxx.xxx.xxx.121 lookup eth2 > 0: from all to xxx.xxx.xxx.121 lookup eth2 > 0: from xxx.xxx.xxx.122 lookup eth2 > 0: from all to xxx.xxx.xxx.122 lookup eth2 > 1: from all fwmark 0x200/0x200 lookup TProxy > 999: from all lookup main > 32765: from all lookup balance > 32767: from all lookup default > > I've been reading the Shorewall documentation on providers, rtrules etc > and can't see how this fits together. >
Not enough information to be able to tell you with any certainty. 1. Are xxx.xxx.xxx.121 and/or xxx.xxx.xxx.122 local addresses assigned to eth2? If not, what are they? 2. What are the contents of the eth2 routing table? 3. I assume that your current providers file only has the TPROXY provider? -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
------------------------------------------------------------------------------ Site24x7 APM Insight: Get Deep Visibility into Application Performance APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month Monitor end-to-end web transactions and take corrective actions now Troubleshoot faster and improve end-user experience. Signup Now! http://pubads.g.doubleclick.net/gampad/clk?id=272487151&iu=/4140
_______________________________________________ Shorewall-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/shorewall-users
