search for: outside_device

...Linux from the LAN ( pinging from the Linux itself is OK ). But pinging beyond the two external interfaces ( eg the default route ) is OK. I use symbolic names here :- # ip route add ${INSIDE_NETWORK} dev ${INSIDE_DEV} table first ip route add ${OUTSIDE_NETWORK} dev ${OUTSIDE_DEVICE} table first ip route add ${OUTSIDE_NETWORK2} dev ${OUTSIDE_DEVICE2} table first ip route add 127.0.0.0/8 dev lo table first # ip route add ${INSIDE_NETWORK} dev ${INSIDE_DEV} table second ip route add ${OUTSIDE_NETWORK} dev ${OUTSIDE_DEVICE} ta...

The LARTC howto correctly describes load balancing and split access for traffic from a machine with multiple ISP connections (http://www.lartc.org/lartc.html#LARTC.RPDB.MULTIPLE-LINKS) -- *provided* the traffic originates from the machine itself (i.e. traffic regularly handled by the INPUT and OUTPUT chains of iptables). When forwarding traffic from an attached local network, the following

I am working on a split route and ShoreWall system. I reviewed the lartc documentation but have a few areas that I still need help on. Here is my network: 64.xxx.xxx.1/25 66.xxx.xxx.129/26 | | ################################################# # Eth2 64.xxx.xxx.2 eth0 66.xxx.xxx.130 # #