Linux Netfilter discussions
 help / color / mirror / Atom feed
From: Andrew Beverley <andy@andybev.com>
To: Vishal Jumar <vishaljumar@live.com>
Cc: netfilter@vger.kernel.org
Subject: Re: Help with INVALID packets rule. Best way to see the actual packet isloating the rest?‏
Date: Thu, 12 Apr 2012 20:48:32 +0100	[thread overview]
Message-ID: <1334260112.1603.1.camel@andy-laptop> (raw)
In-Reply-To: <BLU155-W39963085CD8F1B244A4730CB3A0@phx.gbl>

On Thu, 2012-04-12 at 16:25 +0000, Vishal Jumar wrote:
> iptables -A INPUT -m state --state INVALID -j LOG --log-prefix "
> Invalid NOT DROPPED"
...
> How can I view the packet that this rule match is originating?

You may be able to use ulogd as the target instead. The following
website might help; it describes capturing strange packets and examining
them later with wireshark.

http://rm-rf.ca/blog/fun-iptables-ulogd-and-wireshark

Andy



      reply	other threads:[~2012-04-12 19:48 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-12 16:25 Help with INVALID packets rule. Best way to see the actual packet isloating the rest?‏ Vishal Jumar
2012-04-12 19:48 ` Andrew Beverley [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=1334260112.1603.1.camel@andy-laptop \
    --to=andy@andybev.com \
    --cc=netfilter@vger.kernel.org \
    --cc=vishaljumar@live.com \
    /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