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


Hi everyone,

I'm trying to configure (OK, 'hack') a Linux-based Broadcom wireless gateway to prioritize the traffic between two groups of interfaces, e.g. where home traffic gets rate 80% ceil 95% prio 1, and where guest traffic (i.e. wl1) gets rate 15% ceil 60% prio 2.

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.

Specifically, I've put in a lot of work trying to get IFB working, but it seems to be stitched too early in the packet processing chain to be any use for shaping a WAN interface's downlink traffic. Basically, my downlink bandwidth stats stay resolutely at zero bytes / zero  packets, whatever I try. :-(

Are there any higher-level (i.e. device-level) configuration alternatives to using IFB? It seems obvious to me that if I could insert any (fake, forwarding-only) device at all between the WAN port and the rest of the system, then I would be able to use normal  tc egress shaping on the traffic going through it.

It strikes me that this would be something a tap device could do, for example: but I've never seen anyone discuss this anywhere on the web.

Anyway, I'm currently using eth3 for the WAN, so my (working) uplink traffic shaping looks like this:-

eth0-2 / wl0 ---> br0 --->  \
                                                     +---> [tc egress] eth3 --> [Internet]
wl1                                  --->  /

For the downlink, however, I'm wondering if there might be a fake device I could configure in that serves only to forward packets. tap0?

eth0-2 / wl0 <--- br0 <---  \
                                                     + <--- fakedevice [tc egress] <--- eth3 <--- [Internet]
wl1                                   <---  /

I was hoping (of course) that IFB would be able to do this for me, but it doesn't seem to want to play nicely. Am I missing something? All suggestions and comments very much appreciated! :-)

Thanks very much, Nick

             reply	other threads:[~2015-03-16 16:00 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-16 16:00 Nick Pelling [this message]
2015-03-16 16:26 ` Are there any alternatives to IFB for downlink shaping? 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
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=1426521620621.27129@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.