All of lore.kernel.org
 help / color / mirror / Atom feed
From: Spyou spyou@club-internet.fr
To: lartc@vger.kernel.org
Subject: [LARTC] Incoming trafic shaping (depending on src IP)
Date: Tue, 20 Feb 2001 10:47:25 +0000	[thread overview]
Message-ID: <marc-lartc-98373940417037@msgid-missing> (raw)

<PRE>
Hi there,


i'm trying to shape incoming trafic on my linux box.

I want it to depend on the source IP adress of the packets (in fact, i got 
a VPN on an ADSL link and wanted to get at least/max 64Kbit/s for the VPN)

So i tried this :

tc qdisc add dev ppp0 root handle 1:0 cbq bandwidth 512Kbit avpkt 1000 cell 8
tc class add dev ppp0 parent 1:0 classid 1:1 cbq bandwidth 512Kbit rate 
512Kbit weight 50Kbit prio 8 allot 1514 cell 8 maxburst 20 avpkt 1000
tc class add dev ppp0 parent 1:1 classid 1:10 cbq bandwidth 512Kbit rate 
64Kbit weight 6Kbit prio 8 allot 1514 cell 8 maxburst 20 avpkt 1000 bounded 
isolated
tc qdisc add dev ppp0 parent 1:10 tbf rate 64Kbit buffer 10Kb/8 limit 15Kb 
mtu 1500
tc filter add dev ppp0 parent 1:0 protocol ip prio 100 u32 match ip src 
&lt;the SRC IP of my VPN&gt; flowid 1:10

Okay, so, with this, packets comming trought ppp0 and from &lt;the SRC IP of 
my VPN&gt; should be shaped at 64Kbit/s, right ?

Where's my error ? Is there something more simple (eg. with iptables and 
packet marking ?)


thx for help :)
____________________________________
  'Spyou' - www.spyou.org - <A HREF="mailto:root@spyou.org">root@spyou.org</A>
     #gtr / ircnet.grolier.net - UIN : 6871374

We've done so much, for so long, with so little
We're now qualified to do anything with nothing.



</PRE>

             reply	other threads:[~2001-02-20 10:47 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-02-20 10:47 Spyou [this message]
2001-02-20 13:40 ` [LARTC] Incoming trafic shaping (depending on src IP) bert
2001-02-23  3:07 ` Oki

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-98373940417037@msgid-missing \
    --to=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.