From: Marco Gaiarin <gaio@sv.lnf.it>
To: lartc@vger.kernel.org
Subject: Re: Are there any alternatives to IFB for downlink shaping?
Date: Mon, 16 Mar 2015 16:26:09 +0000 [thread overview]
Message-ID: <20150316162609.GU3861@sv.lnf.it> (raw)
In-Reply-To: <1426521620621.27129@farncombe.com>
Mandi! Nick Pelling
In chel di` si favelave...
> 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?
> 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. :-(
I've asked something similar some weeks ago, here.
I've also done some tests, and seems to me that, missing iptables
hooks, you have also no NAT, so if you have to match dest IP you cannot
in IFB, because dest ip is everytime the public ip. ;(
--
dott. Marco Gaiarin GNUPG Key ID: 240A3D66
Associazione ``La Nostra Famiglia'' http://www.sv.lnf.it/
Polo FVG - Via della Bontà, 7 - 33078 - San Vito al Tagliamento (PN)
marco.gaiarin(at)lanostrafamiglia.it t +39-0434-842711 f +39-0434-842797
Dona il 5 PER MILLE a LA NOSTRA FAMIGLIA!
http://www.lanostrafamiglia.it/25/index.php/component/k2/item/123
(cf 00307430132, categoria ONLUS oppure RICERCA SANITARIA)
next prev parent reply other threads:[~2015-03-16 16:26 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 [this message]
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=20150316162609.GU3861@sv.lnf.it \
--to=gaio@sv.lnf.it \
--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.