From: Rodrigo Goya <rgoya@linuxcenter.com.mx>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] unshaping telnet
Date: Mon, 01 Oct 2001 15:18:16 +0000 [thread overview]
Message-ID: <marc-lartc-100195313309427@msgid-missing> (raw)
Hi,
My guess is you could mark packets with netfilter and use fwmark as the filter parameter,
you can mark packets not going to the linux box and then use that value as the handle
in a fwmark filter.
The netfilter rules would be something like:
iptables -t mangle -I PREROUTING -s 10.0.0.2/32 -d ! $LINUX_BOX -j MARK --set-mark 1
iptables -t mangle -I PREROUTING -s 10.0.0.3/32 -d ! $LINUX_BOX -j MARK --set-mark 2
Then the filter lines:
tc filter add dev eth1 protocol ip parent 1:0 prio 24 handle 1 fw classid 1:102
tc filter add dev eth1 protocol ip parent 1:0 prio 24 handle 2 fw classid 1:103
That'd be my first shot at it...
Cheers,
Rodrigo
On Sat, Sep 29, 2001 at 10:47:21AM +0100, Fabian Gervan wrote:
> Hello
>
> I have this setup, it work fine, but i can't telnet from any client to
> the linux server without trafic shaping:
> --cut--
> tc qdisc add dev eth1 root handle 1: cbq bandwidth 10Mbit avpkt 1000
> tc class add dev eth1 parent 1:0 classid 1:1 cbq bandwidth 100Mbit rate 100Mbit allot 1514 weigh
>
> tc class add dev eth1 parent 1:1 classid 1:100 cbq bandwidth 100Mbit rate 64kbit allot 1514 weight 6Kbit prio 5 maxburst 12 avpkt 1000 bounded
> tc class add dev eth1 parent 1:100 classid 1:102 cbq bandwidth 100Mbit rate 32kbit allot 1514 weight 3Kbit prio 5 maxburst 6 avpkt 1000 borrow
> tc class add dev eth1 parent 1:100 classid 1:103 cbq bandwidth 100Mbit rate 32kbit allot 1514 weight 3Kbit prio 5 maxburst 6 avpkt 1000 borrow
>
> tc qdisc add dev eth1 parent 1:102 sfq quantum 1514b perturb 15
> tc qdisc add dev eth1 parent 1:103 sfq quantum 1514b perturb 15
>
> tc filter add dev eth1 parent 1:0 protocol ip prio 25 u32 match ip dst
> 10.0.0.2/32 flowid 1:102
> tc filter add dev eth1 parent 1:0 protocol ip prio 25 u32 match ip dst
> 10.0.0.3/32 flowid 1:103
> --cut--
> server (10.0.0.1)
> 64kbit (bounded)
> 32kbit (borrow)- PC1 (10.0.0.2)
> 32kbit-(borrow)- PC2 (10.0.0.3)
>
> what I should add/change to make a telnet from pc1 or pc2 to server, without
> trafic shaping, or minimal shapping?
>
> Regards, Fabian.
>
>
>
> _______________________________________________
> LARTC mailing list / LARTC@mailman.ds9a.nl
> http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://ds9a.nl/2.4Routing/
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://ds9a.nl/2.4Routing/
next reply other threads:[~2001-10-01 15:18 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-01 15:18 Rodrigo Goya [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-09-29 9:47 [LARTC] unshaping telnet Fabian Gervan
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-100195313309427@msgid-missing \
--to=rgoya@linuxcenter.com.mx \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.