search for: teql0

...ithout netem, and teql works as expected: ping traffic goes to both interfaces. ) ========= Machine 1 with NetEm ============ Commands to install NetEm and TEQL together: # modprobe sch_teql # tc qdisc add dev eth0 root handle 1: netem delay 10ms # tc qdisc add dev eth0 parent 1:1 handle 10: teql0 # tc qdisc add dev eth1 root teql0 # ip link set dev teql0 up # ip addr add dev eth0 10.0.0.1/30 # ip addr add dev eth1 10.0.0.5/30 # ip addr add dev teql0 10.0.0.9/30 # echo 0 > /proc/sys/net/ipv4/conf/eth0/rp_filter # echo 0 > /proc/sys/net/ipv4/conf/eth1/rp_filter [root@machine1]#...

...is for two computers connected directly with two links. My topology is a little different: one link is connected directly, but the other is connected through a gateway. My problem is teql can''t send packets through both links at the same time. When I don''t configure a gateway for teql0 in the routing table, all packets go to the direct link; when I do add the gateway, all packets go to the link with the gateway. It seems to me that the problem is that when packets are forwarded by the teql0 interface to each local Ethernet cards, the routing is still based on the routing entry f...

...1 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...

...hen I test the other connection with TEQL and it works fine to, but then I add both connections to TEQL and then the speed go down to 1Mbit/s. WAN router: # Connected to the 10.0.0.0/8 network eth0: 10.1.1.118/24 eth1: 10.2.20.1/30 # First WAN connection eth2: 10.2.20.5/30 # Second WAN connection teql0: 10.2.20.9/30 # TEQL connection LAN router: # Connected to the 10.2.18.0/24 network eth0: 10.2.18.254/24 eth1: 10.2.20.2/30 # First WAN connection eth2: 10.2.20.6/30 # Second WAN connection teql0: 10.2.20.10/30 # TEQL connection On the WAN router I route 10.2.18.0/24 to 10.2.20.10 dev teql0. On...

TEQL and Subnet problem I have a network topology shown below, and I am trying to use TEQL. My problem is: When I ping to P3.teql0 from P2 ("[P2]# ping 16.119.144.66"), the traffic can never go from P2.eth1, and all traffic only goes to P1.eth0. What P2.eth1 (16.119.144.33) did is broadcasting an ARP asking for the MAC address of 16.119.144.66, although I have specified the route to 16.119.144.64/30 is through gatewa...

...phrase the question and hopefully some one may be willing to read. Sorry to spam. I am using TEQL on two computers, each with two network interfaces. The two eth0 are connected directly, and the two eth1 are connected via a gateway (a linux machine). The problem is that when I send packets through teql0 to the other machine (ping -I teql0), the packets can''t go through eth1 and all packets go via eth0. But I can send packets via eth1 directly (ping -I eth1). What''s wrong? P.S. I put eth1 and teql0 on one computer, and the gateway interface on the same side into one subnet. I on...

...+-------+ | |==========| | ''network 1'' ----| A | | B |---- ''network 2'' | |==========| | +-------+ eth2 +-------+ A and B are routers # tc qdisc add dev eth1 root teql0 # tc qdisc add dev eth2 root teql0 # ip link set dev teql0 up On router A: # ip addr add dev eth1 10.0.0.0/31 # ip addr add dev eth2 10.0.0.2/31 # ip addr add dev teql0 10.0.0.4/31 On router B: # ip addr add dev eth1 10.0.0.1/31 # ip addr add dev eth2 10.0.0.3/31 # ip addr add dev teql0 10.0.0....

..., and each has two network cards. P2 and P3 are connected in two ways: (1) directed connection between P2.eth0 and P3.eth0; (2) connection via P1. P1 acts as the gateway. TEQL is installed on P2 and P3 to load-balance packet transmission by round-robin sending packets to eth0 and eth1. I defined P2.teql0, P2.eth1, P1.eth0 as 16.119.144.32/30 subnet, and defined P3.teql0, P3.eth1, P1.eth1 as 16.119.144.64/30 subnet. My problem is: When I ping to P3.teql0 from P2 ("[P2]# ping 16.119.144.66"), the traffic can never go from P2.eth1, and all traffic only goes to P1.eth0. What P2.eth1 (16.119....

I''am using the following script to aggregate the bandwidth of one quad gigabit ethernet controller (pci-express). #!/bin/bash sysctl -w net.ipv4.tcp_reordering = 30 ifconfig eth1 up ifconfig eth2 up ifconfig eth3 up ifconfig eth4 up modprobe sch_teql tc qdisc add dev eth1 root teql0 tc qdisc add dev eth2 root teql0 tc qdisc del dev eth3 root teql0 tc qdisc del dev eth4 root teql0 ip link set dev teql0 up ip addr flush dev eth1 ip addr flush dev eth2 ip addr flush dev eth3 ip addr flush dev eth4 ip addr flush dev teql0 ip addr add dev eth1 10.0.0.3/31 ip addr add dev eth2 10.0....

...9; iwconfig ath1 channel 11 iwconfig ath1 key ''password'' ifconfig ath1 up ifconfig ath1 192.168.2.YYY ifconfig ath1 netmask 255.255.255.0 ifconfig ath1 broadcast 192.168.2.255 where YYY is 100 for host A and 101 for host B. Then I try modprobe sch_teql tc qdisc add dev ath0 root teql0 tc qdisc add dev ath1 root teql0 ip link set dev teql0 up ifconfig teql0 192.168.1.YYY After this step I cannot ping via any of {ath0, ath1, teql0}. I have tried renaming the devices to eth1 and eth2 via ip link set dev ath0 name eth1. I do this before the iwconfig commands above, but this does n...

...NIC ). The way i set this up is so that internal network clients will be routed through the 3 nics with their packets sent out in a round robin sort of fashion. I found a few sites explaining a bit about how to do this, and the current setup i found that somewhat works is this: A virtual device teql0 is created: This virtual device teql0 is an imaginary device using QoS Trivial link equalizer (TeQL). It has a static ip address assigned to it. If you attempt to ping it from another machine, you wont necessarily be pinging the same network card every time. Code:  tc qdisc add dev eth0 root teql...

