From: Patrick McHardy <kaber@trash.net>
To: Indan Zupancic <indan@nul.nu>
Cc: netfilter-devel@lists.netfilter.org, gandalf@wlug.westbo.se,
Yasuyuki KOZAKAI <yasuyuki.kozakai@toshiba.co.jp>
Subject: Re: 2.6.23-rc1: ipv4_get_l4proto: Frag of proto 17
Date: Thu, 26 Jul 2007 12:22:00 +0200 [thread overview]
Message-ID: <46A875C8.8030902@trash.net> (raw)
In-Reply-To: <47728.81.207.0.53.1185444598.squirrel@secure.samage.net>
Indan Zupancic wrote:
> On Thu, July 26, 2007 11:50, Patrick McHardy wrote:
>
>>iptables -t raw -I PREROUTING \
>> -m icmp --icmp-type destination-unreachable -j LOG
>>
>>should log the packets.
>
>
> So with this when I get a Frag of proto it should also log an ICMP error?
Exactly.
> Considering that the errors happened with a near exact 1 second interval
> and a 0.5s interval I think it's highly likely that it were retry packets to
> an unreachable host. But why is the proto UDP and not ICMP?
Its the inner packet that is parsed by nf_ct_get_tuplepr.
next prev parent reply other threads:[~2007-07-26 10:22 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-24 23:24 2.6.23-rc1: ipv4_get_l4proto: Frag of proto 17 Indan Zupancic
2007-07-25 15:19 ` Patrick McHardy
2007-07-25 16:12 ` Indan Zupancic
2007-07-25 16:17 ` Patrick McHardy
2007-07-25 17:02 ` Indan Zupancic
2007-07-25 17:13 ` Martin Josefsson
2007-07-25 17:41 ` Indan Zupancic
2007-07-26 1:27 ` Yasuyuki KOZAKAI
[not found] ` <200707260127.l6Q1RPP6019173@toshiba.co.jp>
2007-07-26 9:46 ` Indan Zupancic
2007-07-26 9:50 ` Patrick McHardy
2007-07-26 10:09 ` Indan Zupancic
2007-07-26 10:22 ` Patrick McHardy [this message]
2007-07-26 11:17 ` Indan Zupancic
2007-07-26 11:17 ` Patrick McHardy
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=46A875C8.8030902@trash.net \
--to=kaber@trash.net \
--cc=gandalf@wlug.westbo.se \
--cc=indan@nul.nu \
--cc=netfilter-devel@lists.netfilter.org \
--cc=yasuyuki.kozakai@toshiba.co.jp \
/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.