how to emulate large IP routing table
Hi all
I am conducting the experiments comparing IP router forwarding delay and MPLS LSR forwarding delay, it is obvious in theory MPLS in Core should be faster than IP, but for small netork (only have several core routers), result show it is not, this is why I want emulate a large IP routing table in one core router.
can I do it and how ? right now I use static routing table (by using command : ip route add network/mask via gateway)
thanks anyway
yuxiao
----- Original Message -----
From: <[email protected]>
To: <[email protected]>
Sent: Sunday, June 15, 2003 2:15 PM
Subject: LARTC digest, Vol 1 #1225 - 6 msgs
Quoted 11 lines
Send LARTC mailing list submissions to
[email protected]To subscribe or unsubscribe via the World Wide Web, visit
http://mailman.ds9a.nl/mailman/listinfo/lartc
or, via email, send a message with subject or body 'help' to [email protected]You can reach the person managing the list at
[email protected]
Quoted 7 lines
When replying, please edit your Subject line so it is more specific than "Re: Contents of LARTC digest..."
Today's Topics:
1. Re: Low latency on large uploads - almost done but not quite. (Stef
Coene)
Quoted 1 line
2. Re: Low latency on large uploads - almost done but not quite. (Thilo
Schulz)
Quoted 2 lines
3. herz the script that i have done. (Trevor Warren)
4. Re: Low latency on large uploads - almost done but not quite. (Stef
Coene)
Quoted 10 lines
5. Re: herz the script that i have done. (Stef Coene)
6. Re: htb problem (Stef Coene)--__--__--
Message: 1
From: Stef Coene <[email protected]>
Organization: None
To: [email protected], [email protected]
Subject: Re: [LARTC] Low latency on large uploads - almost done but not
quite.
Quoted 17 lines
Date: Sun, 15 Jun 2003 11:09:09 +0200
Quoted 1 line
Here's still my script, if you are interested to look at it.
I'm interested and I have some remarks.
Quoted 12 lines
#!/bin/bash
DEV=ppp0
# delete any qdiscs or rule sets created so far. tc qdisc del dev $DEV root 2> /dev/null > /dev/null # tc qdisc del dev $DEV ingress 2> /dev/null > /dev/null# create the root qdisc tc qdisc add dev $DEV root handle 1: htb default 13# install a root class, so that other clients can borrow from each
other.
Quoted 4 lines
Quoted 4 lines
tc class add dev $DEV parent 1: classid 1:1 htb rate 15kbps ceil 15kbps
# now install 4 sub classes for different priorities # highest priority for low latency games like quake3 and ssh / ftp
control.
Quoted 1 line
Quoted 1 line
tc class add dev $DEV parent 1:1 classid 1:10 htb rate 7kbps ceil 15kbps
\
Quoted 2 lines
Quoted 2 lines
prio 0 burst 20000b cburst 22000b
# not as high but still high priority for ACK's - useful for keeping
large
Quoted 4 lines
Quoted 4 lines
# d/l's alive :)
tc class add dev $DEV parent 1:1 classid 1:11 htb rate 7kbps ceil 15kbps prio 1 burst 200b cburst 200b# very few data allowed for HTTP requests, but still higher priority
than
Quoted 7 lines
Quoted 6 lines
bulk uploads.
tc class add dev $DEV parent 1:1 classid 1:12 htb rate 2kbps ceil 15kbps prio 10 burst 1b cburst 1b# bulk uploads have no prio :D tc class add dev $DEV parent 1:1 classid 1:13 htb rate 1bps ceil 15kbps prio 20 burst 1b cburst 1bYour burst is too low. I understand you want a minimum burst, but you
have to
Quoted 1 line
follow some rules. The best you can do is to remove the burst/cburst
option
Quoted 5 lines
so htb can calculate the minimum burst/cburst for you.
And don't you get quantum errors in your kernel log? That's because your quantum is too low for the classes. There is a long explanation for this, see www.docum.org on the faq page.
You also use different prio's. This can be ok in most cases, except if
you
Quoted 1 line
have a low prio class that's sending more data then the configured rate.
If
Quoted 2 lines
you do so, the latency can go up for that class. I (still) didn't test it myself, but you can find prove of it on the htb homepage. The solution
for
Quoted 14 lines
this is to make sure you never put too much traffic in a low prio class.
Quoted 4 lines
# now make all qdiscs simple pfifo # small queues for minimum latency tc qdisc add dev $DEV parent 1:10 handle 20: pfifo limit 0 tc qdisc add dev $DEV parent 1:11 handle 30: pfifo limit 0Are you sure limit 0 is possible ????
Quoted 6 lines
# larger queues for more latency. tc qdisc add dev $DEV parent 1:12 handle 40: pfifo limit 5 tc qdisc add dev $DEV parent 1:13 handle 50: pfifo limit 20#quake3-style udp games have been marked in iptables
tc filter add dev $DEV protocol ip parent 1: prio 0 handle 1 fw flowid
1:10
Quoted 2 lines
Quoted 2 lines
# icmp to get the response times. tc filter add dev $DEV protocol ip parent 1: prio 1 u32 match ip
protocol 1
Quoted 3 lines
Quoted 3 lines
0xffflowid 1:10# ssh - not scp! scp is seperated by the TOS bits from ssh tc filter add dev $DEV protocol ip parent 1: prio 2 u32 match ip dport
22
Quoted 3 lines
Quoted 3 lines
0xffffmatch ip tos0x100xffflowid 1:10# ftp tc filter add dev $DEV protocol ip parent 1: prio 3 u32 match ip dport
21
Quoted 3 lines
Quoted 3 lines
0xffffmatch ip tos0x100xffflowid 1:10
# ACK packets ..
tc filter add dev $DEV protocol ip parent 1: prio 4 u32 match ip
protocol 6
Quoted 4 lines
Quoted 4 lines
0xffmatch u80x050x0fat 0 match u160x00000xffc0at 2 match u80x100xffat 33 flowid 1:11
# HTTP requests
tc filter add dev $DEV protocol ip parent 1: prio 10 u32 match ip dport
80
Quoted 12 lines
Quoted 1 line
0xffffflowid 1:12Stef
--
[email protected]
"Using Linux as bandwidth manager"
http://www.docum.org/
#lartc @ irc.oftc.net
Quoted 7 lines
--__--__--
Message: 2
From: Thilo Schulz <[email protected]>
Reply-To: [email protected]
To: [email protected]
Subject: Re: [LARTC] Low latency on large uploads - almost done but not
quite.
Quoted 10 lines
Date: Sun, 15 Jun 2003 13:44:10 +0200
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1Quoted 4 lines · you
Quoted 1 line
Here's still my script, if you are interested to look at it.
I'm interested and I have some remarks.
Your burst is too low. I understand you want a minimum burst, but you
ha> ve
Quoted 6 lines
Quoted 2 lines
to follow some rules. The best you can do is to remove the burst/cburst option so htb can calculate the minimum burst/cburst for you.
yes, sounds reasonable now that I spend a second thought about it.
Quoted 1 line
And don't you get quantum errors in your kernel log? That's because
your
Quoted 1 line
Quoted 1 line
quantum is too low for the classes. There is a long explanation for
this,
Quoted 5 lines
Quoted 1 line
see www.docum.org on the faq page.
hmm .. quantum? I have never set quantum with any parameter, or have I?
Quoted 1 line
You also use different prio's. This can be ok in most cases, except if
y> ou
Quoted 1 line
Quoted 1 line
have a low prio class that's sending more data then the configured
rate.>
Quoted 1 line
Quoted 1 line
If you do so, the latency can go up for that class. I (still) didn't
test
Quoted 1 line
Quoted 1 line
it myself, but you can find prove of it on the htb homepage. The
solution
Quoted 4 lines
Quoted 2 lines
for this is to make sure you never put too much traffic in a low prio class.
I have given plenty of bandwidth to the 1:10 class. Quake3 streams are
max.>
Quoted 63 lines
1500 bytes/s. And ssh does not use that much either.
Quoted 6 lines
Quoted 4 lines
# now make all qdiscs simple pfifo # small queues for minimum latency tc qdisc add dev $DEV parent 1:10 handle 20: pfifo limit 0 tc qdisc add dev $DEV parent 1:11 handle 30: pfifo limit 0Are you sure limit 0 is possible ????
Yes, at least the status command showed me, that the limit was set to 0.
- Thilo Schulz
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.2 (GNU/Linux)iD8DBQE+7FwPZx4hBtWQhl4RAn8XAKDSJR6E7w3Q6I0ki4bVpDGfH//anwCfestd aj5fVwoC9ANATJ1CA50N5P4=
=9XOi
-----END PGP SIGNATURE-------__--__--
Message: 3
From: Trevor Warren <[email protected]>
To: lartc <[email protected]>
Cc: Stef Coene <[email protected]>, Trevor Warren <[email protected]>
Organization: Red Hat India
Date: 15 Jun 2003 05:16:31 +0530
Subject: [LARTC] herz the script that i have done.This is a MIME-formatted message. If you see this text it means that your E-mail software does not support MIME-formatted messages.
--=_jive-4095-1055677798-0001-2
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 7bitHello there,
Having made quite a lot of expensive mistakes i have finally clobbered
together a script for the users on my network.Have a look at it and please suggest as to how can i limit bandwidth to
each ip on this network to about 64Kbits.Trevor
--
( >- GNU/LINUX, It's all about CHOICE -< )
/~\ __ [email protected] __ /~\| \) / Pre Sales Consultant - Red Hat \ (/ | |_|_ \ 9820349221(M) | 22881326(O) / _|_| \___________________________________/--=_jive-4095-1055677798-0001-2
Content-Type: text/x-sh; name="final.sh"; charset=utf-8
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment; filename=final.sh
Quoted 8 lines
#!/bin/bash
#####################################
#Deleting and setting up
#Root qdisc's
#####################################
tc qdisc del dev eth0 root
tc qdisc add dev eth0 root handle 1:0 cbq bandwidth 1Mbit avpkt 1000 cell
8
Quoted 9 lines
#######################################
#Setting up top 2 qdiscs
#for initial packet classification
#######################################
# Exatt Rules
#######################################tc class add dev eth0 parent 1:0 classid 1:1 cbq bandwidth 1Mbit rate
800kbit weight 80kbit allot 1514 cell 8 maxburst 20 avpkt 1000 isolated
Quoted 1 line
tc filter add dev eth0 parent 1:0 protocol ip u32 match ip src
192.168.10.0/24 classid 1:1
Quoted 1 line
tc filter add dev eth0 parent 1:0 protocol ip u32 match ip dst
192.168.10.0/24 classid 1:1
Quoted 2 lines
tc filter add dev eth0 parent 1:0 protocol ip u32 match ip src
192.168.11.0/24 classid 1:1
Quoted 1 line
tc filter add dev eth0 parent 1:0 protocol ip u32 match ip dst
192.168.11.0/24 classid 1:1
Quoted 2 lines
tc filter add dev eth0 parent 1:0 protocol ip u32 match ip src
192.168.12.0/24 classid 1:1
Quoted 1 line
tc filter add dev eth0 parent 1:0 protocol ip u32 match ip dst
192.168.12.0/24 classid 1:1
Quoted 2 lines
tc filter add dev eth0 parent 1:0 protocol ip u32 match ip src
192.168.13.0/24 classid 1:1
Quoted 1 line
tc filter add dev eth0 parent 1:0 protocol ip u32 match ip dst
192.168.13.0/24 classid 1:1
Quoted 2 lines
tc filter add dev eth0 parent 1:0 protocol ip u32 match ip src
192.168.14.0/24 classid 1:1
Quoted 1 line
tc filter add dev eth0 parent 1:0 protocol ip u32 match ip dst
192.168.14.0/24 classid 1:1
Quoted 2 lines
tc filter add dev eth0 parent 1:0 protocol ip u32 match ip src
192.168.15.0/24 classid 1:1
Quoted 1 line
tc filter add dev eth0 parent 1:0 protocol ip u32 match ip dst
192.168.15.0/24 classid 1:1
Quoted 2 lines
tc filter add dev eth0 parent 1:0 protocol ip u32 match ip src
192.168.16.0/24 classid 1:1
Quoted 1 line
tc filter add dev eth0 parent 1:0 protocol ip u32 match ip dst
192.168.16.0/24 classid 1:1
Quoted 2 lines
tc filter add dev eth0 parent 1:0 protocol ip u32 match ip src
192.168.17.0/24 classid 1:1
Quoted 1 line
tc filter add dev eth0 parent 1:0 protocol ip u32 match ip dst
192.168.17.0/24 classid 1:1
Quoted 2 lines
tc filter add dev eth0 parent 1:0 protocol ip u32 match ip src
192.168.18.0/24 classid 1:1
Quoted 1 line
tc filter add dev eth0 parent 1:0 protocol ip u32 match ip dst
192.168.18.0/24 classid 1:1
Quoted 2 lines
tc filter add dev eth0 parent 1:0 protocol ip u32 match ip src
192.168.19.0/24 classid 1:1
Quoted 1 line
tc filter add dev eth0 parent 1:0 protocol ip u32 match ip dst
192.168.19.0/24 classid 1:1
Quoted 6 lines
##########################################
#Paradyne Rules
##########################################
tc class add dev eth0 parent 1:0 classid 1:2 cbq bandwidth 1Mbit rate
200kbit weight 20kbit allot 1514 cell 8 maxburst 20 avpkt 1000 bounded
Quoted 1 line
tc filter add dev eth0 parent 1:0 protocol ip u32 match ip src
192.168.20.0/24 classid 1:2
Quoted 1 line
tc filter add dev eth0 parent 1:0 protocol ip u32 match ip dst
192.168.20.0/24 classid 1:2
Quoted 2 lines
tc filter add dev eth0 parent 1:0 protocol ip u32 match ip src
192.168.21.0/24 classid 1:2
Quoted 1 line
tc filter add dev eth0 parent 1:0 protocol ip u32 match ip dst
192.168.21.0/24 classid 1:2
Quoted 2 lines
tc filter add dev eth0 parent 1:0 protocol ip u32 match ip src
192.168.22.0/24 classid 1:2
Quoted 1 line
tc filter add dev eth0 parent 1:0 protocol ip u32 match ip dst
192.168.22.0/24 classid 1:2
Quoted 2 lines
tc filter add dev eth0 parent 1:0 protocol ip u32 match ip src
192.168.23.0/24 classid 1:2
Quoted 1 line
tc filter add dev eth0 parent 1:0 protocol ip u32 match ip dst
192.168.23.0/24 classid 1:2
Quoted 2 lines
tc filter add dev eth0 parent 1:0 protocol ip u32 match ip src
192.168.24.0/24 classid 1:2
Quoted 1 line
tc filter add dev eth0 parent 1:0 protocol ip u32 match ip dst
192.168.24.0/24 classid 1:2
Quoted 2 lines
tc filter add dev eth0 parent 1:0 protocol ip u32 match ip src
192.168.25.0/24 classid 1:2
Quoted 1 line
tc filter add dev eth0 parent 1:0 protocol ip u32 match ip dst
192.168.25.0/24 classid 1:2
Quoted 2 lines
tc filter add dev eth0 parent 1:0 protocol ip u32 match ip src
192.168.26.0/24 classid 1:2
Quoted 1 line
tc filter add dev eth0 parent 1:0 protocol ip u32 match ip dst
192.168.26.0/24 classid 1:2
Quoted 2 lines
tc filter add dev eth0 parent 1:0 protocol ip u32 match ip src
192.168.27.0/24 classid 1:2
Quoted 1 line
tc filter add dev eth0 parent 1:0 protocol ip u32 match ip dst
192.168.27.0/24 classid 1:2
Quoted 2 lines
tc filter add dev eth0 parent 1:0 protocol ip u32 match ip src
192.168.28.0/24 classid 1:2
Quoted 1 line
tc filter add dev eth0 parent 1:0 protocol ip u32 match ip dst
192.168.28.0/24 classid 1:2
Quoted 2 lines
tc filter add dev eth0 parent 1:0 protocol ip u32 match ip src
192.168.29.0/24 classid 1:2
Quoted 1 line
tc filter add dev eth0 parent 1:0 protocol ip u32 match ip dst
192.168.29.0/24 classid 1:2
Quoted 8 lines
#######################################
#Setting up top 10 qdiscs
#for initial Exatt packet classification
#######################################
tc class add dev eth0 parent 1:1 classid 1:3 cbq bandwidth 1Mbit rate
80Kbit allot 1514 cell 8 maxburst 20 avpkt 1000 weight 8Kbit bounded isolated
Quoted 1 line
tc filter add dev eth0 parent 1:1 protocol ip u32 match ip src
192.168.10.0/24 classid 1:3
Quoted 1 line
tc filter add dev eth0 parent 1:1 protocol ip u32 match ip dst
192.168.10.0/24 classid 1:3
Quoted 2 lines
tc class add dev eth0 parent 1:1 classid 1:4 cbq bandwidth 1Mbit rate
80Kbit allot 1514 cell 8 maxburst 20 avpkt 1000 weight 8Kbit bounded isolated
Quoted 1 line
tc filter add dev eth0 parent 1:1 protocol ip u32 match ip src
192.168.11.0/24 classid 1:4
Quoted 1 line
tc filter add dev eth0 parent 1:1 protocol ip u32 match ip dst
192.168.11.0/24 classid 1:4
Quoted 1 line
tc class add dev eth0 parent 1:1 classid 1:5 cbq bandwidth 1Mbit rate
80Kbit allot 1514 cell 8 maxburst 20 avpkt 1000 weight 8Kbit bounded isolated
Quoted 1 line
tc filter add dev eth0 parent 1:1 protocol ip u32 match ip src
192.168.12.0/24 classid 1:5
Quoted 1 line
tc filter add dev eth0 parent 1:1 protocol ip u32 match ip dst
192.168.12.0/24 classid 1:5
Quoted 2 lines
tc class add dev eth0 parent 1:1 classid 1:6 cbq bandwidth 1Mbit rate
80Kbit allot 1514 cell 8 maxburst 20 avpkt 1000 weight 8Kbit bounded isolated
Quoted 1 line
tc filter add dev eth0 parent 1:1 protocol ip u32 match ip src
192.168.13.0/24 classid 1:6
Quoted 1 line
tc filter add dev eth0 parent 1:1 protocol ip u32 match ip dst
192.168.13.0/24 classid 1:6
Quoted 3 lines
tc class add dev eth0 parent 1:1 classid 1:7 cbq bandwidth 1Mbit rate
80Kbit allot 1514 cell 8 maxburst 20 avpkt 1000 weight 8Kbit bounded isolated
Quoted 1 line
tc filter add dev eth0 parent 1:1 protocol ip u32 match ip src
192.168.14.0/24 classid 1:7
Quoted 1 line
tc filter add dev eth0 parent 1:1 protocol ip u32 match ip dst
192.168.14.0/24 classid 1:7
Quoted 2 lines
tc class add dev eth0 parent 1:1 classid 1:8 cbq bandwidth 1Mbit rate
80Kbit allot 1514 cell 8 maxburst 20 avpkt 1000 weight 8Kbit bounded isolated
Quoted 1 line
tc filter add dev eth0 parent 1:1 protocol ip u32 match ip src
192.168.15.0/24 classid 1:8
Quoted 1 line
tc filter add dev eth0 parent 1:1 protocol ip u32 match ip dst
192.168.15.0/24 classid 1:8
Quoted 2 lines
tc class add dev eth0 parent 1:1 classid 1:9 cbq bandwidth 1Mbit rate
80Kbit allot 1514 cell 8 maxburst 20 avpkt 1000 weight 8Kbit bounded isolated
Quoted 1 line
tc filter add dev eth0 parent 1:1 protocol ip u32 match ip src
192.168.16.0/24 classid 1:9
Quoted 1 line
tc filter add dev eth0 parent 1:1 protocol ip u32 match ip dst
192.168.16.0/24 classid 1:9
Quoted 2 lines
tc class add dev eth0 parent 1:1 classid 1:10 cbq bandwidth 1Mbit rate
80Kbit allot 1514 cell 8 maxburst 20 avpkt 1000 weight 8Kbit bounded isolated
Quoted 1 line
tc filter add dev eth0 parent 1:1 protocol ip u32 match ip src
192.168.17.0/24 classid 1:10
Quoted 1 line
tc filter add dev eth0 parent 1:1 protocol ip u32 match ip dst
192.168.17.0/24 classid 1:10
Quoted 2 lines
tc class add dev eth0 parent 1:1 classid 1:11 cbq bandwidth 1Mbit rate
80Kbit allot 1514 cell 8 maxburst 20 avpkt 1000 weight 8Kbit bounded isolated
Quoted 1 line
tc filter add dev eth0 parent 1:1 protocol ip u32 match ip src
192.168.18.0/24 classid 1:11
Quoted 1 line
tc filter add dev eth0 parent 1:1 protocol ip u32 match ip dst
192.168.18.0/24 classid 1:11
Quoted 2 lines
tc class add dev eth0 parent 1:1 classid 1:12 cbq bandwidth 1Mbit rate
80Kbit allot 1514 cell 8 maxburst 20 avpkt 1000 weight 8Kbit bounded isolated
Quoted 1 line
tc filter add dev eth0 parent 1:1 protocol ip u32 match ip src
192.168.19.0/24 classid 1:12
Quoted 1 line
tc filter add dev eth0 parent 1:1 protocol ip u32 match ip dst
192.168.19.0/24 classid 1:12
Quoted 7 lines
######################################
#Setting up top 10 qdiscs
#for initial Paradyne packet classification
#######################################
tc class add dev eth0 parent 1:2 classid 1:13 cbq bandwidth 1Mbit rate
80Kbit allot 1514 cell 8 maxburst 20 avpkt 1000 weight 8Kbit bounded
Quoted 1 line
tc filter add dev eth0 parent 1:2 protocol ip u32 match ip src
192.168.20.0/24 classid 1:13
Quoted 1 line
tc filter add dev eth0 parent 1:2 protocol ip u32 match ip dst
192.168.20.0/24 classid 1:13
Quoted 2 lines
tc class add dev eth0 parent 1:2 classid 1:14 cbq bandwidth 1Mbit rate
80Kbit allot 1514 cell 8 maxburst 20 avpkt 1000 weight 8Kbit bounded
Quoted 1 line
tc filter add dev eth0 parent 1:2 protocol ip u32 match ip src
192.168.21.0/24 classid 1:14
Quoted 1 line
tc filter add dev eth0 parent 1:2 protocol ip u32 match ip dst
192.168.21.0/24 classid 1:14
Quoted 2 lines
tc class add dev eth0 parent 1:2 classid 1:15 cbq bandwidth 1Mbit rate
80Kbit allot 1514 cell 8 maxburst 20 avpkt 1000 weight 8Kbit bounded
Quoted 1 line
tc filter add dev eth0 parent 1:2 protocol ip u32 match ip src
192.168.22.0/24 classid 1:15
Quoted 1 line
tc filter add dev eth0 parent 1:2 protocol ip u32 match ip dst
192.168.22.0/24 classid 1:15
Quoted 2 lines
tc class add dev eth0 parent 1:2 classid 1:16 cbq bandwidth 1Mbit rate
80Kbit allot 1514 cell 8 maxburst 20 avpkt 1000 weight 8Kbit bounded
Quoted 1 line
tc filter add dev eth0 parent 1:2 protocol ip u32 match ip src
192.168.23.0/24 classid 1:16
Quoted 1 line
tc filter add dev eth0 parent 1:2 protocol ip u32 match ip dst
192.168.23.0/24 classid 1:16
Quoted 2 lines
tc class add dev eth0 parent 1:2 classid 1:17 cbq bandwidth 1Mbit rate
80Kbit allot 1514 cell 8 maxburst 20 avpkt 1000 weight 8Kbit bounded
Quoted 1 line
tc filter add dev eth0 parent 1:2 protocol ip u32 match ip src
192.168.24.0/24 classid 1:17
Quoted 1 line
tc filter add dev eth0 parent 1:2 protocol ip u32 match ip dst
192.168.24.0/24 classid 1:17
Quoted 2 lines
tc class add dev eth0 parent 1:2 classid 1:18 cbq bandwidth 1Mbit rate
80Kbit allot 1514 cell 8 maxburst 20 avpkt 1000 weight 8Kbit bounded
Quoted 1 line
tc filter add dev eth0 parent 1:2 protocol ip u32 match ip src
192.168.25.0/24 classid 1:18
Quoted 1 line
tc filter add dev eth0 parent 1:2 protocol ip u32 match ip dst
192.168.25.0/24 classid 1:18
Quoted 2 lines
tc class add dev eth0 parent 1:2 classid 1:19 cbq bandwidth 1Mbit rate
80Kbit allot 1514 cell 8 maxburst 20 avpkt 1000 weight 8Kbit bounded
Quoted 1 line
tc filter add dev eth0 parent 1:2 protocol ip u32 match ip src
192.168.26.0/24 classid 1:19
Quoted 1 line
tc filter add dev eth0 parent 1:2 protocol ip u32 match ip dst
192.168.26.0/24 classid 1:19
Quoted 2 lines
tc class add dev eth0 parent 1:2 classid 1:20 cbq bandwidth 1Mbit rate
80Kbit allot 1514 cell 8 maxburst 20 avpkt 1000 weight 8Kbit bounded
Quoted 1 line
tc filter add dev eth0 parent 1:2 protocol ip u32 match ip src
192.168.27.0/24 classid 1:20
Quoted 1 line
tc filter add dev eth0 parent 1:2 protocol ip u32 match ip dst
192.168.27.0/24 classid 1:20
Quoted 2 lines
tc class add dev eth0 parent 1:2 classid 1:21 cbq bandwidth 1Mbit rate
80Kbit allot 1514 cell 8 maxburst 20 avpkt 1000 weight 8Kbit bounded
Quoted 1 line
tc filter add dev eth0 parent 1:2 protocol ip u32 match ip src
192.168.28.0/24 classid 1:21
Quoted 1 line
tc filter add dev eth0 parent 1:2 protocol ip u32 match ip dst
192.168.28.0/24 classid 1:21
Quoted 2 lines
tc class add dev eth0 parent 1:2 classid 1:22 cbq bandwidth 1Mbit rate
80Kbit allot 1514 cell 8 maxburst 20 avpkt 1000 weight 8Kbit bounded
Quoted 1 line
tc filter add dev eth0 parent 1:2 protocol ip u32 match ip src
192.168.29.0/24 classid 1:22
Quoted 1 line
tc filter add dev eth0 parent 1:2 protocol ip u32 match ip dst
192.168.29.0/24 classid 1:22
Quoted 10 lines
#################################
# Start of Actual Filters
#################################--=_jive-4095-1055677798-0001-2--
Quoted 7 lines
--__--__--
Message: 4
From: Stef Coene <[email protected]>
Organization: None
To: [email protected], [email protected]
Subject: Re: [LARTC] Low latency on large uploads - almost done but not
quite.
Quoted 16 lines
Date: Sun, 15 Jun 2003 14:00:10 +0200
Quoted 13 lines · Thilo Schulz
Quoted 8 lines · you
Quoted 1 line
Here's still my script, if you are interested to look at it.
I'm interested and I have some remarks.
Your burst is too low. I understand you want a minimum burst, but you have to follow some rules. The best you can do is to remove the burst/cburst option so htb can calculate the minimum burst/cburst for you.
yes, sounds reasonable now that I spend a second thought about it.
Quoted 1 line
And don't you get quantum errors in your kernel log? That's because
your
Quoted 5 lines
Quoted 4 lines
Quoted 2 lines
quantum is too low for the classes. There is a long explanation for this, see www.docum.org on the faq page.
hmm .. quantum? I have never set quantum with any parameter, or have I?
No. Quantum is used for leaf classes to determine the amount of packets
they
Quoted 1 line
can send. It's calculates as rate / r2q. And r2q is 10 by default. You
can
Quoted 1 line
overrule r2q if you add the htb qdisc and you can overrule quantum if you
add
Quoted 3 lines
a htb class. Quantum must be > 1500 (the size of 1 packet) and < 60000.
Quoted 1 line
Quoted 1 line
You also use different prio's. This can be ok in most cases, except
if
Quoted 3 lines
Quoted 3 lines
Quoted 3 lines
you have a low prio class that's sending more data then the configured rate. If you do so, the latency can go up for that class. I (still) didn't test it myself, but you can find prove of it on the htb
homepage.
Quoted 1 line
Quoted 1 line
Quoted 1 line
The solution for this is to make sure you never put too much traffic
in a
Quoted 3 lines
Quoted 3 lines
Quoted 1 line
low prio class.
I have given plenty of bandwidth to the 1:10 class. Quake3 streams are
max.
Quoted 2 lines
Quoted 1 line
1500 bytes/s. And ssh does not use that much either.
Ok. As long as you are aware of the problem. You can also try to limit
the
Quoted 35 lines
amount of packets the filters with a policer. So there are never too much packets in a class.
Quoted 8 lines
Quoted 6 lines
Quoted 4 lines
# now make all qdiscs simple pfifo # small queues for minimum latency tc qdisc add dev $DEV parent 1:10 handle 20: pfifo limit 0 tc qdisc add dev $DEV parent 1:11 handle 30: pfifo limit 0Are you sure limit 0 is possible ????
Yes, at least the status command showed me, that the limit was set to 0.
Ok.
Stef
--
[email protected]
"Using Linux as bandwidth manager"
http://www.docum.org/
#lartc @ irc.oftc.net--__--__--
Message: 5
From: Stef Coene <[email protected]>
Organization: None
To: Trevor Warren <[email protected]>, lartc <[email protected]>
Subject: Re: [LARTC] herz the script that i have done.
Date: Sun, 15 Jun 2003 19:56:15 +0200
Cc: Trevor Warren <[email protected]>On Sunday 15 June 2003 01:46, Trevor Warren wrote:
Quoted 8 lines
Quoted 7 lines
Hello there,
Having made quite a lot of expensive mistakes i have finally clobbered
together a script for the users on my network.Have a look at it and please suggest as to how can i limit bandwidth to
each ip on this network to about 64Kbits.You specify bandwidth 1mbit. But that should be your real nic bandwidth.
So
Quoted 1 line
10mbit or 100mbit. If you want to share the same 1Mbit between some
classes,
Quoted 1 line
you have to add 1 bounded class with rate = 1mbit to the root qdisc and
add
Quoted 2 lines
the other classes to that class.
Remove the isolated class, it's not working and can even distubr your
setup.
Quoted 13 lines
Stef
--
[email protected]
"Using Linux as bandwidth manager"
http://www.docum.org/
#lartc @ irc.oftc.net--__--__--
Quoted 12 lines
Message: 6
From: Stef Coene <[email protected]>
Organization: None
To: [email protected], [email protected]
Subject: Re: [LARTC] htb problem
Date: Sun, 15 Jun 2003 20:14:52 +0200Quoted 4 lines · On Saturday 14 June 2003 23:46, [email protected] wrote:
Hey I hve the same problem. My packets are marked, my classes are OK my filters are set OK
and all packets are passing through the root class!!
I think that this is a big problem. A know 1 more person that has the
same
Quoted 2 lines
Quoted 1 line
problem!
Ok. I don't understand. I do all my test using iptables and fw filter.
This
Quoted 5 lines
works for me :
tc filter add dev eth0 parent 1: protocol ip handle 1 fw classid 1:100 iptables -A OUTPUT -t mangle -p tcp --dport 2000 -j MARK --set-mark 1This is on a simple pc. No router, no bridge, no firewall. It's only
used to
Quoted 15 lines
shape outgoing locally bandwidth.
Stef
--
[email protected]
"Using Linux as bandwidth manager"
http://www.docum.org/
#lartc @ irc.oftc.net--__--__--
Quoted 7 lines
_______________________________________________
LARTC mailing list
[email protected]
http://mailman.ds9a.nl/mailman/listinfo/lartcEnd of LARTC Digest
_______________________________________________
LARTC mailing list / [email protected]
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
--- yuxiao jia <[email protected]> wrote: > Hi
all
Quoted 11 lines
I am conducting the experiments comparing IP router forwarding delay and
MPLS LSR forwarding delay, it is obvious in theory MPLS in Core should be
faster than IP, but for small netork (only have several core routers),
result show it is not, this is why I want emulate a large IP routing table
in one core router.
Quoted 3 lines
can I do it and how ? right now I use static routing table (by using command
: ip route add network/mask via gateway)
Simple soultions would be write a script that expands lange ranges of IP address and pumps into the routing table.
Quoted 4 lines
thanks anyway
yuxiao
__________________________________________________
Yahoo! Plus - For a better Internet experience
http://uk.promotions.yahoo.com/yplus/yoffer.html
_______________________________________________
LARTC mailing list / [email protected]
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
Hi,
can you give me a example of this kind of script. Does it relate with routing protocol (OSPF..)?
thanks
yuxiao
Quoted 39 lines
Message: 2
Date: Mon, 16 Jun 2003 05:35:37 +0100 (BST)
From: =?iso-8859-1?q?deepak patwardhan?= <[email protected]>
Subject: Re: [LARTC] how to emulate large IP routing table
To: [email protected]--- yuxiao jia <[email protected]> wrote: > Hi
allQuoted 11 lines
I am conducting the experiments comparing IP router forwarding delay and
MPLS LSR forwarding delay, it is obvious in theory MPLS in Core should be
faster than IP, but for small netork (only have several core routers),
result show it is not, this is why I want emulate a large IP routing table
in one core router.Quoted 3 lines
can I do it and how ? right now I use static routing table (by using command
: ip route add network/mask via gateway)Simple soultions would be write a script that expands lange ranges of IP address and pumps into the routing table.
Quoted 4 lines
thanks anyway
yuxiao
__________________________________________________
Yahoo! Plus - For a better Internet experience
http://uk.promotions.yahoo.com/yplus/yoffer.html--__--__--
Quoted 7 lines
_______________________________________________
LARTC mailing list
[email protected]
http://mailman.ds9a.nl/mailman/listinfo/lartcEnd of LARTC Digest
_______________________________________________
LARTC mailing list / [email protected]
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
----- Original Message -----
From: "deepak patwardhan" <[email protected]>
To: "yuxiao jia" <[email protected]>
Sent: Tuesday, June 17, 2003 8:26 AM
Subject: Re: [LARTC] how to emulate large IP routing table
Quoted 97 lines
--- yuxiao jia <[email protected]> wrote: > Hi,
Quoted 4 lines
can you give me a example of this kind of script.
Does it relate with
routing protocol (OSPF..)?hmm.... I guess it relates to all. If you are using Gated or Zebra or cisco, juniper ... you can use redistribute route technique to pump in routes. But again there they don't have facilities to redistribute ranges of routes.
for eg.
<some command> 192.168.1.0/24 to 192.169.1.0/24 gateway a.b.c.d.So one needs to write huge config files to put in large state routes and redistribute them into the required protocols.
Quoted 1 line
Quoted 1 line
Quoted 1 line
: ip route add network/mask via gateway)
If you can wrap it in a script, which takes start IPaddr, End IPaddr and networkmask (comman mask to keep things simple) you can use the script to pump in large routes.
The script would have a for loop kinda algorithm Step 1. begin with the start IP/Mask,
Step 2. add route
Step 3. increment Ip, go to step4 untill you reach endIP.Once you have routes in kernel RT, try redistributing them from there to any protocol of your choice.
Am speaking very conceptual .... Hope you get my point. I haven't come across a readily available admin option to pump in large routes.
-Deepak
Quoted 57 lines
thanks
yuxiao
Quoted 4 lines
Message: 2
Date: Mon, 16 Jun 2003 05:35:37 +0100 (BST)
From: =?iso-8859-1?q?deepak patwardhan?> > <[email protected]>
Subject: Re: [LARTC] how to emulate large IProuting table
Quoted 3 lines
--- yuxiao jia <[email protected]> wrote: >
Hi
Quoted 3 lines
all
Quoted 2 lines
I am conducting the experiments comparing IP
router
Quoted 2 lines
Quoted 2 lines
forwarding delay and
MPLS LSR forwarding delay, it is obvious intheory
Quoted 4 lines
Quoted 4 lines
MPLS in Core should be
faster than IP, but for small netork (only have
several core routers),
result show it is not, this is why I wantemulate a
Quoted 4 lines
Quoted 4 lines
large IP routing table
in one core router.can I do it and how ? right now I use static
routing
Quoted 2 lines
Quoted 1 line
table (by using command
Simple soultions would be write a script that
expands
Quoted 1 line
lange ranges of IP address and pumps into the
routing
Quoted 22 lines
table.
Quoted 4 lines
thanks anyway
yuxiao
__________________________________________________
Yahoo! Plus - For a better Internet experience
http://uk.promotions.yahoo.com/yplus/yoffer.html--__--__--
_______________________________________________
LARTC mailing list
[email protected]
http://mailman.ds9a.nl/mailman/listinfo/lartcEnd of LARTC Digest
Quoted 8 lines
Quoted 3 lines
_______________________________________________
LARTC mailing list / [email protected]
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO:__________________________________________________
Yahoo! Plus - For a better Internet experience
http://uk.promotions.yahoo.com/yplus/yoffer.html
_______________________________________________
LARTC mailing list / [email protected]
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/