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 owner --uid-owner <user> -m time --weekdays Su,Mo,Tu,We,Th,Fr,Sa --timestart 00:00:00 --timestop 04:30:00 -j DROP <user> being substituted by the user to be tested. So, when those two conditions are met (the time scheduled specified and the user), then tcp packets are dropped. With 5.0.0-13 kernel, time considered is since startup, so it rejects packets since the computer is up, no matter the time. It is important to specify all the week days (or perhaps Sunday is the one that matters); If not specified all of them, the test may not be tested correctly (that was my experience) With the new kernel, it allows those packets (unless between 00:00 and 04:30, ovbiuously). I think times are UTC based, so I test and try want I want to specify a time. Thanks a lot -- 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 manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/iptables/+bug/1827040/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
