All of lore.kernel.org
 help / color / mirror / Atom feed
From: Edwin Whitelaw <Edwin.Whitelaw@nrvunwired.net>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] iptables CLASSIFY vs fwmark?
Date: Sat, 06 May 2006 11:58:07 +0000	[thread overview]
Message-ID: <445C8F4F.2040103@nrvunwired.net> (raw)
In-Reply-To: <445BD9FE.7000400@nrvunwired.net>

My observation also, but one example shows using fwmark in the 
PREROUTING chain while CLASSIFY can be used in POSTROUTING only 
(correct?).  My experience with tc at this point is limited but 
sometimes added flexibility is useful, even if it's a little more effort. 

Edwin

Denis Ovsienko wrote:
>> Could someone comment on the benefits of using CLASSIFY vs fwmark (or 
>> vice versa) in iptables?
>>     
> One benefit I see is that one avoids extra filters, this can be useful
> with lots of classes.
>
>   

-- 
<=+=+=+=+=+=+=+=+=+=+=+=+=+=+=>
Edwin Whitelaw, P.E.
New River Valley Unwired, LLC
2200 Lonesome Dove Dr
Christiansburg, VA 24073
540-239-0318

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

  parent reply	other threads:[~2006-05-06 11:58 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-05-05 23:04 [LARTC] iptables CLASSIFY vs fwmark? Edwin Whitelaw
2006-05-06  7:05 ` Denis Ovsienko
2006-05-06 11:58 ` Edwin Whitelaw [this message]
2006-05-07 14:42 ` William Bohannan

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=445C8F4F.2040103@nrvunwired.net \
    --to=edwin.whitelaw@nrvunwired.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.