Project

General

Profile

Actions

Bug #6657

closed

Unable to add network in the source section of a LAN firewall rule

Added by Edwin Chan over 8 years ago. Updated about 8 years ago.

Status:
Not a Bug
Priority:
Normal
Assignee:
-
Category:
Web Interface
Target version:
-
Start date:
07/29/2016
Due date:
% Done:

0%

Estimated time:
Plus Target Version:
Release Notes:
Affected Version:
2.3.2
Affected Architecture:
amd64

Description

Since 2.3.2-RELEASE, the following causes an "Please match the request format" error:
1. Go to Firewall / Rules / LAN
2. "Add" the following rule:
- Source: Network 10.10.10.0/24
- Destination: Single Host 8.8.8.8, any ports
3. Click Save


Files

error.png (79.3 KB) error.png Edwin Chan, 07/29/2016 05:56 AM
Actions #1

Updated by Phillip Davis over 8 years ago

That works fine for me - give more information about the data you enter and exactly which field the "Please match the the requested format" message appears in.

Actions #2

Updated by Edwin Chan over 8 years ago

Phillip Davis wrote:

That works fine for me - give more information about the data you enter and exactly which field the "Please match the the requested format" message appears in.

I have attached the image for your reference!!

Actions #3

Updated by Edwin Chan over 8 years ago

Destination host should be 8.8.8.8, but the error is the same.

Actions #4

Updated by Jim Pingle over 8 years ago

  • Status changed from New to Not a Bug

I can't reproduce it using the settings you show. Make sure there are no extra spaces or anything else non-printable in the box. If you're copying and pasting the value, erase it and enter it manually. And before you perform more tests, clear your browser cache.

Actions #5

Updated by Chris Anderson over 8 years ago

I have the same issue with the latest BETA version of Chrome. It works in the latest stable release, and in other browsers. This is probably a Chrome bug.

Actions #6

Updated by Jim Pingle over 8 years ago

Chris Anderson wrote:

I have the same issue with the latest BETA version of Chrome. It works in the latest stable release, and in other browsers. This is probably a Chrome bug.

That is likely the case. Be sure to report it upstream to Chrome.

Actions #7

Updated by Jon Gerdes over 8 years ago

See the "best answer" here: https://productforums.google.com/forum/#!msg/chrome/MBEvipQlgyg/yeM-2XDkEi8J reproduced below, just in case:

"The messages you are getting are newly implemented html5 form validation messages, triggered on textfields with the required-attribute and input fields with custom types like "email", "date",... Other browsers will follow soon with implementing these. Browser validation is a big leap forward and you probably don't want to disable it (http://diveintohtml5.org/forms.html#validation).

If you actually do want to disable the form validation, don't rename all "required" attributes, but simply put the "novalidate" attribute in your form tag."

WORKAROUND: https://chrome.google.com/webstore/detail/auto-remove-html5-form-va/odfjmmehfeibapgipjbhdojkiemkbpik sigh

Actions #8

Updated by Steve Allison about 8 years ago

So from Jon Gerdes explanation, this should be adjusted to "Bug" as pfSense is using invalid HTML5? Just not apparent on browsers that are yet to support HTML5 validation.

Actions #9

Updated by Jim Pingle about 8 years ago

It is not a bug in our code. It is a bug in Chrome that we have worked around by removing escaping from the regular expression for validation. Chrome is not properly obeying the Regular Expression specification.

See #6762 for a better discussion.

Actions

Also available in: Atom PDF