4 ms·
How does FireQOS/FireHOL handle dynamic behavior like interfaces coming/going? My problem isn't so much the tc/ip/iptables syntax or semantics, but stateful mis
by mindslight 11y ago
How does FireQOS/FireHOL handle dynamic behavior like interfaces coming/going? My problem isn't so much the tc/ip/iptables syntax or semantics, but stateful mismatch like 'ip route' disappearing when an interface goes down, while 'ip rule' sticks around. Once a config gets that complex it's nice to keep in one place rather than scattered through various files. The easiest hacks are to let rules build up, or to reload everything on any ifup, but ugh. Also, manually allocating numeric table/mark/prio/class numbers is annoying.
- ktsaou 11y agoiptables (FireHOL) is generally autonomous and does not depend on interfaces being available at activation. tc (FireQOS) requires the interfaces to be up and running. To overcome these issues a) the configuration of both tools is a BASH script itself - do whatever you like in them: variables, conditions, loops, etc and b) in the distribution there is another tool called 'link-balancer' that applies inheritance to routing tables (!) and dynamically alters ip rule filters - it can also manage the balance of gateways.
- ktsaou 11y agoAnd all these tools (FireHOL, FireQOS, link-balancer) are just BASH scripts themselves (big ones of course). FireHOL: https://github.com/firehol/firehol/blob/master/sbin/firehol.in https://github.com/firehol/firehol/blob/master/sbin/firehol.... FireQOS: https://github.com/firehol/firehol/blob/master/sbin/fireqos.in https://github.com/firehol/firehol/blob/master/sbin/fireqos.... Link-Balancer: https://github.com/firehol/firehol/blob/master/sbin/link-balancer.in https://github.com/firehol/firehol/blob/master/sbin/link-bal...