Linux Netfilter discussions
 help / color / mirror / Atom feed
From: Mikhail Zotov <e-boogie@yandex.ru>
To: netfilter@lists.netfilter.org
Subject: Re: Possible reasons for INVALID packets ?
Date: Wed, 2 Mar 2005 19:35:25 +0300	[thread overview]
Message-ID: <200503021935.25498.e-boogie@yandex.ru> (raw)
In-Reply-To: <Pine.LNX.4.62.0503021025540.4201@L01.THNET>

On Wednesday 02 March 2005 12:26, Michael Tautschnig wrote:
> > Hello everybody,
>
> [...]
>
> You said that already, didn't you? See my answer at
>
> https://lists.netfilter.org/pipermail/netfilter/2005-February/058982.html

Thank you for the replies!  There was a pause in receiving messages
from the mailing list around Feb 28 and I didn't see any reply to my question.

>
>> IN= OUT=eth0 SRC=ROUTER DST=193.108.155.115 LEN=68 TOS=0x00 PREC=0xC0
>> TTL=64  ID=22467 PROTO=ICMP TYPE=11 CODE=0 [SRC=193.108.155.115
>> DST=A.LAN.HOST LEN=40 TOS=0x00 PREC=0x00 TTL=1 ID=40760 PROTO=ICMP TYPE=8
>> CODE=0 ID=20244 SEQ=45126 ]
>>
[...]
>
> Why would you consider these packets invalid - TYPE=11 is "time exceeded", 
> CODE=0 is "maximum lifetime of the datagram exceeded" - for whatever 
> reason those packets are generated ...

I have (roughly) the following rules in the script:

iptables -A OUTPUT -m state --state INVALID -j LOG \
--log-prefix "Fired invalid:"
iptables -A OUTPUT -m state --state INVALID -j DROP

These rules worked at the records I posted.


Regards,
Mikhail


  reply	other threads:[~2005-03-02 16:35 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-02  9:26 Possible reasons for INVALID packets ? Michael Tautschnig
2005-03-02 16:35 ` Mikhail Zotov [this message]
2005-03-02 16:58   ` Michael Tautschnig
  -- strict thread matches above, loose matches on Subject: below --
2005-03-02  8:35 Mikhail Zotov

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=200503021935.25498.e-boogie@yandex.ru \
    --to=e-boogie@yandex.ru \
    --cc=netfilter@lists.netfilter.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