Skip to contentSkip to conversation

Loadbalancing on multiple eth rtl8139

LARTC Daniel Bergqvist [email protected] 3 participants 4 messages Oct 16, 2000 – Oct 17, 2000

lore
Share & tools
lore

Daniel Bergqvist [email protected]

author
#0 lore raw

<PRE>Hi!

The devices eth1 and eth3 MUST be active. Remove &quot;ip link set down eth1&quot; and &quot;ip link set down eth3&quot;. You might get problems with &quot;TCP packet reordering&quot; resulting in lower bandwidth but I'm currently working with a patch to the sch_teql driver. I will post it to the list if/when I get it to work.

Regards,
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 </I>&gt;<i> <A HREF="mailto:[email protected]">[email protected]</A> </I>&gt;<i> Skickat: Monday, October 16, 2000 12:03 PM
</I>&gt;<i> Till: <A HREF="mailto:[email protected]">[email protected]</A>
</I>&gt;<i> Ämne: [LARTC] Loadbalancing on multiple eth rtl8139
</I>&gt;<i>
</I>&gt;<i>
</I>&gt;<i> Hello!
</I>&gt;<i>
</I>&gt;<i> I have a 4 interfaces Linux router with 2.2.14 kernel realtec
</I>&gt;<i> 10/100 rtl8139 driver. The kernel should be compiled with the
</I>&gt;<i> right options.
</I>&gt;<i> I have to loadbalance the traffic on two interfaces. We speak
</I>&gt;<i> about microwave connection, but the microwave devices are
</I>&gt;<i> breezenet access points so they can not be included into the
</I>&gt;<i> router machine directly, they are attached by ethernet T based 10
</I>&gt;<i> Mbs cord one to one eth card respectively. The line have to have
</I>&gt;<i> the double of the 3MB of today`s capacity.
</I>&gt;<i> The other side of the line is a cisco 7000 series router of our
</I>&gt;<i> provider. We would like to use one virtual interface and two
</I>&gt;<i> slaved ones attached to the virtual master to route statically
</I>&gt;<i> the traffic. We tried the sch_teql module to do so and the Linux
</I>&gt;<i> 2.4 Advanced Routing HOWTO chapter 8.5 Loadsharing over multiple
</I>&gt;<i> interfaces. We exactly entered this lines in shell:
</I>&gt;<i> modprobe sch_teql
</I>&gt;<i> ip link set down eth1
</I>&gt;<i> ip link set down eth3
</I>&gt;<i> tc qdisc add dev eth1 root teql0
</I>&gt;<i> tc qdisc add dev eth3 root teql0
</I>&gt;<i> ip addr add dev teql0 62.168.113.130/25
</I>&gt;<i> (the interfaces eth1 and eth3 are already set up with
</I>&gt;<i> 62.168.113.254 resp. 62.168.113.253)
</I>&gt;<i> The system was unable to ping the other side. After we tried to
</I>&gt;<i> link up the interfaces - teql0 before, eth1 and eth3 after. Ping
</I>&gt;<i> with all the interfaces bringed up (ip link set up dev [device])
</I>&gt;<i> resulted in system crash. We was told by third party that the
</I>&gt;<i> realtec eth card has a mallfunctioning driver for some operation.
</I>&gt;<i>
</I>&gt;<i> Please let us know how to do.
</I>&gt;<i>
</I>&gt;<i> Thanks
</I>&gt;<i>
</I>&gt;<i> Dzony and the team.
</I>&gt;<i>
</I>&gt;<i> _______________________________________________
</I>&gt;<i> LARTC mailing list / <A HREF="mailto:[email protected]">[email protected]</A> </I>&gt;<i> <A HREF="http://mailman.ds9a.nl/mailman/listinfo/lartc">http://mailman.ds9a.nl/mailman/listinfo/lartc</A> HOWTO:
</I><A HREF="http://ds9a.nl/2.4Routing/">http://ds9a.nl/2.4Routing/</A>

</PRE>

#1 lore raw

<PRE>On Mon, Oct 16, 2000 at 01:44:50PM +0200, Daniel Bergqvist wrote:
&gt;<i> Hi!
</I>&gt;<i>
</I>&gt;<i> The devices eth1 and eth3 MUST be active. Remove &quot;ip link set down eth1&quot; and </I>&gt;<i> &quot;ip link set down eth3&quot;. You might get problems with &quot;TCP packet reordering&quot; </I>&gt;<i> resulting in lower bandwidth but I'm currently working with a patch to the </I>&gt;<i> sch_teql driver. I will post it to the list if/when I get it to work.
</I>
Read the archive of <A HREF="mailto:[email protected]">[email protected]</A>, I discussed it with Alexey and Jamal there and they had some reservations about the idea. What might work is set
up the bundled device, and run a tcp/ip tunnel over it, like 'vtund'. This
lets the Linux TCP/IP stack reorder packets. Linux is not disturbed by
simple reordering problems, and thus solves your problems.

The only remaining problem is that tunneling over tcp/ip has some problems of its own.

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>HI,
I read IP Command Reference from A. Kuznetsov and in section about interface flags is:

SLAVE - this interface is bonded to some another interface to share link capacities.

If I understanded this, it is a posibility to make something similar what do cisco IOS if it slaves interface under dummy, dummy have assigned an IP address, slave interfaces are without IP adress.

But in IP Command Reference it is no note about slaving an interface.

PSIkappa
<A HREF="mailto:[email protected]">[email protected]</A>

</PRE>

#3 lore raw
In reply to Daniel Bergqvist [email protected]

<PRE>On Tue, Oct 17, 2000 at 05:42:23PM +0200, Miro PSIkappa F. wrote:

&gt;<i> If I understanded this, it is a posibility to make something similar what </I>&gt;<i> do cisco IOS if it slaves interface under dummy, dummy have assigned an IP </I>&gt;<i> address, slave interfaces are without IP adress.
</I>&gt;<i>
</I>&gt;<i> But in IP Command Reference it is no note about slaving an interface. </I>
I think this has to to with TEQL, see the relevant chapter on that.

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>