>What this does is:
>1. Permanently disable the load balancing that was working, (with the
>same gateway on both interfaces; see my other posting on this
>thread) and
>2. Nothing else, as far as I can tell.
Well, from your post i gathered your main problem was to get the port
80 packets going to the goodisp -- not load balancing. You should probably
try to resolve that first.
>It looks like there are bugs lurking here. Here's the initial setup:
>
>route add default gw goodISPgateway goodISPdev
>route add goodISPgateway badISPdev
>route add default gw goodISPgateway badISPdev
>
Why is it the same gateway for both paths?
Try, instead:
#load balance between dev goodISPdev and device badISPdev
ip route add default via goodISPgateway nexthop dev goodISPdev nexthop dev
badISPdev
Or you can do it this way (better):
ip route add default via goodISPgateway nexthop dev goodISPdev weight 1
ip route add default via badISPgateway nexthop dev badISPdev weight 1
Or even more ambitious:
ip route add default via goodISPgateway nexthop dev goodISPdev weight 2
ip route add default via badISPgateway nexthop dev goodISPdev weight 1
ip route add default via badISPgateway nexthop dev badISPdev weight 2
ip route add default via goodISPgateway nexthop dev badISPdev weight 1
play with the weights to give routes more preference -- i believe 2
is a higher preference than 1.
#fwmark 1 always goes out on goodISPdev
ip route add table 50 0/0 via goodISPgateway dev goodISPdev
ip rule add fwmark 1 table 50
Again i havent tested this: the operator "nexthop" is key in the
multipath route.
cheers,
jamal
-
To unsubscribe from this list: send the line "unsubscribe linux-net" in
the body of a message to [EMAIL PROTECTED]
