Version 0.5.2 of Prometheus QoS
Release Notes: This release fixes long integer traffic counter overflow at 4 gigabytes (up or down). Incorrect inclusion of HTTP proxy traffic in direct traffic has been fixed. Incorrectly displayed parameters of asymmetrical upload have been fixed. A new option magic-priorities allows better soft shaping without reducing HTB ceil.
Other releases
Release Notes: Startup times were improved by using the iptables-restore utility. Much less CPU system time is used because, by default, the iptables CLASSIFY target is used instead of iptables MARK.
Release Notes: Multiple keywords can be defined and used in the configuration file, so you can use Prometheus QoS to handle both symmetrical and asymmetrical or both limited and unlimited virtual subscriber lines in a single configuration file.
Release Notes: The most important feature enhancement is improved performance (packets-per-second throughput) in heavy-duty configurations, where Prometheus QoS is used to allocate the capacity of a shared Internet uplink among thousands of individualy configured IP addresses in a local network. Networks with a small number of individually configured hosts won't see any difference.
Release Notes: The most important change is probably the bugfix that allows the magic-fixed-prio and magic-relative-prio parameters to be used even with magic-fixed-limit and magic-relative-limit set to 0. This means that Prometheus can now be used to freely share spare bandwith as a real Quality of Service (QoS) tool, and not only just as a traffic shaper and Fair Use Policy (FUP) enforcement tool.
Release Notes: This release fixes long integer traffic counter overflow at 4 gigabytes (up or down). Incorrect inclusion of HTTP proxy traffic in direct traffic has been fixed. Incorrectly displayed parameters of asymmetrical upload have been fixed. A new option magic-priorities allows better soft shaping without reducing HTB ceil.
