From: Stephen Hemminger <stephen@networkplumber.org>
To: netdev@vger.kernel.org
Subject: Fw: [Bug 203743] New: Networking goes down when running Docker and receiving fragmented IPv4 packets
Date: Tue, 28 May 2019 09:16:42 -0700 [thread overview]
Message-ID: <20190528091642.6be8af3e@hermes.lan> (raw)
Begin forwarded message:
Date: Tue, 28 May 2019 15:49:52 +0000
From: bugzilla-daemon@bugzilla.kernel.org
To: stephen@networkplumber.org
Subject: [Bug 203743] New: Networking goes down when running Docker and receiving fragmented IPv4 packets
https://bugzilla.kernel.org/show_bug.cgi?id=203743
Bug ID: 203743
Summary: Networking goes down when running Docker and receiving
fragmented IPv4 packets
Product: Networking
Version: 2.5
Kernel Version: 4.15.0-1032-aws
Hardware: x86-64
OS: Linux
Tree: Mainline
Status: NEW
Severity: normal
Priority: P1
Component: IPV4
Assignee: stephen@networkplumber.org
Reporter: camden.fullmer@boxcast.com
Regression: No
We are experiencing an issue where our EC2 instances fail instance status
checks and completely lose networking because of cellular UDP traffic going to
an instance.
It seems that when sending UDP traffic using T-Mobile cellular the packets are
fragmented and causes the system to completely lose networking because of this.
I have attached the source code for the iOS app that can reliabily reproduce
this issue as well as the server code to receive the traffic. The packet
capture of the traffic is attached as well. Also important to note that the
system only drops networking when Docker is running, but the fragmentation also
happens no matter if Docker is installed or not.
It's also worth pointing out that when sending the traffic over Cellular to a
local network at our office that the traffic is not fragmented. This makes me
think that there is an issue with networking between T-Mobile and AWS.
Base AWS AMI: ami-0a313d6098716f372
Instance Types: g3.4xlarge or c5.2xlarge
Docker GitHub Issue: https://github.com/docker/for-linux/issues/672
iOS app: https://github.com/docker/for-linux/files/3192116/LockUpDemo.zip
Server app:https://github.com/docker/for-linux/files/3192118/main.c.zip
tcpdump capture:
https://github.com/docker/for-linux/files/3192155/capture.pcap.zip
--
You are receiving this mail because:
You are the assignee for the bug.
reply other threads:[~2019-05-28 16:16 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20190528091642.6be8af3e@hermes.lan \
--to=stephen@networkplumber.org \
--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).