From: Fabio Uggeri <f.uggeri@iol.it>
To: linux-net@vger.kernel.org
Subject: TEQL with two ADSL connection
Date: Sun, 28 Apr 2002 18:35:42 +0200 [thread overview]
Message-ID: <3CCC24DE.55D71C61@iol.it> (raw)
Hi all,
I have:
- two Netopia router for ADSL,
- one linux box with 3 ethernet card
The LAN interface, of the two ADSL router, have address
(A) 192.168.0.254
(B) 192.168.2.254
The 3 ethernet card have address:
-eth2 172.16.255.254, connected to a switch and operate with VLANs
-eth1 192.168.0.2, directly connected to the router (A)
-eth0 192.168.2.2, directly connected to the router (B)
The routing with router (A) or (B) work fine.
I want to do a load balancing using teql
I have configured the qdisc and teql as follow
#ip route del default
#tc qdisc add dev eth0 root teql0
#tc qdisc add dev eth1 root teql0
#ip addr del 192.168.0.2 dev eth1
#ip addr del 192.168.2.2 dev eth0
#ip address add 192.168.0.2/24 dev teql0
#ip address add 192.168.2.2/24 dev teql0
#ip link set teql0 up
#ip route add default/0 dev teql0
The rp filter of eth0 and eth1 are turned off by default.
After I have done some ping and traceroute but I haven't answers
then I have done
#ip neigh ls
172.16.240.1 dev eth2 lladdr 00:d0:b7:49:6f:09 nud stale
172.16.1.3 dev vlan0017 lladdr 00:10:a7:0f:01:23 nud stale
172.16.4.4 dev vlan0017 lladdr 00:10:a7:12:4c:01 nud stale
172.16.97.3 dev vlan0014 lladdr 00:40:f4:34:b5:69 nud reachable
#tc -s qdisc ls
qdisc teql0 8001: dev eth0
Sent 829337 bytes 5807 pkts (dropped 0, overlimits 0)
qdisc teql0 8002: dev eth1
Sent 4536 bytes 108 pkts (dropped 0, overlimits 0)
# ip -s link ls
1: lo: <LOOPBACK,UP> mtu 16436 qdisc noqueue
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
RX: bytes packets errors dropped overrun mcast
420 6 0 0 0 0
TX: bytes packets errors dropped carrier collsns
420 6 0 0 0 0
2: teql0: <BROADCAST,NOARP,UP> mtu 1500 qdisc pfifo_fast qlen 100
link/[65535]
RX: bytes packets errors dropped overrun mcast
0 0 0 0 0 0
TX: bytes packets errors dropped carrier collsns
0 0 161 161 0 0
3: eth0: <BROADCAST,MULTICAST,UP> mtu 1500 qdisc teql0 qlen 100
link/ether 00:00:21:e7:9f:93 brd ff:ff:ff:ff:ff:ff
RX: bytes packets errors dropped overrun mcast
6445168 9286 0 0 0 0
TX: bytes packets errors dropped carrier collsns
1233331 8555 0 0 0 1
4: eth1: <BROADCAST,MULTICAST,UP> mtu 1500 qdisc teql0 qlen 100
link/ether 00:00:21:e3:d1:78 brd ff:ff:ff:ff:ff:ff
RX: bytes packets errors dropped overrun mcast
354 4 0 0 0 0
TX: bytes packets errors dropped carrier collsns
6834 112 0 0 0 0
5: eth2: <BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast qlen 100
link/ether 00:a0:d2:12:8f:bb brd ff:ff:ff:ff:ff:ff
RX: bytes packets errors dropped overrun mcast
1817579 12549 0 0 0 0
TX: bytes packets errors dropped carrier collsns
6473156 9749 0 0 0 0
6: vlan0005: <BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue
link/ether 00:a0:d2:12:8f:bb brd ff:ff:ff:ff:ff:ff
RX: bytes packets errors dropped overrun mcast
13487 188 0 0 0 37
TX: bytes packets errors dropped carrier collsns
424811 287 0 0 0 0
......
.......
#ip route list
192.168.2.0/24 dev teql0 proto kernel scope link src 192.168.2.2
192.168.0.0/24 dev teql0 proto kernel scope link src 192.168.0.2
172.16.240.0/20 dev eth2 proto kernel scope link src 172.16.255.254
172.16.128.0/20 dev vlan0025 proto kernel scope link src
172.16.143.254
172.16.80.0/20 dev vlan0013 proto kernel scope link src 172.16.95.254
........
.......
127.0.0.0/8 dev lo scope link
default dev teql0 scope link
Any suggestion will be appreciated
Tank you
Fabio
next reply other threads:[~2002-04-28 16:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-28 16:35 Fabio Uggeri [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-05-01 8:54 TEQL with two ADSL connection Fabio Uggeri
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3CCC24DE.55D71C61@iol.it \
--to=f.uggeri@iol.it \
--cc=linux-net@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).