For our application, I have found the most time consuming process to be managing Port Forwards. Due to the fact that not every device uses the same port forwards, a simple backup or task manager config solution is not applicable. Being able to easily setup ranges (ie: set ports 1100-1200 as open to traffic) would save a lot of effort as we currently have to create a rule for 1100,1101,1102, and so forth, each with setting the allowed IPs in the advanced settings of the rule.
Thank you for sharing, and I’m very sorry to hear this is causing you trouble. To begin exploring some UX improvements, I’d like to understand exactly where the problem occurs. Have you tried entering the port range in the “Custom input” field?
The range there would not work as we would need to be able to select multiple devices under “Internal IP address” when creating the rule as port 1111 for example needs to go to a specific device.
First of all, your devices are good and work like a charm, and your updates on regular bases talk for themselves.
We use similar setups on different locations with different network-devices. The combination of devices may change, but the devices themselves are often from “the same pool of devices”. Starting with our own standard base-configuration already saves an amount of time, but still requires boring manual adaptions. It would be cool to have “sectioned” configuration files, e.g. for VPN-combinations (set of ovpn-files), snipets for firewall rules or a set of rules per network-device, etc., something comparable to the wireless network list…