From: Stef Coene <stef.coene@docum.org>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] marking packets problem: iptables
Date: Mon, 28 Jul 2003 17:46:43 +0000 [thread overview]
Message-ID: <marc-lartc-105941471713933@msgid-missing> (raw)
In-Reply-To: <marc-lartc-105902455010226@msgid-missing>
On Thursday 24 July 2003 07:27, pawan gupta wrote:
> 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)?
You can check the iptables counters to see if the iptables rules are matched.
Stef
--
stef.coene@docum.org
"Using Linux as bandwidth manager"
http://www.docum.org/
#lartc @ irc.oftc.net
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
prev parent reply other threads:[~2003-07-28 17:46 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
2003-07-24 12:29 ` hare ram
2003-07-28 17:46 ` Stef Coene [this message]
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-105941471713933@msgid-missing \
--to=stef.coene@docum.org \
--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.