IP ranges help simplify/optimize policy rules

Product Discussion Feature Requests
1

I really wish Peplink used IP ranges instead of power-of-two sized CIDR.

For example, one of the AWS blocks is 99.83.64.0 - 99.84.255.255 but in CIDR that requires rules: 99.83.64.0/18, 99.84.0.0/16, and 99.83.128.0/17.

Can we please just get ranges for rules to simplify/optimize things? Thanks!

5 Likes
2

Are you using grouped networks? If you create a grouped network entry for it (say “aws whatever”) and add all three ranges to it, you can then reference the grouped network by name from firewall or outbound policy

4 Likes
3

I think ranges would be more elegant (even for groups!) but otherwise yes, this solves my problem. Thanks!