I was able to reproduce the wondershaper behavior with iproute
20071016-2ubuntu1 from the hardy 8.04 release. I can confirm that the
iproute package in hardy-proposed, 20071016-2ubuntu2, does fix the
behavior when wondershaper is started. The rate limiting that
wondershaper does is also set up more effectively with the updated
iproute package; I did not notice any regressions with basic
wondershaper usage and some test file transfers.
I was not able to reproduce the shorewall failing to start behavior.
However, I'm marking both the wondershapr and shorewall tasks as
invalid, as I believe the iproute update fixes them. If that's
incorrect, please reopen by marking the tasks as New and provide more
information to track down the specific issues within those packages.
Thanks for helping to improve Ubuntu!
** Changed in: shorewall (Ubuntu Hardy)
Status: New => Invalid
** Changed in: wondershaper (Ubuntu Hardy)
Status: New => Invalid
** Changed in: shorewall (Ubuntu)
Status: New => Invalid
** Tags added: verification-done
** Tags removed: verification-needed
--
[hardy] running wondershaper gives 'What is "flowid"? Illegal "police"'
https://bugs.launchpad.net/bugs/194623
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
