Bug 202235
Summary: | regression: physical to VETH (LXC) network bridge after updating to 4.20.0 | ||
---|---|---|---|
Product: | Networking | Reporter: | Michael Evans (mjevans1983) |
Component: | Other | Assignee: | Stephen Hemminger (stephen) |
Status: | NEW --- | ||
Severity: | blocking | CC: | Ian.kumlien, linux-bugzilla, mjevans1983 |
Priority: | P1 | ||
Hardware: | x86-64 | ||
OS: | Linux | ||
Kernel Version: | 4.20.0 | Subsystem: | |
Regression: | No | Bisected commit-id: |
Description
Michael Evans
2019-01-11 22:58:45 UTC
Try applying this patch: https://marc.info/?l=linux-netdev&m=154696956604748&w=2 It solved it for me, what qdisc do you use? (tc qdisc will list them - I was using fq which is why it hit me) (In reply to Ian Kumlien from comment #1) > Try applying this patch: > https://marc.info/?l=linux-netdev&m=154696956604748&w=2 > > It solved it for me, what qdisc do you use? > (tc qdisc will list them - I was using fq which is why it hit me) Thank you, I can confirm that applying that single line patch DOES make the difference and resolve the issue (for me); though as the published current kernel versions are still need this patch back-ported this bug shouldn't be closed. ArchLinux had a package that made testing the a custom-kernel build easier, but it was based on 4.20.2, so I re-tested without (failed, as expected) the patch and with (appears to be working, as hoped). Yeah, it didn't make 4.20.2 - It has been picked up and marked for -stable so hopefully it will be in 4.20.3 :) FYI it's in the current pull set posted to Linus Patch 15 in: https://marc.info/?l=linux-netdev&m=154741526902566&w=2 I've had a similar issie with bridged networking in QEMU (TAP networking to a bridge with enslaved host interface) and the patch mentioned above did solve my issue (where both the VM and the host lost internet connectivity - setting the host interface down, then up again brought networking back for the host). It's not yet included in 4.20.3 either, for anyone looking for this. It's included in: 4.20.5-rc1 So, it should be in 4.20.5 final ;) Released and confirmed working, IMHO this bug report can be closed with fixed in 4.20.5 |