In article <[EMAIL PROTECTED]>, Andi Kleen <[EMAIL PROTECTED]> wrote:
>In article <7jtjfs$jsr$[EMAIL PROTECTED]>,
>[EMAIL PROTECTED] (Zygo Blaxell) writes:
>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.
teql does seem to work (although it's hard to tell without rearranging
the hardware, as all the teql0 traffic is hidden from a tcpdump of the
slave devices, and tcpdump can't handle teql0 itself). The LEDs on
both ISP's boxes are flashing in tandem now, so until I get another
machine in there to tcpdump the net I'll assume it works for now. ;-)
>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 have two ISP's: one that is broken (they provide only dynamic IP,
packet filtering, high latency, and flaky CPE hardware) and one that
I have to pay for (static IP, no filtering, low latency, and equally
flaky CPE hardware). Neither filters by source address, so I can set
up either as my default route and everything works (except that one ISP
filters packets with destination TCP port 80). The three problems I'd like
to solve are sending on both interfaces at the same time (teql0 does that),
receivng on both interfaces at the same time (see below) and routing
packets destined for port 80 differently than packets destined for other
ports (possibly using ipchains '-m' and routing tables keyed by the mark
on the packet, although I haven't an example of this working yet).
It occurs to me that what I really want for balanced receiving is to
get IP masquerading working with equally selected source interfaces.
This is orthogonal to whether the individual packets are routed on
many or only one interface. Since the IP's are different and neither
ISP knows about routing to the other, the reply packets for outgoing
connections will always be received on the one interface that matches the
IP address the outgoing connection was made from. It would be useful if
the masquerade code could send each entire masqueraded connection through
each available ISP that could handle the connection. Of course because
of the port 80 filtering, the list of suitable ISP's is changes depending
on destination, and would probably have to be controlled by ipchains marks.
--
Zygo Blaxell, Linux Engineer, Corel Corporation. [EMAIL PROTECTED] (work) or
[EMAIL PROTECTED] (play). Opinions above are my own, not Corel's.
Linux naga 2.0.36 #1 Dec 29 13:11 EST 1998 up 11 days, 23:44
Linux mokona 2.2.9 #1 Jun 12 02:07 EDT 1999 i586 up 12:05
-
To unsubscribe from this list: send the line "unsubscribe linux-net" in
the body of a message to [EMAIL PROTECTED]
