Loadbalancing on multiple eth rtl8139
Daniel Bergqvist [email protected]
<PRE>><i> Från: <A HREF="mailto:[email protected]">[email protected]</A> </I>><i> [mailto:<A HREF="mailto:[email protected]">[email protected]</A>]För bert hubert </I>><i>
</I>><i> On Mon, Oct 16, 2000 at 03:25:37PM +0200, Daniel Bergqvist wrote:
</I>><i>
</I>><i> > This is basicly what I'm trying to do, but inside the sch_teql
</I>><i> driver. What
</I>><i> > is the problems with tunnels?
</I>><i>
</I>><i> If your link saturates and you get packetloss, you get very weird
</I>><i> performance problems. Also, one lost packet stops *all* your IP traffic </I>><i> until it's resent.
</I>
My idea is to have to devices, teql_send0 and teql_receive0. The teql_send0
is the old teql0 device, but it also adds a serial number and a new IP
header so the packet goes to the teql_receive0 device at the remote end. I
know that the packets will be sent in order on each ethernet link to theteql_receive0 device so it keeps a queue for each connection. If there is no
packet loss only one queue that will have packets. If both queues have a
packet it means we have a packet loss. The teql_receive0 device then sends
the packets in the original order.
><i>
</I>><i> > Where is the archive for <A HREF="mailto:[email protected]">[email protected]</A>? </I>><i>
</I>><i> It appears to have died. I'll forward you the right messages.
</I>
I got it. Thanks!
><i> Regards,
</I>><i>
</I>><i> bert hubert
</I>
Regards,
Daniel
</PRE>