All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andy Furniss <adf.lists@gmail.com>
To: lartc@vger.kernel.org
Subject: Re: reroute icmp traffic from one interface to another
Date: Wed, 01 Jun 2016 16:45:14 +0000	[thread overview]
Message-ID: <574F111A.2060106@gmail.com> (raw)
In-Reply-To: <20160531171329.Horde.SLfG6i6j_hmWsfb5FjpBZwP@ermis.noc.duth.gr>

Ηλια Χατζηστυλη wrote:
> the code used to rerout traffic and limmit bandwith is :

>          tc qdisc add dev $IF root handle 1:0 htb default 30
>          echo "class 10(home) 20(guest)"
>          tc class add dev $IF parent 1: classid 1:1 htb rate 2mbit
>          tc class add dev $IF parent 1:1 classid 1:10 htb rate 2mbit
> --home user bandwidth
>      tc class add dev $IF parent 1:1 classid 1:20 htb rate
> 200kbit--guest user bw
>          tc class add dev $IF parent 1:1 classid 1:30 htb rate 2mbit
>      tc qdisc add dev $IF parent 1:10 handle 100: bfifo limit 75000
>      tc qdisc add dev $IF parent 1:20 handle 200: bfifo limit 75000
>
> #----
> #---QDISC gia to download
>
>      tc qdisc add dev $IF handle ffff: ingress
>      tc filter add dev $IF parent ffff: protocol ip prio 50 u32 match ip
> src 0.0.0.0/0 police rate 30mbit burst 30mbit drop flowid :1

Policers are not very good in practice, consider using ifb.
Either way policing/shaping ingress traffic is not totally controllable
like it is on egress.

> I send this nping command with the --data-length extension so that the
> ping will not be treated as a single bit.

If htb/bfifo is not backlogged then the packet will get sent instantly
whatever length it is.



      parent reply	other threads:[~2016-06-01 16:45 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-31 14:13 reroute icmp traffic from one interface to another Ηλια Χατζηστυλη
2016-05-31 15:40 ` Andy Furniss
2016-05-31 23:40 ` Ηλια Χατζηστυλη
2016-06-01 16:45 ` Andy Furniss [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=574F111A.2060106@gmail.com \
    --to=adf.lists@gmail.com \
    --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.