>-----Original Message----- >From: lartc-admin@xxxxxxxxxxxxxxx [mailto:lartc-admin@xxxxxxxxxxxxxxx]On >Behalf Of bert hubert >Sent: Sunday, September 23, 2001 10:59 AM >To: lartc@xxxxxxxxxxxxxxx >Subject: Re: [LARTC] 2 gateways ou >> the most important thing is to load balence between the two cable modems >> and route all traffic out the right way if one of the cable modems goes >> down. >This depends greatly on what's on the other side of the cable modems - are >there two separate ISPs? yes. two different providers. >This situation is very difficult to resolve properly, the best way is to >experiment a bit. You will most probably need a cronscript to detect which >modems are operating. so i would ping both of my two gateways via the cronscripts and, if the current default gateway is down, and the standby is up, then change default gateway? but what if both are up? is this where policy routing steps in? would policy routing replace any pinging cronscripts? >Policy routing does this for you, and may in fact be the best solution. >Route part of your customers to one modem, and others to the other, if both >are functioning. If you detect that stuff is down, route everybody to the >other one. so policy routing dynamically routes based upon available paths on the fly? could anyone provide an example that just cuts traffic equally between the two? lets say someone was was browsing cars.com and it was 10 hops from one ISP but only 5 from the other.... can policy routing tell those packets to use the shorter path? or is this something that routing daemons are for? or is there another way to solve this puzzle? >> [root@xx /root]# cat masquerade >> #!/bin/sh >> >> modprobe ip_tables >> modprobe ip_nat_ftp >> modprobe ip_conntrack >> modprobe ip_conntrack_ftp >> modprobe iptable_nat >Having modules autoload themselves is way easier, bt. do you mean droping these commands in an init script so they always come up at boot time? or something else? thanks, Fernando Pando
