Linux Netfilter discussions
 help / color / mirror / Atom feed
From: Michele Petrazzo - Unipex <michele.petrazzo@unipex.it>
To: netfilter@vger.kernel.org
Subject: Re: strange log on gateway inside []
Date: Fri, 30 Jul 2010 12:41:38 +0200	[thread overview]
Message-ID: <4C52AC62.3090609@unipex.it> (raw)
In-Reply-To: <4C513E0B.6040005@unipex.it>

Jan Engelhardt wrote:

Hi e thanks.

>>> And the last, have you also an rfc that explain why and where
>>> invalid come from?
> INVALID is a CT classification. RFC don't have much to do with that.

Pascal Hambourg wrote:
> ICMP port unreachable is not the natural reply to an unexpected TCP
> packet, so I guess it was generated by a REJECT target in the INPUT
> or FORWARD chain. If the original packet was in the INVALID state
> (or UNTRACKED if you used the NOTRACK target), then the ICMP error
> packet is in the INVALID state instead of RELATED.


A doubt.
Like said, INVALID is only a CT classification of my firewall. But,
since it's not a standard, how I can receive and reply (through my
FORWARD chain) to an INVALID packet? Who generate/classify it like
INVALID? My sender (I don't believe since it's not a standard) or my CT?

Thanks,
Michele

  parent reply	other threads:[~2010-07-30 10:41 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-29  8:38 strange log on gateway inside [] Michele Petrazzo - Unipex
2010-07-29  8:52 ` Jan Engelhardt
2010-07-29  9:18   ` Michele Petrazzo - Unipex
2010-07-29  9:49     ` Jan Engelhardt
2010-07-29  9:20 ` Pascal Hambourg
2010-07-30 10:41 ` Michele Petrazzo - Unipex [this message]
2010-07-30 10:48   ` Richard Horton
2010-07-30 11:12   ` Jan Engelhardt

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=4C52AC62.3090609@unipex.it \
    --to=michele.petrazzo@unipex.it \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox