From: "David S. Miller" <davem@redhat.com>
To: Harald Welte <laforge@netfilter.org>
Cc: linux-kernel@vger.kernel.org, netdev@oss.sgi.com,
netfilter-devel@lists.netfilter.org
Subject: Re: [PATCH 2.6] ip6t_LOG and packets with hop-by-hop options
Date: Tue, 6 Jul 2004 13:55:19 -0700 [thread overview]
Message-ID: <20040706135519.028b22b5.davem@redhat.com> (raw)
In-Reply-To: <20040706160109.GO32707@sunbeam2>
On Tue, 6 Jul 2004 18:01:09 +0200
Harald Welte <laforge@netfilter.org> wrote:
> On Tue, Jul 06, 2004 at 05:09:18PM +0200, Marcel Sebek wrote:
> > Packet with IPPROTO_HOPOPTS extended header isn't logged properly by
> > ip6t_LOG.c. It only prints PROTO=0 and nothing more, because
> > IPPROTO_HOPOPTS=0 and in this file 0 is used to indicate last header.
> > This patch fix it by using IPPROTO_NONE to indicate last header.
>
> looks fine to me. Dave, can you please include this to your tree?
> Thanks.
Applied, thanks everyone.
prev parent reply other threads:[~2004-07-06 20:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-06 15:09 [PATCH 2.6] ip6t_LOG and packets with hop-by-hop options Marcel Sebek
2004-07-06 16:01 ` Harald Welte
2004-07-06 20:55 ` David S. Miller [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=20040706135519.028b22b5.davem@redhat.com \
--to=davem@redhat.com \
--cc=laforge@netfilter.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@oss.sgi.com \
--cc=netfilter-devel@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 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.