Tags: uw-ictd/haulage
Tags
Release 0.3.0 This release adds the major new feature of allowing rateliming via linux qdiscs on a per-user basis. It updates the haulage database schema and includes new optional configuration options to allow ratelimiting in both the upstream and downstream direction.
Release 0.2.7 This version of haulage fixes integration issues found when deploying with active CoLTE instances with field partners. Notably it fixes a conflict beteween database table names between CoLTE and haulage, and also changes the default behavior to automatically apply new migrations on startup if the migrations cleanly proceed from the existing applied migrations. Errata ------ If you are upgrading directly from haulage 0.2.0, you must upgrade to a version [0.2.1, 0.2.6] first before upgrading to this or a newer version. Versions prior to 0.2.0 are not impacted.
Release 0.0.7
monitored subnet and ignored addresses now configurable
This release fixes a couple of significant bugs wherein (1) haulage
was blocked on RADIUS server creation and (2) haulage was hard-coded
to only monitor users on 192.168.151.0/24 and ignore
192.168.151.1 (the router). Now, the monitored subnet can be set in
config.yml ("userSubnet") and any ignored addresses can be added to
"ignoredUserAddresses".
Release 0.0.6 haulagedb split from colte haulage now installs its own database (haulage_db) on install, and is fully operational without any colte dependencies. Note that the core operation only uses data_balance, not balance. Haulage also now comes with a tool called "haulagedb" that allows you to add/remove users and topup their data_balance. Migrated from github release by Spencer Sevilla <[email protected]> on March 12, 2020
Release 0.2.4 This release addresses a regression where the rust version of haulage would not be able to successfully parse packets from non-L2 interfaces, like the tun interface used by default in open5gs. This release adds logic to detect L3 interfaces and attempt to parse them directly as IPv4.
PreviousNext