This may or may not be appropriate for a firewall, but I would like to see some more routing options added to Astaro.
1. Load balancing across equally weighted gateways. Something like in a Cisco router where you have two default routes with the same metric. By default a Cisco router will load balance across these two routes.
2. Related to the first request, route metric assignments in the static route page. The ability to assign different paths based on load or availability of a path.
3. Routing protocol! OSPF would be the preferred choice…
4. DiffServ QOS options in the QOS section.
5. This is more of an interface request; The ability to down interfaces and modify definitions on the fly regardless of their use in other things like filter rules. Currently you can’t down an interface to reset it. You can’t modify a network’s definition if it is part of a group. These restrictions force me to down my whole network and rebuild large sections of rules and definitions to make one simple change like a subnet mask.
I know some of these things can be achieved with hacks and additional software, but that doesn’t really help to promote your product to people who are not comfortable looking under the hood (like my windows bred IT manager…) Also, I would feel more comfortable knowing that you have tested it for compatibility and security.
BTW: Thanks for adding the extra control to the SMTP proxy. Patch 4.010’s added white list and finer SpamAssassin control has made my postmaster’s life much easier. It is nice to see a company respond to user requests.
This thread was automatically locked due to age.
