From: Stephen Hemminger <stephen@networkplumber.org>
To: Steffen Klassert <steffen.klassert@secunet.com>,
Herbert Xu <herbert@gondor.apana.org.au>
Cc: netdev@vger.kernel.org
Subject: Fw: [Bug 195969] New: ipsec icmp and udp works, tcp doesn't work
Date: Tue, 6 Jun 2017 12:14:39 -0700 [thread overview]
Message-ID: <20170606121439.6d24d7f0@xeon-e3> (raw)
Begin forwarded message:
Date: Sat, 03 Jun 2017 06:25:05 +0000
From: bugzilla-daemon@bugzilla.kernel.org
To: stephen@networkplumber.org
Subject: [Bug 195969] New: ipsec icmp and udp works, tcp doesn't work
https://bugzilla.kernel.org/show_bug.cgi?id=195969
Bug ID: 195969
Summary: ipsec icmp and udp works, tcp doesn't work
Product: Networking
Version: 2.5
Kernel Version: 4.11.3-1-ARCH
Hardware: All
OS: Linux
Tree: Mainline
Status: NEW
Severity: normal
Priority: P1
Component: Other
Assignee: stephen@networkplumber.org
Reporter: dev@djagoo.io
Regression: No
A few days ago I updated to 4.11.3-1-ARCH. After that my VPN access to our
corporate network was broken.
The connection is established and I can use UDP (i.e. DNS) and ICMP. All TCP
connections I tried (ssh, smb, http...) failed.
On the AUR page "MartinDiehl commented on 2017-05-25 19:57" the same error.
https://aur.archlinux.org/packages/strongswan/
And I found a bug report on redhat bugzilla:
https://bugzilla.redhat.com/show_bug.cgi?id=1458222
--
You are receiving this mail because:
You are the assignee for the bug.
next reply other threads:[~2017-06-06 19:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-06 19:14 Stephen Hemminger [this message]
2017-06-07 5:50 ` Fw: [Bug 195969] New: ipsec icmp and udp works, tcp doesn't work 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=20170606121439.6d24d7f0@xeon-e3 \
--to=stephen@networkplumber.org \
--cc=herbert@gondor.apana.org.au \
--cc=netdev@vger.kernel.org \
--cc=steffen.klassert@secunet.com \
/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