From: Vadtec <vadtec@vadtec.net>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Question about how TC enforces bandwidth limiting
Date: Thu, 06 Sep 2007 04:08:33 +0000 [thread overview]
Message-ID: <46DF7D41.40907@vadtec.net> (raw)
In-Reply-To: <46D758ED.2030705@vadtec.net>
Ok, I'm almost to tearing my hair out now...
I am trying to do more proper ingress policing as Martin has said I do.
But every tutorial or example I have seen on traffic shaping with tc
says very little (if anything at all) about ingress policing. I have
tried a few methods to get this to work including: adding qdiscs to it
(failed), adding filters that would give it a FWMARK to classify with
(failed), adding HTBs to it (failed). I finally gave up and just routed
all the ingress to the same root as I have no idea what the heck I'm doing.
Can someone please provide me with an example of how to split ingress
policing so that I can achieve what Martin is saying I need to achieve?
Vadtec
_______________________________________________
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc
next prev parent reply other threads:[~2007-09-06 4:08 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-30 23:55 [LARTC] Question about how TC enforces bandwidth limiting Vadtec
2007-09-03 12:05 ` Vadtec
2007-09-03 18:43 ` Martin A. Brown
2007-09-03 20:15 ` Vadtec
2007-09-04 2:09 ` Martin A. Brown
2007-09-04 12:27 ` Vadtec
2007-09-04 13:02 ` Martin A. Brown
2007-09-04 13:39 ` Vadtec
2007-09-06 1:13 ` Vadtec
2007-09-06 2:47 ` Martin A. Brown
2007-09-06 3:04 ` Vadtec
2007-09-06 4:08 ` Vadtec [this message]
2007-09-06 17:43 ` Vadtec
2007-09-06 17:57 ` David Boreham
2007-09-06 18:43 ` Vadtec
2007-09-06 19:32 ` David Boreham
2007-09-06 20:09 ` Vadtec
2007-09-06 20:09 ` Andy Furniss
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=46DF7D41.40907@vadtec.net \
--to=vadtec@vadtec.net \
--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.