From: Steffen Klassert <steffen.klassert@secunet.com>
To: Martin Pelikan <martin.pelikan@gmail.com>
Cc: <netdev@vger.kernel.org>
Subject: Re: (patch needs review) NULL dereference in xfrm_output with NAT
Date: Mon, 7 Apr 2014 12:55:59 +0200 [thread overview]
Message-ID: <20140407105559.GO32371@secunet.com> (raw)
In-Reply-To: <20140404122917.GM5945@methuselah>
On Fri, Apr 04, 2014 at 02:29:17PM +0200, Martin Pelikan wrote:
>
> Your patch avoids the crash the same way as mine, but doesn't fix my related
> problem: I have two flows through that IPv6 endpoint: IPv6 default gw tunnel
> + IPv4 tunnel between two private networks. But only one of them works at a
> time, and it is the one which was set up first.
> The other endpoint is OpenBSD with iked(8) and I can see the replies going
> into enc0 there, ESP packets arriving into this Linux box at enp4s6, but the
> traffic isn't being decapsulated and sent further away on br0.
> If I disable the working tunnel (v6 for example), the other one (v4) starts
> working immediately, so it's probably not caused by bad strongSwan config.
>
> Do you think these bugs might be related? Any ideas how to proceed without
> spending days on it?
A good starting point for further debugging would be to find out
where the packets are dropped. xfrm increases a counter whenever
a packet is dropped in the xfrm layer. You can find these counters
in /proc/net/xfrm_stat.
next prev parent reply other threads:[~2014-04-07 10:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-02 10:37 (patch needs review) NULL dereference in xfrm_output with NAT Martin Pelikan
2014-04-04 9:02 ` Steffen Klassert
2014-04-04 12:29 ` Martin Pelikan
2014-04-07 10:55 ` Steffen Klassert [this message]
2014-04-08 7:31 ` Steffen Klassert
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=20140407105559.GO32371@secunet.com \
--to=steffen.klassert@secunet.com \
--cc=martin.pelikan@gmail.com \
--cc=netdev@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;
as well as URLs for NNTP newsgroup(s).