Skip to contentSkip to conversation

TEQL: 2 Mbit eth1 + 2Mbit eth2 = 1Mbit teql0]

[email protected]: SV: Daniel Bergqvist [email protected] 2 participants 3 messages Oct 10, 2000 – Oct 11, 2000

lore
Share & tools
lore

Daniel Bergqvist [email protected]

author
#0 lore raw

<PRE>The logs are at <A HREF="http://www.bergqvist.se/teql/.">http://www.bergqvist.se/teql/.</A>

The speed is about 1.3Mbit/s.

Thanks,
Daniel

&gt;<i> -----Ursprungligt meddelande-----
</I>&gt;<i> Från: <A HREF="mailto:[email protected]">[email protected]</A> </I>&gt;<i> [mailto:<A HREF="mailto:[email protected]">[email protected]</A>]För bert hubert </I>&gt;<i>
</I>&gt;<i> Ok, then we need to go all out. Try this: tcpdump -i teql0 -w for.ahu, and </I>&gt;<i> run it while ftp-ing a file over teql0, end put this file online.
</I>&gt;<i> Take care
</I>&gt;<i> that there is no confidential data in the file you are ftp-ing.
</I>&gt;<i>
</I>&gt;<i> If possible, try dumping eth0 and eth1 as well, simultaneously.
</I>&gt;<i>
</I>&gt;<i> I'll take a look at the dump and see if anything is wrong.
</I>&gt;<i>
</I>&gt;<i> Regards,
</I>&gt;<i>
</I>&gt;<i> bert hubert
</I>

</PRE>

#1 lore raw

<PRE>On Tue, Oct 10, 2000 at 04:21:06PM +0200, Daniel Bergqvist wrote:
&gt;<i> The logs are at <A HREF="http://www.bergqvist.se/teql/.">http://www.bergqvist.se/teql/.</A> </I>&gt;<i>
</I>&gt;<i> The speed is about 1.3Mbit/s.
</I>
There is lots of packetloss. Also, it is obvious from this dump that
lan_router is sending both over eth1 and eth2, but that the wan router is
only receiving on eth2, and not on eth1, or that your dump failed.

    lan_router_eth1         10-Oct-2000 16:16    73k  
    lan_router_eth2         10-Oct-2000 16:16    73k  
    lan_router_teql0        10-Oct-2000 16:16    42k  
    wan_router_eth1         10-Oct-2000 16:15     1k
    wan_router_eth2         10-Oct-2000 16:15    46k
    wan_router_teql0        10-Oct-2000 16:15   146k

lan_router_eth[12] carry ftp data, teql0 carries acknowledgements, and lots of them are duplicate or triplicate, indicating packetloss and resends.

wan_router_eth1 receives almost nothing, while wan_router_eth2 is sees the same the ACKs seen by teql0 on the lan_router, also duplicate.

wan_router_teql0 sees packets also seen by lan_router_eth1 and eth2, and they are alternatingly from eth1 and eth2, which is as it should be.

10.2.18.2 is telling ftp2.citynet.nu that is is missing packets, so it appears that data is getting lost on the other way. I'm not sure if this is related to TEQL.

I'm interested in knowing what you make of the nearly empty wan_router_eth1 file.

Regards,

bert hubert

Signature · 6 lines
PowerDNS                     Versatile DNS Services  
Trilab                       The Technology People   
'SYN! .. SYN|ACK! .. ACK!' - the mating call of the internet


</PRE>
#2 lore raw
In reply to Daniel Bergqvist [email protected]

<PRE>On Tue, Oct 10, 2000 at 06:03:44PM +0200, bert hubert wrote:
&gt;<i> On Tue, Oct 10, 2000 at 04:21:06PM +0200, Daniel Bergqvist wrote:
</I>&gt;<i> &gt; The logs are at <A HREF="http://www.bergqvist.se/teql/.">http://www.bergqvist.se/teql/.</A> </I>&gt;<i> &gt;
</I>&gt;<i> &gt; The speed is about 1.3Mbit/s.
</I>&gt;<i>
</I>&gt;<i> There is lots of packetloss. Also, it is obvious from this dump that </I>&gt;<i> lan_router is sending both over eth1 and eth2, but that the wan router is </I>&gt;<i> only receiving on eth2, and not on eth1, or that your dump failed.
</I>

On second thought, there is no packet loss. This is expected behaviour, it
appears, see <A HREF="http://www.kernelnotes.de/kt/latest.html:">http://www.kernelnotes.de/kt/latest.html:</A>

Alexey Kuznetsov was critical of this explanation, and said that multipath routing worked &quot;perfectly when you need to split load on servers talking to enough large number of clients. Any
http server is good example.&quot; He added that Andi's suggestion of the
existing eql, teql and bonding devices, would introcude &quot;even worse problem of strong tcp reordering. Actually,
experiments show that load balancing works only in the situations, when
congestion window is bounded by 3 packets. If it is not made artificially, it occurs automatically on each connection
after some amount of excessive retransmissions. Total single TCP
connection throughput is never better in this case. Actually, it hints to the thought that &quot;true load blalancing&quot; has to

     involve tracking connections and avoiding reordering TCP packets.&quot;

There was no reply to this, but there was a bit of implementation discussion elsewhere, along the lines of Andi's
explanations.

----

You might consider using google a bit to find out about packet reordering - packets arrive out of sequence on eth1 and eth2, which the kernel interprets as packetloss.

Regards,

bert hubert

Signature · 6 lines
PowerDNS                     Versatile DNS Services  
Trilab                       The Technology People   
'SYN! .. SYN|ACK! .. ACK!' - the mating call of the internet


</PRE>