All of lore.kernel.org
 help / color / mirror / Atom feed
From: Grant Taylor <gtaylor@riverviewtech.net>
To: Mail List - Netfilter <netfilter@vger.kernel.org>
Subject: Re: iptables u32 tests and user logging
Date: Mon, 21 Jul 2008 16:52:19 -0500	[thread overview]
Message-ID: <48850513.1040800@riverviewtech.net> (raw)
In-Reply-To: <76fdae320807211315v74557772jc9f8fefb83ac5b2b@mail.gmail.com>

On 07/21/08 15:15, Padmanabhan wrote:
> My interested 4 bytes can have value between all 0's to all FF's... 
> that's the reason that without matching it for a specific value,

*nod*  That makes things a little bit more difficult, but not impossible.

> I want to record those values.. without using any capturing programs 
> like tcpdump/wireshark.. u32 provided me flexibility to look for only 
> specific bytes...but the action which I would like perform is not 
> currently supported ....

Do you want to capture all packets in a connection or just one per 
connection?  If you want one per connection, you might want to match in 
the NAT table, which only sees the first packet in a connection.

> I have another story after recording these values :-)

*nod*

I'm always curious, probably to a fault.



Grant. . . .

      reply	other threads:[~2008-07-21 21:52 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <76fdae320807202313ma67d4c3l1921e41fa962a976@mail.gmail.com>
2008-07-21  6:15 ` iptables u32 tests and user logging Padmanabhan
2008-07-21  7:51   ` Jan Engelhardt
2008-07-21 15:40     ` Grant Taylor
2008-07-21 16:41       ` Padmanabhan
2008-07-21 16:49         ` Jan Engelhardt
2008-07-21 18:06           ` Padmanabhan
2008-07-21 18:49             ` Jan Engelhardt
2008-07-21 19:57             ` Grant Taylor
2008-07-21 20:15               ` Padmanabhan
2008-07-21 21:52                 ` Grant Taylor [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=48850513.1040800@riverviewtech.net \
    --to=gtaylor@riverviewtech.net \
    --cc=netfilter@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.