IP Subnet to internet routing fails 5x/day after latest 16.04 LTS updates
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
linux (Ubuntu) |
Expired
|
Medium
|
Unassigned |
Bug Description
Since updating Ubuntu 16.04.02 LTS with all latest patches on 6/2, my subnet internet routing is failing 5x+/day for my Windows 10 machine. Unfortunately, Windows 10 is also a moving target, which also updated 6/2, about when this problem started. Bug report also filed with MS.
Why I think it's Ubuntu... When Windows 10 based web pages stop loading, email stops transmitting, and internet-based CAD licensing stops working, I can get everything working like new again by typing "firehol start", which refreshes iptables entries. So I suspect the issue might be related to either the Linux kernel or iptables.
I also see another bug dated 2-Jun-2017 for IP subnet routing, but that one is running on an ARM processor. Mine is AMD FX-8120, Ubuntu 16.04.2 LTS x64. The reported problem sounds similar.
I performed an IP Tables dump during "operating" and "not routing" states. I can't see any difference between the two dumps, but running firehol start clears the problem.
While in the "problem state", my Ubuntu server does have internet connectivity. i.e. Loading web pages on Firefox on the Server/router does work. On the "routed" Windows 10 machine, what doesn't work are; ping (internet), Firefox (internet), Thunderbird (internet)... From the Windows 10 machine what does work are; ping (server), Firefox (server apache web pages), Thunderbird (server imaps accounts). So the Windows 10 machine still has full server access over gigabit ethernet, but can't see any internet based services, where IP routing is required to succeed. "firehol start" restores routing until for a brief time when the Windows machine is busy accessing the internet. Routing stayed up all night when there was no Windows 10 internet routing activity. Resuming activity in the morning caused a quick routing failure.
---
ApportVersion: 2.20.1-0ubuntu2.6
Architecture: amd64
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/
/dev/snd/
DistroRelease: Ubuntu 16.04
HibernationDevice: RESUME=
InstallationDate: Installed on 2016-06-13 (357 days ago)
InstallationMedia: Ubuntu-Server 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.3)
MachineType: To be filled by O.E.M. To be filled by O.E.M.
Package: linux (not installed)
ProcEnviron:
LANGUAGE=en_US
TERM=xterm-
PATH=(custom, no user)
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcFB: 0 nouveaufb
ProcKernelCmdLine: BOOT_IMAGE=
ProcVersionSign
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon.
RelatedPackageV
linux-
linux-
linux-firmware 1.157.10
RfKill:
Tags: xenial
Uname: Linux 4.4.0-78-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:
_MarkForUpload: True
dmi.bios.date: 11/24/2011
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 0901
dmi.board.
dmi.board.name: SABERTOOTH 990FX
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev 1.xx
dmi.chassis.
dmi.chassis.type: 3
dmi.chassis.vendor: To Be Filled By O.E.M.
dmi.chassis.
dmi.modalias: dmi:bvnAmerican
dmi.product.name: To be filled by O.E.M.
dmi.product.
dmi.sys.vendor: To be filled by O.E.M.
affects: | kernel → linux (Ubuntu) |
Thank you for taking the time to report this bug and helping to make Ubuntu better. It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general. It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it. You can find some hints about determining what package your bug might be about at https:/ /wiki.ubuntu. com/Bugs/ FindRightPackag e. You might also ask for help in the #ubuntu-bugs irc channel on Freenode.
To change the source package that this bug is filed about visit https:/ /bugs.launchpad .net/ubuntu/ +bug/1695829/ +editstatus and add the package name in the text box next to the word Package.
[This is an automated message. I apologize if it reached you inappropriately; please just reply to this message indicating so.]