Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#37342 - [iproute2] Setting up the prio qdisc is broken with iproute2 3.11-1
Attached to Project:
Arch Linux
Opened by Joel Burleson-Davis (sysengbd) - Monday, 14 October 2013, 22:31 GMT
Last edited by Evangelos Foutras (foutrelis) - Monday, 13 January 2014, 19:01 GMT
Opened by Joel Burleson-Davis (sysengbd) - Monday, 14 October 2013, 22:31 GMT
Last edited by Evangelos Foutras (foutrelis) - Monday, 13 January 2014, 19:01 GMT
|
DetailsDescription:
Setting up the prio qdisc is broken with iproute2 3.11-1. Additional info: The breakage seems to be related to this commit: http://git.kernel.org/cgit/linux/kernel/git/shemminger/iproute2.git/commit/?id=8c8a9089ba3894d793f68bb6ef0cb920d7575f7d The commit (to the manpage) adds commas "," to the priomap syntax, though this isn't recognized by netlink. I can apply the qdisc if I manual specify the priomap, without the commas. So it seems tc is now using commas for priomap and breaking the QoS scripts on my routers. Steps to reproduce: run: tc qdisc add dev enp1s0 handle 1: root prio Result is a RTNETLINK: Invalid argument tc qdisc add dev enp1s0 handle 1: root prio bands 3 priomap 1 2 2 2 1 2 0 0 1 1 1 1 1 1 1 1 Works fine. I'd expect the default priomap to work though. |
This task depends upon
Closed by Evangelos Foutras (foutrelis)
Monday, 13 January 2014, 19:01 GMT
Reason for closing: No response
Additional comments about closing: iproute2 3.12.0-1 is now in [core]; reopen if this is still an issue with the current version.
Monday, 13 January 2014, 19:01 GMT
Reason for closing: No response
Additional comments about closing: iproute2 3.12.0-1 is now in [core]; reopen if this is still an issue with the current version.
thank you having reported, is it possible to fix the summary ?