From: "Daniel Ditu" <dditu@fx.ro>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] isolated works fine for me
Date: Sat, 25 Jan 2003 10:36:38 +0000 [thread overview]
Message-ID: <marc-lartc-104349108908011@msgid-missing> (raw)
In-Reply-To: <marc-lartc-104343487127786@msgid-missing>
> Can you post your script so I can take a look at it ?
>
> Stef
>
//mark the packets in iptables .. the ip 192.168.1.111 will have an isolated
band of 5k enough to play cs
iptables -t mangle -F
iptables -t mangle -A FORWARD -s 0/0 -d 0/0 -j MARK --set-mark 100
iptables -t mangle -A FORWARD -s ! 192.168.1.0/24 -d 192.168.1.111 -j
MARK --set-mark 111
iptables -t mangle -A FORWARD -d ! 192.168.1.0/24 -s 192.168.1.111 -j
MARK --set-mark 111
tc qdisc add dev eth0 root handle 10: cbq bandwidth 10Mbit avpkt 1000 allot
1514
#total traffic.. 200/8%K..
tc class add dev eth0 parent 10:0 classid 10:1 cbq rate 200kbit avpkt 1000
prio 5
tc class add dev eth0 parent 10:1 classid 10:10 cbq rate 40kbit allot 1514
prio 5 isolated
tc class add dev eth0 parent 10:1 classid 10:20 cbq rate 160kbit allot 1514
prio 4 bounded
# filtre care clasifica traficu handle 1 e traficul de download
tc filter add dev eth0 parent 10:0 protocol ip prio 5 handle 111 fw flowid
10:10
tc filter add dev eth0 parent 10:0 protocol ip prio 4 handle 100 fw flowid
10:20
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
prev parent reply other threads:[~2003-01-25 10:36 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-24 18:57 [LARTC] isolated works fine for me Daniel Ditu
2003-01-24 19:24 ` Stef Coene
2003-01-24 20:21 ` Sebastian 'spax' Pape
2003-01-24 20:31 ` Stef Coene
2003-01-24 20:41 ` Sebastian 'spax' Pape
2003-01-25 10:36 ` Daniel Ditu [this message]
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=marc-lartc-104349108908011@msgid-missing \
--to=dditu@fx.ro \
--cc=lartc@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