On 2/15/11 9:31 AM, Zaar Hai wrote: > My shorewall box is connected to two internet providers (isp0, isp1) > and local lan (br0). >
It is always helpful to know which *version* of Shorewall is being used. I have two kind of machines on br0 - server machines (with several > known IP addresses, say ip1, ip2, ip3) and many dhcp workstations. > > I want to setup these policies: > 1). workstations should use isp0 ONLY (if its online and use isp1 othewise). > 2). servers should prefer isp1, but can use isp0 IF its has free > bandwidth not occupied by workstations. A Shorewall-generated configuration has no capability to make routing decisions based on bandwidth availability. > > So far i have this configuration: > > $ cat /etc/shorewall/interfaces > #ZONE INTERFACE BROADCAST OPTIONS > net ppp0 detect > dhcp,tcpflags,nosmurfs,routefilter,logmartians,optional > net ppp1 detect > dhcp,tcpflags,nosmurfs,routefilter,logmartians,optional > loc br0 detect > tcpflags,nosmurfs,routefilter,logmartians,bridge > > $ cat /etc/shorewall/providers > #NAME NUMBER MARK DUPLICATE INTERFACE GATEWAY > OPTIONS COPY > isp0 1 1 main ppp0 - > track,balance br0 > isp1 2 2 main ppp1 - > track,balance br0 > > With this configuration all traffic from br0 is load-balanced between > two providers. > No I want to make certain hosts to prefer certain provider as I've > described above. > > Setting something like (br0!ip1!ip2!ip3) - i.e. "all that comes from > br0 except of servers ips" as SOURCE fields in route_rules would help > me with 1), but it seems that such complicated source address > specifications are not supported. ip1 - isp1 ip2 - isp1 ip3 - isp1 br0 - isp0 -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
------------------------------------------------------------------------------ The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE: Pinpoint memory and threading errors before they happen. Find and fix more than 250 security defects in the development cycle. Locate bottlenecks in serial and parallel code that limit performance. http://p.sf.net/sfu/intel-dev2devfeb
_______________________________________________ Shorewall-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/shorewall-users
