Hello, Tyler,I am happy to know you have probably found the issue. And I am 
happy to test it. The problem is that I am not experienced in testing kernels 
at all.I am an advanced users, but not a programmer.I do not know how to switch 
(with no high risk) the kernel, test, and switch it back.If you can give me 
some indications, just to have an idea of the process, I think I will manage; 
maybe it is as simple as copying it to the place where kernels are copied, and 
changing the 'pointer' to the active kernel somewhere.Thanks!
    En jueves, 2 de mayo de 2019 16:15:31 CEST, Tyler Hicks 
<tyhi...@canonical.com> escribió:  
 
 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 subscribed to the bug
report.
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

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to iptables 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/~touch-packages
Post to     : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

Reply via email to