IP Subnet to internet routing fails 5x/day after latest 16.04 LTS updates

Asked by Craig-z

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.

Question information

Language:
English Edit question
Status:
Answered
For:
Ubuntu Edit question
Assignee:
No assignee Edit question
Last query:
Last reply:
Revision history for this message
actionparsnip (andrew-woodhead666) said :
#1

I suggest you report a bug. Do you have the latest BIOS?

You could cron a command to run every hour to restart the service (as root) as a work around

Revision history for this message
Craig-z (craig-z) said :
#2

BIOS is up to date.
Reported as a "bug", thanks, I find bug reporting here very confusing, as apparently did the person who wrote this report:
I'd like to link "https://answers.launchpad.net/ubuntu/+question/639797 to my bug report. Looks very much like the same issue.

Can you help with this problem?

Provide an answer of your own, or ask Craig-z for more information if necessary.

To post a message you must log in.