Is this a bug?
tucansam last edited by
Not sure where to put this, so here it is.
Firewall -> Rules -> LAN
Create a new rule or modify an existing one. In this case I have a few rules using the traffic shaper, and would like to add more.
Copy an existing rule, or edit and existing rule, or create a new one, behavior is the same.
Under "Source," select "Single host or alias." Enter either an alias name or a single IP address.
Error I get is "Please match the requested format" with a yellow exclamation point in the field where you enter an alias or single host.
Thus, I cannot modify, create, copy, etc rules.
Either that or I'm doing it wrong. Please educate me if I'm doing it wrong.
All of the existing rules that I have work, and, as they were carried over during my various version upgrades, all look like what I am trying to do, ie, they all say "Single host or alias" and they all either list an single IP address, or an alias.
But I can't create new ones.
cmb last edited by
That "please match requested format" only happens if you have something other than letters, numbers, _ . or : in the field. Those cover all the valid possibilities for IPs and alias names. Guessing you're putting in a stray space or other invalid character, or maybe if your browser has a form filler of some sort, it's doing so.
rhouk last edited by
I'm on 2.3.2-RELEASE and I experienced this same problem when trying to use an alias. I wonder if the OP is using chrome or chromium and, if so, if that could be the problem? I ask because, I tried again repeatedly with Chromium and could not get it to work. But started Firefox and it worked the first time.
KOM last edited by
Yes it's a known Chrome bug.
You can use the System Patches package to apply https://patch-diff.githubusercontent.com/raw/pfsense/pfsense/pull/3127.patch which will allow the validation to work with the latest Chrome. The Chrome regex parser has a bug in that it does not allow escaped characters inside a list, even though it is a valid – but not required -- regex expression.
NOYB last edited by
The Chrome regex parser has a bug in that it does not allow escaped characters inside a list, even though it is a valid – but not required -- regex expression.
Not required unless a character class includes a character that needs to be escaped that is. Such as, oh say a backslash.