From: "Andrew Hall" <temp02@bluereef.com.au>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] marking packets problem: iptables
Date: Thu, 24 Jul 2003 05:43:01 +0000 [thread overview]
Message-ID: <marc-lartc-105902542410759@msgid-missing> (raw)
In-Reply-To: <marc-lartc-105902455010226@msgid-missing>
Depends what you mean by checking for marked packets. The netfilter "mark"
is only is a logical mark, in that the packet doesn't actually get changed
with a mark, so if you're expecting to see any changes with TCPDUMP or
similar you're not going to see any changes to the packet. The mark value is
only used by other hook listeners to recognise a particular flow, it's only
relevant within the netfilter and TC frameworks.
Hope this helps,
Andrew.
----- Original Message -----
From: "pawan gupta" <pawan_comp@rediffmail.com>
To: <lartc@mailman.ds9a.nl>
Sent: Thursday, July 24, 2003 3:27 PM
Subject: [LARTC] marking packets problem: iptables
> Hi all,
>
> I've set up iptables to mark all the packets coming from
> a particular host on my network. But I'm not sure whether my
> packets are getting marked or not. Does iptables provides any
> way to the packets which are getting marked (or any other way
> which makes sure that the packets are getting marked)?
>
>
> Please help
>
> thanks,
> Pawan
>
>
> ___________________________________________________
> Download the hottest & happening ringtones here!
> OR SMS: Top tone to 7333
> Click here now:
> http://sms.rediff.com/cgi-bin/ringtone/ringhome.pl
>
>
> _______________________________________________
> LARTC mailing list / LARTC@mailman.ds9a.nl
> http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
>
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
next prev parent reply other threads:[~2003-07-24 5:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-24 5:27 [LARTC] marking packets problem: iptables pawan gupta
2003-07-24 5:43 ` Andrew Hall [this message]
2003-07-24 12:29 ` hare ram
2003-07-28 17:46 ` Stef Coene
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=marc-lartc-105902542410759@msgid-missing \
--to=temp02@bluereef.com.au \
--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.