In article <7jtjfs$jsr$[EMAIL PROTECTED]>,
[EMAIL PROTECTED] (Zygo Blaxell) writes:
> 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.
> 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:
> default via 12.34.45.67 dev eth1 equalize # I've done with and
> default via 23.45.67.89 dev eth2 equalize # without "equalize"
> In either case, all the ethernet traffic goes out one of the two network
> cards. The only difference I can see between the two alternatives is
> _which_ one all the outgoing traffic goes through.
The multipath equal cost routing does not do real load
balancing ATM. RTCF_EQUALIZE is not implemented. The -ac kernels contain a
small hack to make it work, but it still does not do very well.
One Alternative is the teql queueing discipline which works on L2.
Of course both will only work if you're truly multihomed, otherwise
you need a user space proxy that knows about TCP flows (NAT only works for
a single connection because others don't like TCP flows that come from two
different addresses)
> I'm not quite sure how the 2.2.x routing tables and rules fit into this,
> if they fit in at all.
See ip-cref.tex in a recent iproute2 snapshot.
-Andi
-
To unsubscribe from this list: send the line "unsubscribe linux-net" in
the body of a message to [EMAIL PROTECTED]
