Hi there,
I currently have a multi-ISP config and it's working great. Host is a
CentOS5.4 machine. Shorewall 4.4.19.1
I've been asked to add a new ISP which has a 1GB download limit during
certain hours. When the cap is hit my users want to switch traffic to
another, shared ISP.
I was planning on just issuing some iptables commands to tag the traffic
for ISP#1 during the on time and ISP#2 during the off time, the same way an
entry in tcrules would.
The question is really how does connection tracking enter this mix and how
can it be avoided?
Can I turn off connection tracking where the source is 192.168.0.0/24 and
the destination is !RFC1918 but still have tracking where the source is
192.168.0.0/24 and the destination is RFC1918? Presumably I'd have to add
an entry in the notrack file for each ISP interface like. Assuming ISP1 on
eth1.9 and ISP2 on eth1.5:
eth1.7:192.168.0.0/24 eth1.9:!(10.0.0.0/8,192.168 ... etc...)
eth1.7:192.168.0.0/24 eth1.5:!(10.0.0.0/8,192.168 ... etc...)
Any suggestions are most welcome,
Lee Brown
------------------------------------------------------------------------------
All the data continuously generated in your IT infrastructure
contains a definitive record of customers, application performance,
security threats, fraudulent activity, and more. Splunk takes this
data and makes sense of it. IT sense. And common sense.
http://p.sf.net/sfu/splunk-novd2d
_______________________________________________
Shorewall-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/shorewall-users
