From: Steffen Klassert <steffen.klassert@secunet.com>
To: Alexander Wetzel <alexander.wetzel@web.de>
Cc: <netdev@vger.kernel.org>, <roque@di.fc.ul.p>,
<kuznet@ms2.inr.ac.ru>, <r.venning@telstra.com>,
<nate@thebog.net>
Subject: Re: ipip6 - integer underrun when handlince icmpv4 unreachable messages
Date: Tue, 9 Dec 2014 14:28:41 +0100 [thread overview]
Message-ID: <20141209132841.GL6390@secunet.com> (raw)
In-Reply-To: <54808A5C.1050205@web.de>
On Thu, Dec 04, 2014 at 05:22:52PM +0100, Alexander Wetzel wrote:
> Hello,
>
> The patch works for me, thank you very much.
>
> Rejecting the ipv4 tunel packets with icmp unreachable is producing the
> expected "Destination unreachable: Address unreachable" messages for the
> inside ipv6 client and everything works as expected. Without the call in
> sit.c to skb_reset_transport_header.
>
> I'll continue to use the patch on my ipv6 tunnel router but I'm sure it
> works as intended.
>
>
> On 04.12.2014 09:56, Steffen Klassert wrote:
> >
> > I think the easiest is to fix it in _decode_session6().
> > Could you please try the patch below?
> >
> > Subject: [PATCH] xfrm6: Fix transport header offset in _decode_session6.
> >
> > skb->transport_header might not be valid when we do a reverse
> > decode because the ipv6 tunnel error handlers don't update it
> > to the inner transport header. This leads to a wrong offset
> > calculation and to wrong layer 4 informations. We fix this
> > by using the size of the ipv6 header as the first offset.
> >
> > Signed-off-by: Steffen Klassert <steffen.klassert@secunet.com>
Thanks for testing, I've applied this to the ipsec tree now.
prev parent reply other threads:[~2014-12-09 13:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-17 21:52 ipip6 - integer underrun when handlince icmpv4 unreachable messages Alexander Wetzel
2014-12-04 8:56 ` Steffen Klassert
2014-12-04 16:22 ` Alexander Wetzel
2014-12-09 13:28 ` Steffen Klassert [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=20141209132841.GL6390@secunet.com \
--to=steffen.klassert@secunet.com \
--cc=alexander.wetzel@web.de \
--cc=kuznet@ms2.inr.ac.ru \
--cc=nate@thebog.net \
--cc=netdev@vger.kernel.org \
--cc=r.venning@telstra.com \
--cc=roque@di.fc.ul.p \
/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.