...only one on earth that would be needing a such thing. This is the first question. The second question is, which interface should I do QoS on? My gw computer (are using FC3, Linux 2.6): eth0 = my LAN eth1 = ISP1 eth2 = ISP2 tun0 = tunnel that goes over ISP1 tun1 = tunnel that goes over ISP2 teql0 = the upstream of ISP1 and ISP2 added together, later splits into tun0 and tun1 computer at my LAN -> eth0 -> teql0 -> tun0 -> eth1 (one example of how a packet would go...) Question is: Should I do QoS at eth0? At eth0 and teql0? Just teql0? Help is highly appreciated.

...nd-robin way, a weighted teql is achieved (my guess). I already have two physical network interfaces, eth0 and eth1. I created a virtual interfaces based on eth1: # ifconfig eth1:0 10.0.0.2 After that I can see eth1:0 in the "ifconfig" result. Then I try to add the virtual interface to teql0: # tc qdisc add dev eth1:0 root teql0 But I got the error message: Cannot find device "eth1:0" What''s wrong with my method? I didn''t see ip_alias module in the "lsmod", but since I can see eth1:0 in "ifconfig", I assume the module is loaded in the k...

...ation). The two tunnels are GRE ip tunnel. It seems to work fine in theory : I manage to send packet on the teql from one of the node (debian sid with kernel 2.4.20-686). But I''ve got a problem to put a teql qdisc on the tunnel on one of the node. When doing : tc qdisc add dev tun1 root teql0 I only manage to have an RTnetlink message. But when doing : tc qdisc add dev eth0 root teql0 It works fine. The second router is debian woody based with a from sid backported tc and a 2.4.20 home made kernel. Is there a special requirement to have this working ? BR, -- Eric Leblond <eric@re...

...ath routing using iproute2 nexthop at the moment, and that works fine for firewalling. But now I have a need for shaping and shaping only works over a single interface it seems and not over multiple interfaces. According to the HOWTO I can setup a teql device to bundle the hdlc0-2 into a single teql0 device, but that requires an extra combined IP address at both sides it seems. The question is whether I can get away with setting up the teql device over the three hdlc IPs with an ip on the teql device that''s either fake or one of our class C subnet (maybe even reuse the IP of the et...

...RH 9 (kernel 2.4.20) machine. (eth0, eth1 and eth2). I want to setup a 'link equalizer' (teql) between eth0 and eth1. This I am able to do with the required commands (using the utilities 'tc' and 'ip'). Now I need to setup a bridge between eth2 and this new interface 'teql0'. This is not possible as 'teql' is not a 'bridgable' interface. Is it possible to rewrite the 'teql' in such a way as to enable it to be bridged? Or should I look into any different approach for attaining this? Thanks in advance for any help/pointers you can provide....

...;trunk'') some connections. In the LARTC-manual I found the chapter about TEQL (see chapter 10). The situation in that example is too link 2 networks. I need to link a network to 1 remote gateway. The problem I can''t solve on my own is that you can only add physical devices to the teql0 qdisc. Therefore the following won''t work: +--------------+ eth1 +--------+ +----------+ | |========== | | eth0 | | ''network 1'' ----| BETAGATE | | INET | ======== | ZEUS |...

...forever 4: eth1: <BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast qlen 1000 link/ether 00:50:fc:4d:68:ad brd ff:ff:ff:ff:ff:ff inet 192.168.1.1/24 brd 192.168.1.255 scope global eth1 inet6 fe80::250:fcff:fe4d:68ad/64 scope link valid_lft forever preferred_lft forever 5: teql0: <NOARP> mtu 1500 qdisc noop qlen 100 link/void 6: tunl0: <NOARP> mtu 1480 qdisc noop link/ipip 0.0.0.0 brd 0.0.0.0 7: gre0: <NOARP> mtu 1476 qdisc noop link/gre 0.0.0.0 brd 0.0.0.0 8: sit0: <NOARP> mtu 1480 qdisc noop link/sit 0.0.0.0 brd 0.0.0.0 9: ip6t...

...lem reporting page, so I will include them, even though I don''t think they''re relevent: $ ip addr show 1: lo: <LOOPBACK,UP> mtu 16436 qdisc noqueue link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo inet6 ::1/128 scope host 2: teql0: <NOARP> mtu 1500 qdisc noop qlen 100 link/void 3: dummy0: <BROADCAST,NOARP> mtu 1500 qdisc noop link/ether 00:00:00:00:00:00 brd ff:ff:ff:ff:ff:ff 4: eth0: <BROADCAST,MULTICAST,ALLMULTI,PROMISC,UP> mtu 1500 qdisc pfifo_fast qlen 1000 link/ether 00:ba:ac:8a:bf:ca brd...