On 12 Jun 1999, Zygo Blaxell wrote:
> Uhhh...does equal cost multipath actually work in Linux 2.2.9? I've seen
> this question asked twice in this list in the last two months, but
> never answered. I'm also looking for user-space tools for setting up
> routing based on ipchains -m(ask)s.
I currently have a machine with two equal-cost routes via two interfaces:
0.0.0.0 10.1.1.1 0.0.0.0 UG 0 0 0 eth1
0.0.0.0 10.1.1.1 0.0.0.0 UG 0 0 0 eth2
It does load-share. If you test by pinging a single IP address,
everything goes out one interface... then try a second IP address, it
uses the other. The load sharing is done by selecting one of the two
equal-cost routes on an IP-by-IP basis. It's done, apparently, by address
and not by network; packets to (for example) 1.2.3.4 will use eth1,
packets to 1.2.3.5 will use eth2.
> With the (Red Hat) standard routing utilities, I have two ethernet cards
> with two default routes:
>
> 0.0.0.0 12.34.56.78 0.0.0.0 UG 0 0 0 eth1
> 0.0.0.0 23.45.67.89 0.0.0.0 UG 0 0 0 eth1
>
> I've read Documentation/networking/policy-routing.txt, fetched the
> iproute program, and have set up two default routes like this:
I didn't use iproute or anything other than the "equal cost multipath"
kernel option.
>From what I can understand of the kernel code that is conditional
> on CONFIG_ROUTE_MULTIPATH, there should be no special user-space
> requirements; if the two entries are in the same routing table then the
> route lookup should be simply compiled differently and load balancing is
> the logical result.
Correct. At least it works for me.
> From what I can understand of the iproute utilities,
> there is no kernel code at all that implements some of their options.
Dunno, I've never used them.
> What I want all this for is to work around some brain damage on the
> part of my newer (and cheaper) ISP, who blocks port 80 on outgoing TCP
> connections; they insist that I must use a proxy, while I insist that
> their proxy is slow and rarely caches anything I'm interested in anyway.
> What I'd like to do is use ipchains to mark outgoing packets for TCP
> port 80, route them through another ISP, and equally distribute all the
> other packets between the two ISP's. (Then again, if I can't easily
> do the load-balancing, I'll probably just discontinue the broken ISP's
> service...they suck in ways other than blocking port 80.)
<dons former ISP hat> Dump the boobs. If they want to force people to use
a proxy (which is questionable, since proxies are not a cure-all), and
they can't figure out how to do a transparent proxy, they're incompetent.
Or just fascist. But that's just my opinion, of course. In most cases,
you gets what you pays for, and ISPs are no exception.
---
The most exciting phrase to hear in science, the one that heralds new
discoveries, is not "Eureka!" (I found it!) but "That's funny ..."
-- Isaac Asimov
-
To unsubscribe from this list: send the line "unsubscribe linux-net" in
the body of a message to [EMAIL PROTECTED]
