Can't set port range in firewall rules

Started by dgktkr, September 12, 2020, 07:33:36 PM

Previous topic - Next topic
Hi,

I've succeeded in bringing up 20.7 on my arm device (Clearfog Base) and so far most everything functions as expected.

An exception is setting a port range for source or destination in a firewall rule in the http GUI. While on a page generated by firewall_rules_edit.php the section "Destination port range" shows up with "From:" and "To:", but neither field will accept input. The fields below those labelled "any" are grayed out and show a "not allowed" symbol (circle with a slash) when the mouse cursor hovers over them.

The same behavior occurs with Safari, Firefox and Chrome. I don't know about Edge or IE since we're an Apple household.

Am I doing something wrong, or is this a bug?

dgktkr

Does it work when you assign an alias in the port, where that alias consists of that port range in question?
An I assume you have defined as protocol either tcp or udp, right?

Thanks jasonmc, that was it. The behavior occurred because the protocol selected was the default "any". When changed to "TCP/UDP" the buttons under "From:" and "To:" became active. That allowed a choice of a well known port or an alias of my own making.

dgktkr



Quote from: jassonmc on September 12, 2020, 07:45:29 PM
Does it work when you assign an alias in the port, where that alias consists of that port range in question?
An I assume you have defined as protocol either tcp or udp, right?