On 7/20/12 5:08 AM, Roland dnaloR wrote:
> Thanks for the reply.
> 
> Given your advice, i fixed the logs part and edited my tcrules:
> 
> 1 192.168.70.0/24 0.0.0.0/0
> 2 192.168.70.0/24 4.2.2.2
> 
> 
> With that, 4.2.2.2 always routes through the second ISP correctly.
> though some things match the first rule and others don't and still go 
> through the second unless is specifically add them by IP to go through 
> the first..
> 

Then why don't you change the first rule to

1       0.0.0.0/0       0.0.0.0/0

-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 \________________________________________________

Attachment: signature.asc
Description: OpenPGP digital signature

------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
Shorewall-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/shorewall-users

Reply via email to