Overall everything works nearly perfectly. Incomming connections to either the fios (PPPoE) connection, or cable modem get routed back out correctly. The problem I'm having is with the default gateway.
${IP} route add default table 221 proto static \
nexthop via ${EXTGW2} dev ${EXTIF2} weight 1\
nexthop via ${EXTGW1} dev ${EXTIF1} weight 5
With this command, connections going out from my network always seem to use the GW1 route. I if I reverse the order of the nexthop's to list GW1 first and GW2 second, then the reverse happens and all outgoign connections use GW2. I'm going to attempt to test this better by attempting a large number of connections to a large list of ip's, but in running this setup I've never seen it use both gateway's.
Possible symptom I've noticed is that in the route cache, there tends to be 2 entries, with the used gateway showing up first, such as:
83.53.46.36 from 192.168.0.128 via 10.9.44.15 dev ppp0 src 192.168.0.1
cache <src-direct> mtu 1492 advmss 1452 metric10 64 iif eth0
83.53.46.36 from 192.168.0.128 via 66.189.76.1 dev eth1 src 192.168.0.1
cache <src-direct> mtu 1500 advmss 1460 metric10 64 iif eth0
In this case, ppp0 was listed as the second nexthop. If I reversed the order of the nexthop's, then the order they show up in the cache reverses. Does anyone have any ideas why both gateways don't seem to be used? Please let me know if any other information about my setup would be useful. I've been experimenting with various other options like turning off rp_filter for both connections, adjusting weight's, performing the connections from various internal ip's to various external ip's to insure new route lookups, etc. I've just never ever seen it use anything but the last specified nexthop which has lead me to fear it's a problem with the patches and/or my kernel.
Thanks,
Jody
_______________________________________________ LARTC mailing list LARTC@xxxxxxxxxxxxxxx http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc
