Package Details: wondershaper-git r41.67473d4-1

Git Clone URL: https://aur.archlinux.org/wondershaper-git.git (read-only, click to copy)
Package Base: wondershaper-git
Description: Command-line utility for limiting an adapter's bandwidth
Upstream URL: https://github.com/magnific0/wondershaper
Keywords: bandwidth limit network
Licenses: GPL
Submitter: None
Maintainer: aksr
Last Packager: aksr
Votes: 20
Popularity: 0.36
First Submitted: 2015-08-31 16:24 (UTC)
Last Updated: 2021-01-19 14:35 (UTC)

Dependencies (2)

Required by (0)

Sources (1)

Latest Comments

autape commented on 2020-12-04 06:26 (UTC)

The config file is at /etc/conf.d/wondershaper.conf, but the systemd unit file has EnvironmentFile=/etc/systemd/wondershaper.conf.

bet4it commented on 2020-10-09 13:34 (UTC)

Please add a pkgver() function. https://wiki.archlinux.org/index.php/VCS_package_guidelines#The_pkgver()_function

i_magnific0 commented on 2018-01-11 09:39 (UTC) (edited on 2018-01-12 14:38 (UTC) by i_magnific0)

tc has recently been reported to not work properly with newer version of NetworkManager. The bug has been reported to the Arch Linux bugtracker and is also discussed on the wondershaper GitHub pages. If your experiencing this issue too, please report in on the bug at the link below to increase its visibility.

Links:

UPDATE: the issue has been fixed in networkmanager 1.10.3dev+38+g78ef57197-1

i_magnific0 commented on 2017-12-01 12:57 (UTC)

Github repo maintainer here. The fix described by @fullmetal given that is detailed in the issues doesn't really fix much as the entire ingress traffic control is broken. Although removing the :1 does allow you to run wondershaper with no complaints. So I decided to install the package again today and fix a few issues. The entire outgoing traffic is now limited with HTB thanks to another dev. He also just removed the entire ingress part. The latter I now added back, which works much better.

fullmetal commented on 2017-10-15 18:38 (UTC)

Apparently it can be fixed pretty easily https://github.com/magnific0/wondershaper/issues/13 The maintainer seems pretty inactive though

quellen commented on 2017-09-30 18:40 (UTC)

it doesn't work anymore. $ sudo wondershaper -a eth0 -d 10000 -u 500 What is ":1"? Usage: ... u32 [ match SELECTOR ... ] [ link HTID ] [ classid CLASSID ] [ action ACTION_SPEC ] [ offset OFFSET_SPEC ] [ ht HTID ] [ hashkey HASHKEY_SPEC ] [ sample SAMPLE ] [skip_hw | skip_sw] or u32 divisor DIVISOR Where: SELECTOR := SAMPLE SAMPLE ... SAMPLE := { ip | ip6 | udp | tcp | icmp | u{32|16|8} | mark } SAMPLE_ARGS [ divisor DIVISOR ] FILTERID := X:Y:Z NOTE: CLASSID is parsed at hexadecimal input.

tengel commented on 2016-11-13 19:45 (UTC)

I added a backup() array for the config file. Prior to me adopting this package today and updating it to include the config and systemd unit, it never existed in this package.

kseistrup commented on 2016-11-13 19:34 (UTC)

error: failed to commit transaction (conflicting files) wondershaper-git: /etc/conf.d/wondershaper.conf exists in filesystem Errors occurred, no packages were upgraded. The wondershaper installation shouldn't barf just because /etc/conf.d/wondershaper.conf already exists, instead it should rename the new wondershaper.conf to wondershaper.conf.pacnew and continue installing.

RaphAstronome commented on 2016-08-06 13:29 (UTC)

Since few weeks, this causes kernel panic when executing the "clear" action. This can be triggered when executing "-c" option or when service stops (at shutdown or by doing a "systemctl stop"). Starting the services or see service status don't cause problems. The bandwidth limiter works normally when started. I use this on an RJ45 (not WiFi) Ethernet connection named "enp3s0". Thanks,

gregodadone commented on 2016-07-24 01:17 (UTC)

Please add git as a dependence!