[Bug 1827040] Re: Misbehaviour of iptables 'timestart' parameter in Ubuntu 19.04

2019-05-04 Thread Peret Lopez
Hello, Tyler, I works with your patch! Confirmed that with the patch, it understands the times as absolute ones. I managed to test it in a virtual machine. Switching from one version to the other, I can verify the behaviour easily. The command I am testing is: sudo iptables -I OUTPUT -p tcp -m

Re: [Bug 1827040] Re: Misbehaviour of iptables 'timestart' parameter in Ubuntu 19.04

2019-05-03 Thread Peret Lopez
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

[Bug 1827040] Re: Misbehaviour of iptables 'timestart' parameter in Ubuntu 19.04

2019-04-30 Thread Peret Lopez
** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1827040 Title: Misbehaviour of iptables 'timestart' parameter in Ubuntu 19.04 To

[Bug 1827040] [NEW] Misbehaviour of iptables 'timestart' parameter in Ubuntu 19.04

2019-04-30 Thread Peret Lopez
Public bug reported: 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