Hi Peret - Thanks for the bug report. I was browsing through the kernel
commit log and I think this bug may already be fixed by the following
commit:
commit 916f6efae62305796e012e7c3a7884a267cbacbf
Author: Florian Westphal <f...@strlen.de>
Date: Wed Apr 17 02:17:23 2019 +0200
netfilter: never get/set skb->tstamp
https://git.kernel.org/linus/916f6efae62305796e012e7c3a7884a267cbacbf
I've built a test kernel that is 5.0.0-13.14 plus that patch. Would you
be able to test it? You can find it here:
https://people.canonical.com/~tyhicks/lp1827040/
Thanks again!
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1827040
Title:
Misbehaviour of iptables 'timestart' parameter in Ubuntu 19.04
Status in iptables package in Ubuntu:
New
Status in linux package in Ubuntu:
Confirmed
Bug description:
I have detected that iptables does not behave in the same way as with
previous kernel.
Old behaviour:
'timestart' referred to the absolute time (UTC or whatever) to start applying
the rul
New behaviour:
'timestart' refers to the offset since boot start
It implies a migration of the old rules, and it is difficult to keep
compatibility, as the offset is complex to behave as an absolute time.
Is that expected? Man page suggests that the correct behaviour is the old one
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/iptables/+bug/1827040/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
