Linux Netfilter discussions
 help / color / mirror / Atom feed
From: Casey Scott <casey@phantombsd.org>
To: Matt Zagrabelny <mzagrabe@d.umn.edu>
Cc: Rob Sterenborg <rob@sterenborg.info>, netfilter@vger.kernel.org
Subject: Re: verifying set-mark
Date: Sat, 23 Feb 2008 10:14:21 -0800 (PST)	[thread overview]
Message-ID: <25498998.61203790461346.JavaMail.root@tomcat.phantombsd.org> (raw)
In-Reply-To: <1203720563.27608.55.camel@grateful.d.umn.edu>

Is there a way with tcpdump to verify that the marks are actually
getting set though?

Casey

----- "Matt Zagrabelny" <mzagrabe@d.umn.edu> wrote:

> On Fri, 2008-02-22 at 14:40 -0800, Casey Scott wrote:
> > Ultimately, I am trying to mark packets for a tc filter. Should I
> > not be using the iptables set-mark to do that?
> 
> I think set-mark is fine for that.
> 
> I suggest marking some packets in the prerouting chain and then
> logging
> them in input chain. Something like the following:
> 
> $iptables --table mangle --append PREROUTING
> --in-interface $in_interface
> --destination $host --jump MARK --set-mark $mark_integer
> 
> $iptables --table filter --append INPUT
> --in-interface $in_interface
> --match mark --mark $mark_integer --jump LOG
> 
> > 

  reply	other threads:[~2008-02-23 18:14 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-22 20:14 verifying set-mark Casey Scott
2008-02-22 20:44 ` Rob Sterenborg
2008-02-22 20:53   ` Casey Scott
2008-02-22 21:44     ` Matt Zagrabelny
2008-02-22 22:40       ` Casey Scott
2008-02-22 22:49         ` Matt Zagrabelny
2008-02-23 18:14           ` Casey Scott [this message]
2008-02-23 19:23             ` Rob Sterenborg
     [not found] <15675295.211203870881109.JavaMail.root@tomcat.phantombsd.org>
2008-02-24 16:36 ` Casey Scott
2008-02-24 17:30   ` Martijn Lievaart
2008-02-24 17:34     ` Casey Scott

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=25498998.61203790461346.JavaMail.root@tomcat.phantombsd.org \
    --to=casey@phantombsd.org \
    --cc=mzagrabe@d.umn.edu \
    --cc=netfilter@vger.kernel.org \
    --cc=rob@sterenborg.info \
    /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