loadbalancing@highlander.my-scotland.co.uk
2000-Oct-16 10:03 UTC
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 operation. Please let us know how to do. Thanks Dzony and the team.
Hi! The devices eth1 and eth3 MUST be active. Remove "ip link set down eth1" and "ip link set down eth3". You might get problems with "TCP packet 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ån: lartc-admin@mailman.ds9a.nl > [mailto:lartc-admin@mailman.ds9a.nl]För > loadbalancing@highlander.my-scotland.co.uk > Skickat: Monday, October 16, 2000 12:03 PM > Till: lartc@mailman.ds9a.nl > Ämne: [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 operation. > > Please let us know how to do. > > Thanks > > Dzony and the team. > > _______________________________________________ > LARTC mailing list / LARTC@mailman.ds9a.nl > http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO:http://ds9a.nl/2.4Routing/
This is basicly what I''m trying to do, but inside the sch_teql driver. What is the problems with tunnels? Where is the archive for netdev@oss.sgi.com? Thanks, Daniel> -----Ursprungligt meddelande----- > Från: lartc-admin@mailman.ds9a.nl > [mailto:lartc-admin@mailman.ds9a.nl]För bert hubert > > Read the archive of netdev@oss.sgi.com, 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 > > -- > PowerDNS Versatile DNS Services > Trilab The Technology People > ''SYN! .. SYN|ACK! .. ACK!'' - the mating call of the internet > > _______________________________________________ > LARTC mailing list / LARTC@mailman.ds9a.nl > http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO:http://ds9a.nl/2.4Routing/
On Mon, Oct 16, 2000 at 01:44:50PM +0200, Daniel Bergqvist wrote:> Hi! > > The devices eth1 and eth3 MUST be active. Remove "ip link set down eth1" and > "ip link set down eth3". You might get problems with "TCP packet 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.Read the archive of netdev@oss.sgi.com, 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 -- PowerDNS Versatile DNS Services Trilab The Technology People ''SYN! .. SYN|ACK! .. ACK!'' - the mating call of the internet
On Mon, Oct 16, 2000 at 03:25:37PM +0200, Daniel Bergqvist wrote:> This is basicly what I''m trying to do, but inside the sch_teql driver. What > is the problems with tunnels?If your link saturates and you get packetloss, you get very weird performance problems. Also, one lost packet stops *all* your IP traffic until it''s resent.> Where is the archive for netdev@oss.sgi.com?It appears to have died. I''ll forward you the right messages. Regards, bert hubert -- PowerDNS Versatile DNS Services Trilab The Technology People ''SYN! .. SYN|ACK! .. ACK!'' - the mating call of the internet
> Från: lartc-admin@mailman.ds9a.nl > [mailto:lartc-admin@mailman.ds9a.nl]För bert hubert > > On Mon, Oct 16, 2000 at 03:25:37PM +0200, Daniel Bergqvist wrote: > > > This is basicly what I''m trying to do, but inside the sch_teql > driver. What > > is the problems with tunnels? > > If your link saturates and you get packetloss, you get very weird > performance problems. Also, one lost packet stops *all* your IP traffic > until it''s resent.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 the teql_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.> > > Where is the archive for netdev@oss.sgi.com? > > It appears to have died. I''ll forward you the right messages.I got it. Thanks!> Regards, > > bert hubertRegards, Daniel
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 psi@atlantis.sk
On Tue, Oct 17, 2000 at 05:42:23PM +0200, Miro PSIkappa F. wrote:> 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.I think this has to to with TEQL, see the relevant chapter on that. Regards, bert hubert -- PowerDNS Versatile DNS Services Trilab The Technology People ''SYN! .. SYN|ACK! .. ACK!'' - the mating call of the internet
Hi all, I''m trying to write a command reference for TC. It''s a lot of work left to do but I post it already for your comments. If anyone wants to help writing some part or explain some things better you are most welcome to do so. TC command reference: http://linux.bergqvist.se/tc/tc_command_reference.htm Regards, Daniel