-----Ursprungligt meddelande-----

Hi!

The devices eth1 and eth3 MUST be active. Remove "ip link set down eth=
1" and
"ip link set down eth3". You might get problems with "TCP pa=
cket reordering"
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

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