Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Bad argument `qos_Default' #3975

Closed
BennD opened this issue Apr 29, 2020 · 1 comment
Closed

Bad argument `qos_Default' #3975

BennD opened this issue Apr 29, 2020 · 1 comment

Comments

@BennD
Copy link

BennD commented Apr 29, 2020

Hi, i tried using the 'luci-app-qos' package but ran into an error
that qos is not even starting successfully.
I pretty much only configured that it is enabled and the upload/download limits.

When i connect to the router via ssh and try to start qos
/etc/init.d/qos start i get the output

Bad argument `qos_Default'
Try `ip6tables -h' or 'ip6tables --help' for more information.
Bad argument `qos_Default'
Try `ip6tables -h' or 'ip6tables --help' for more information.
Bad argument `qos_Default'
Try `iptables -h' or 'iptables --help' for more information.
Bad argument `qos_Default'
Try `iptables -h' or 'iptables --help' for more information.
Bad argument `qos_Default'
Try `ip6tables -h' or 'ip6tables --help' for more information.
Bad argument `qos_Default'
Try `ip6tables -h' or 'ip6tables --help' for more information.
Bad argument `qos_Default'
Try `iptables -h' or 'iptables --help' for more information.
Bad argument `qos_Default'
Try `iptables -h' or 'iptables --help' for more information.

my qos config file looks like this:

config classify
        option target 'Priority'
        option ports '22,53'
        option comment 'ssh, dns'

config classify
        option target 'Express'
        option ports '5190'
        option comment 'AOL, iChat, ICQ'

config classify
        option target 'Normal'
        option proto 'tcp'
        option ports '20,21,25,80,110,443,993,995'
        option comment 'ftp, smtp, http(s), imap'

config interface 'wan'
        option classgroup 'Default'
        option enabled '1'
        option download '80000'
        option upload '30000'

config default
        option target 'Express'
        option proto 'udp'
        option pktsize '-500'

config reclassify
        option target 'Priority'
        option proto 'icmp'

config default
        option target 'Bulk'
        option portrange '1024-65535'

config classgroup 'Default'
        option classes 'Priority Express Normal Bulk'
        option default 'Normal'

config class 'Priority'
        option packetsize '400'
        option avgrate '10'
        option priority '20'

config class 'Priority_down'
        option packetsize '1000'
        option avgrate '10'

config class 'Express'
        option packetsize '1000'
        option avgrate '50'
        option priority '10'

config class 'Normal'
        option packetsize '1500'
        option packetdelay '100'
        option avgrate '10'
        option priority '5'

config class 'Normal_down'
        option avgrate '20'

config class 'Bulk'
        option avgrate '1'
        option packetdelay '200'

I know this is probably not the right repository to report this issue, but i did not know where to report this since the link on the openwrt website seems to be broken.

jow- added a commit to openwrt/openwrt that referenced this issue May 29, 2020
Also ensure that the error message is actually printed to stderr and that
the rule generation is aborted if an interface cannot be resolved.

Ref: openwrt/luci#3975
Signed-off-by: Jo-Philipp Wich <jo@mein.io>
jow- added a commit to openwrt/openwrt that referenced this issue May 29, 2020
Also ensure that the error message is actually printed to stderr and that
the rule generation is aborted if an interface cannot be resolved.

Ref: openwrt/luci#3975
Signed-off-by: Jo-Philipp Wich <jo@mein.io>
(cherry picked from commit 559b338)
@jow-
Copy link
Contributor

jow- commented May 29, 2020

Fixed in OpenWrt with https://git.openwrt.org/559b338466 - as a workaround you can set option device eth0 (adjust accordingly for your device) in config interface 'wan'

@jow- jow- closed this as completed May 29, 2020
aiamadeus pushed a commit to immortalwrt/immortalwrt that referenced this issue May 30, 2020
Also ensure that the error message is actually printed to stderr and that
the rule generation is aborted if an interface cannot be resolved.

Ref: openwrt/luci#3975
Signed-off-by: Jo-Philipp Wich <jo@mein.io>
jollaman999 pushed a commit to jollaman999/openwrt that referenced this issue Jul 10, 2020
Also ensure that the error message is actually printed to stderr and that
the rule generation is aborted if an interface cannot be resolved.

Ref: openwrt/luci#3975
Signed-off-by: Jo-Philipp Wich <jo@mein.io>
phs07 pushed a commit to phs07/openwrt that referenced this issue Oct 3, 2020
Also ensure that the error message is actually printed to stderr and that
the rule generation is aborted if an interface cannot be resolved.

Ref: openwrt/luci#3975
Signed-off-by: Jo-Philipp Wich <jo@mein.io>
(cherry picked from commit 559b338)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants