On Sat, Sep 22, 2001 at 05:45:50PM -0400, Largo Hellenz wrote: > hi, > > first, i'd like to say im so happy this list is finally back up!!!! I'm happy too :-) > those two connect to a central 2.4.2 machine with 5 nics. > box C (eth0 10.0.0.1/24, eth1 10.1.1.2/24, eth2 10.2.2.2/24, eth3 > 10.3.3.1/24, eth4 10.4.4.1/24) Very impressive. > 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? 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. > if possible, possibly even send some packets out one way and some out > aNother (based on payload content and packet tagging?) but this is for my > next lesson :) 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. > [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. > echo 1 > /proc/sys/net/ipv4/ip_forward > > /sbin/iptables -F I would advise to change the path, so you can leave out the redundant /sbin on every line. Regards, bert -- http://www.PowerDNS.com Versatile DNS Software & Services Trilab The Technology People Netherlabs BV / Rent-a-Nerd.nl - Nerd Available - 'SYN! .. SYN|ACK! .. ACK!' - the mating call of the internet
