Bug: Creating a rule with a single IPv4-scope not editable #98
Description
After editing or creating a rule with a single IP-scope (as in allowing DNS-traffic only to the DNS server at 192.168.1.2, or a network via 192.168.1.0), adds a "subnet mask"-thingie of 255.255.255.255.
It works fine, but when opening the rule at a later time, and trying to save it, the Address field complains about an invalid IP.
Workaround is deleting the "/255.255.255.255"
Also while you're at it, under Windows 11, the X-indicator to indicate the error is half-hidden behind the groupbox border.
And maybe it would be cool to add a little "i" or something to list the supported keywords, like "Local Subnet"