From: Don Bowman <db@donbowman.ca>
To: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: ipsec doesn't route TCP with 4.11 kernel
Date: Tue, 25 Apr 2017 21:08:28 -0400 [thread overview]
Message-ID: <CADJev78Cs0VBdagtfU-71pv3HHC5Vq41UXQee856aVbUqEqAYg@mail.gmail.com> (raw)
I'm not sure how to describe this.
4.11rc2 worked, after that, no.
My ipsec tunnel comes up ok. ICMP works. UDP works. But TCP, the
sender [which is the ipsec client] does not reach the destination.
Its not a routing rule issue (since ICMP/UDP work).
Its not a traffic selector just selecting TCP (I think) since ipsec
status shows just a subnet, no protocol.
Using tcpdump:
# iptables -t mangle -I PREROUTING -m policy --pol ipsec --dir in -j
NFLOG --nflog-group 5
# iptables -t mangle -I POSTROUTING -m policy --pol ipsec --dir out -j
NFLOG --nflog-group 5
# tcpdump -s 0 -n -i nflog:5
I see that it thinks it is sending the TCP packet, but the server end
does not receive.
Does anyone have any suggestion to try?
strongswan is 5.5.1 [on ubuntu 17.04]
kernel is 4.11.0-041100rc8-generic
My rightsubnet is
rightsubnet = 192.168.128.0/17,10.0.0.0/8
so no specific protocol selected, the result is:
CHILD_SA sv{1} established with SPIs c05f1b6c_i 0d58815a_o and TS
192.168.130.4/32 === 10.0.0.0/8 192.168.128.0/17
I tried changing charondebug net=3, but i'm not sure how to interpret
the output:
Apr 25 21:06:34 office charon: 04[NET] received packet: from
64.7.137.180[4500] to 172.16.0.8[4500] (80 bytes)
Apr 25 21:06:34 office charon: 04[ENC] parsed INFORMATIONAL request 4 [ ]
Apr 25 21:06:34 office charon: 04[ENC] generating INFORMATIONAL response 4 [ ]
Apr 25 21:06:34 office charon: 04[NET] sending packet: from
172.16.0.8[4500] to 64.7.137.180[4500] (80 bytes)
next reply other threads:[~2017-04-26 1:08 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-26 1:08 Don Bowman [this message]
2017-04-26 19:06 ` ipsec doesn't route TCP with 4.11 kernel Joseph Salisbury
2017-04-27 22:29 ` Don Bowman
2017-05-01 13:53 ` Joseph Salisbury
2017-04-27 5:01 ` Cong Wang
2017-04-27 8:42 ` Steffen Klassert
2017-04-27 22:15 ` Don Bowman
[not found] ` <CADJev7_=YEHmijGweqZvdATMQVuzwywEbBKweYvPurJfTEQRjQ@mail.gmail.com>
2017-04-28 7:13 ` Steffen Klassert
2017-04-28 16:46 ` Eric Dumazet
2017-05-03 8:21 ` Steffen Klassert
2017-04-30 0:39 ` Don Bowman
2017-05-03 8:14 ` Steffen Klassert
2017-05-16 19:05 ` Don Bowman
2017-05-19 10:03 ` 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=CADJev78Cs0VBdagtfU-71pv3HHC5Vq41UXQee856aVbUqEqAYg@mail.gmail.com \
--to=db@donbowman.ca \
--cc=linux-kernel@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).