All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nick Pelling <nick.pelling@farncombe.com>
To: lartc@vger.kernel.org
Subject: Re: Are there any alternatives to IFB for downlink shaping?
Date: Tue, 17 Mar 2015 09:47:44 +0000	[thread overview]
Message-ID: <1426585664345.35294@farncombe.com> (raw)
In-Reply-To: <1426521620621.27129@farncombe.com>

Hi Marco,

"action skbedit" is a simple tc action that edits skb packets in fairly straightforward ways, e.g. "action skbedit mark 1" edits the filtered packet to have mark = 1.

Generally, I prefer "tc filter" commands to "iptables -A" commands, mainly because the former are bound to an individual interface rather than to every netfilter chain call ever. :-)

________________________________________
From: lartc-owner@vger.kernel.org <lartc-owner@vger.kernel.org> on behalf of Marco Gaiarin <gaio@sv.lnf.it>
Sent: 16 March 2015 16:26
To: lartc@vger.kernel.org
Subject: Re: Are there any alternatives to IFB for downlink shaping?

> I now have tc doing this beautifully on the uplink traffic (I use 'action skbedit mark 1', why is this trick mentioned hardly anywhere?): but, like almost every other first time poster here :-) , I'm having no luck at all getting this working for downlink traffic.

?! Looking on google form 'skbedit' lead me to multiqueue management:

        https://www.kernel.org/doc/Documentation/networking/multiqueue.txt

and seems not related... can you explain better?

  parent reply	other threads:[~2015-03-17  9:47 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-16 16:00 Are there any alternatives to IFB for downlink shaping? Nick Pelling
2015-03-16 16:26 ` Marco Gaiarin
2015-03-16 16:58 ` Mike Schmidt
2015-03-16 16:59 ` Andrew Beverley
2015-03-16 21:58 ` Andy Furniss
2015-03-17  9:47 ` Nick Pelling [this message]
2015-03-17 11:36 ` Nick Pelling

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=1426585664345.35294@farncombe.com \
    --to=nick.pelling@farncombe.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.