Linux Advanced Routing and Traffic Control list
 help / color / mirror / Atom feed
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 20:09:18 +0000	[thread overview]
Message-ID: <46E05E6E.5030300@vadtec.net> (raw)
In-Reply-To: <46D758ED.2030705@vadtec.net>

David Boreham wrote:
>
>>
>>
>> I do have one question though. On the egress shaping on eth1 (LAN 
>> interface), when using iptables I should do everything in the 
>> POSTROUTING chain correct? That way it gets routed to the proper LAN 
>> node and still gets shaped, correct? If thats the case, I can have a 
>> setup working in no time (I hope).
> Well now it's my turn to be confused ! What's the connection between
> iptables and your traffic shaping setup ? Are you marking packets for
> shaping, something like that ? If so I have no idea. My routing and
> shaping are completely separate and unrelated in any way (I use
> tc filter to classify packets).
>
>
>
iptables (I forget what version onward supports this) has the ability to 
classify packets that it routes via -j CLASSIFY --set-class X:Y. For all 
intents and purposes, this is the same as -j MARK --set-mark X. 
Basically, it allows a user to use iptables to do the actual 
classification of the packet. For an example, take a look at: 
http://lartc.org/howto/lartc.cookbook.fullnat.intro.html, 
http://www.stanford.edu/~fenn/linux/ (this is the tutorial I base my 
iptables and tc rules on)

I am not familiar enough with tc filter syntax to brave it yet. Hence my 
use of iptables to classify packets, which I think is much easier anyways.

I was simply asking whether I would classify the packets in PREROUTING, 
OUTPUT, or POSTROUTING. I assume OUTPUT or POSTROUTING will let me 
achieve my goals with respect to egress on eth1. Guess it's time to 
enter my dark age of tc+iptables. :P

Sorry if I confused you with my question. It's the only way I know how 
to traffic shape (so far).

Vadtec
_______________________________________________
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc

  parent reply	other threads:[~2007-09-06 20:09 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
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 [this message]
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=46E05E6E.5030300@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox