From: "Brian J. Murrell" <brian@interlinx.bc.ca>
To: netdev@vger.kernel.org
Subject: bonded active-backup ethernet-wifi drops packets
Date: Tue, 18 Jun 2019 14:57:44 -0400 [thread overview]
Message-ID: <0292e9eefb12f1b1e493f5af8ab78fa00744ed20.camel@interlinx.bc.ca> (raw)
[-- Attachment #1: Type: text/plain, Size: 2719 bytes --]
Hi.
I have an active-backup bonded connection on a 5.1.6 kernel where the
slaves are an Ethernet interface and a wifi interface. The goal is to
have network transparent (i.e. same and IP address on both interfaces)
interface which takes advantage of high-speed and low-latency when it
can be physically plugged into the wired network but have portability
when unplugged through WiFi.
It all works, mostly. :-/
I find that even when the primary interface, being the Ethernet
interface is plugged in and active, the bonded interface will drop
packets periodically.
If I down the bonded interface and plumb the Ethernet interface
directly, not as a slave of the bonded interface, no such packet
dropping occurs.
My measure of packet dropping, is by observing the output of "sudo ping
-f <ip_address>. In less than a few minutes even, on the bonded
interface, even with the Ethernet interface as the active slave, I will
have a long string of dots indicating pings that were never
replied. On the unbonded Ethernet interface, no dots, even when
measured over many days.
My bonding config:
$ cat /proc/net/bonding/bond0
Ethernet Channel Bonding Driver: v3.7.1 (April 27, 2011)
Bonding Mode: fault-tolerance (active-backup)
Primary Slave: enp0s31f6 (primary_reselect always)
Currently Active Slave: enp0s31f6
MII Status: up
MII Polling Interval (ms): 100
Up Delay (ms): 0
Down Delay (ms): 0
Slave Interface: enp0s31f6
MII Status: up
Speed: 1000 Mbps
Duplex: full
Link Failure Count: 0
Permanent HW addr: 0c:54:15:4a:b2:0d
Slave queue ID: 0
Slave Interface: wlp2s0
MII Status: up
Speed: Unknown
Duplex: Unknown
Link Failure Count: 1
Permanent HW addr: 0c:54:15:4a:b2:0d
Slave queue ID: 0
Current interface config/stats:
$ ifconfig bond0
bond0: flags=5187<UP,BROADCAST,RUNNING,MASTER,MULTICAST> mtu 1500
inet 10.75.22.245 netmask 255.255.255.0 broadcast 10.75.22.255
inet6 fe80::ee66:b8c9:d55:a28f prefixlen 64 scopeid 0x20<link>
inet6 2001:123:ab:123:d36d:5e5d:acc8:e9bc prefixlen 64 scopeid 0x0<global>
ether 0c:54:15:4a:b2:0d txqueuelen 1000 (Ethernet)
RX packets 1596206 bytes 165221404 (157.5 MiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 1590552 bytes 162689350 (155.1 MiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
Devices:
00:1f.6 Ethernet controller: Intel Corporation Ethernet Connection (2) I219-LM (rev 31)
02:00.0 Network controller: Intel Corporation Wireless 8265 / 8275 (rev 78)
Happy to provide any other useful information.
Any ideas why the dropping, only when using the bonded interface?
Cheers,
b.
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next reply other threads:[~2019-06-18 18:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-18 18:57 Brian J. Murrell [this message]
2019-06-21 12:30 ` bonded active-backup ethernet-wifi drops packets Brian J. Murrell
2019-07-04 15:12 ` Brian J. Murrell
2019-07-06 0:46 ` Jay Vosburgh
2019-07-12 12:51 ` Brian J. Murrell
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=0292e9eefb12f1b1e493f5af8ab78fa00744ed20.camel@interlinx.bc.ca \
--to=brian@interlinx.bc.ca \
--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).