Warning: Attempt to read property "ID" on null in /var/www/blog/wp-content/themes/c2012/functions.php on line 39

Warning: Cannot modify header information - headers already sent by (output started at /var/www/blog/wp-content/themes/c2012/functions.php:39) in /var/www/blog/wp-includes/feed-rss2-comments.php on line 8
Comments on: OpenWRT QoS – a Simple Recipe https://blog.sergem.net/openwrt-qos-a-simple-recipe/ have to publish, sometimes Mon, 23 Mar 2020 06:54:46 +0000 hourly 1 https://wordpress.org/?v=6.1.6 By: admin https://blog.sergem.net/openwrt-qos-a-simple-recipe/#comment-441 Mon, 23 Mar 2020 06:50:42 +0000 http://blog.sergem.net/?p=146#comment-441 In reply to hfsc-convert.

Wow – thanks for the kind word – looking forward to your write-up, man!

]]>
By: hfsc-convert https://blog.sergem.net/openwrt-qos-a-simple-recipe/#comment-440 Sun, 22 Mar 2020 09:27:20 +0000 http://blog.sergem.net/?p=146#comment-440 just wanted to say: this script is absolutely excellent. an excellent balance of simplicity and effectiveness, really solved my limited bandwidth problems, and made learning about hfsc much easier than some of the absurdly complex hfsc scripts people post online.

i made some changes to it: one class for email (via ports 465 and 993), one class for VOIP (via ports used by facetime, whatsapp, etc.) and small packets (which also makes a big difference to web browsing when uploading) and another class for everything else. note that you should not try to match all packets explicitly into the ‘everything else’ class using iptables, you should instead rely on the `tc` line which features `hfsc default 20`.

tc also has a way to produce ASCII diagrams which show where the traffic is actually going, which is very useful for testing. i also made it into a full openwrt init script as openwrt does not have a full bash shell, so it is useful to be able to write short commands to reload rules and show traffic analysis (as you will probably have to fiddle with it alot).

i will try to follow up this post with more explicit details, including some good documentation i also found, in the future.

]]>