[Help] TOS 7 Firewall Issue Using Subnets

[renob]

There seems to be a problem with the firewall on TOS 7 using subnets. Firewall rules work fine when using "All" or specifying a single IP but do not work when using a subnet.

Is this a TOS 7 bug saving the subnet as 192.168.0.0,16 in the backend instead of 192.168.0.0/16? Using a comma is an extremely weird and in my opinion wrong way of displaying the subnet information to the user. This should use a / character. Seeing the comma I immediately think something is broken/buggy or the person who worked on that doesn't understand how subnets are meant to be displayed.

Order and deny:


Not working:


Working:


Working:

[TMzethar]

We apologize for the inconvenience you've encountered, and we appreciate you bringing these issues to our attention.
We have notified our project team to verify the situation, and your suggested improvements have been submitted for review.
We will keep you updated on further developments in this post.

[TMzethar]

We've confirmed that the second field for "Subnet Mask" in the current TOS version only accepts values like 255.255.0.0 or 255.255.255.0 — not shorthand like 16 or 24.

Sorry for any confusion — the field doesn't currently show a hint. We're planning to add one in a future update.

[renob]

Thank you for the update.

Having not only a hint but also a field validation which does not allow someone to save anything other than a full-IP mask would make much more sense. Why let users type an invalid value at all?

Even better would be having that field as a dropdown rather than a text input field.

The selectable dropdown items looking like:
/1 - 128.0.0.0
...
/12 - 255.240.0.0
...
/24 - 255.255.255.0
...
/32 - 255.255.255.255

[EriChan]

We appreciate your detailed description and have passed your valuable feedback along to our product department for evaluation.