Firewall Rule "please match the requested format"
-
Hi,
My pfsense is 2.3.1 and 32bit version. When i create or edit in firewall rule, in the Source section, i choose source type is Network and trying input the network address like 10.10.10.0, then choose /24 but it says that "please match the requested format", I dont know why. I had to install other 64bit version in lab and the issue is not exist. Please advice me how to fix this issue. Thanks in advance.
Regards,
Bin -
If you can install 64-bit you should run 64-bit. Why are you installing 32-bit?
-
I think the 32bit version is more stable than 64bit and my pfsense is provided only 2GB memory so 32bit is best for me. I just want install 64bit to test whether it get same issue with 32bit or not, the result i have 64bit is fine.
-
https://forum.pfsense.org/index.php?topic=84679.0
You are on a shrinking island with sharks everywhere.
-
You are on a shrinking island with sharks everywhere.
Indeed. And it's absolutely not true that 32 bit is more stable. In the past couple years, 32 bit has had issues that 64 bit hasn't, and the reverse hasn't been true at all. It also doesn't matter you only have 2 GB RAM, there are reasons 64 bit is better other than more addressable memory.
But I doubt this is architecture-specific, because the "please match the requested format" comes from the client browser via javascript, which is the same either way. You probably have a stray space in there, or some other character other than numbers and periods.
-
I have checked again with IE, then the issue is not exist anymore. However I had re-installed with 64bit version as your recommendation. Thanks
-
I've started having this problem lately. I'm not sure why. Was there ever a solution?
It seems that chrome is the problem? I was able to get around it with IE.
-
I've started having this problem lately. I'm not sure why. Was there ever a solution?
It seems that chrome is the problem? I was able to get around it with IE.
Just got the same issue with chrome, solved with firefox
-
I found a link to a patch on github in another thread. I'm guessing it'll be iNcluded in the next release.
-
- Navigate to System > Package Manager, Available Packages tab
- Install the System Patches package
- Navigate to System > Patches
- Click + Add New Patch
- Enter the Description: Chrome Bug Workaround
- Enter the URL/Commit ID: 83469e50681bf1ab0388e5cb756d5198b7f705f4
- Click Save
- Click Fetch
- Click Apply
-
The fix worked! Thank you :)
-
I tried applying the patch and PFsense blocked it because it cannot be applied cleanly.
/usr/bin/patch --directory=/ -t -p2 -i /var/patches/57e90407624ac.patch --check --forward --ignore-whitespace Hmm... Looks like a unified diff to me... The text leading up to this was: -------------------------- |From 83469e50681bf1ab0388e5cb756d5198b7f705f4 Mon Sep 17 00:00:00 2001 |From: PiBa-NL |Date: Fri, 2 Sep 2016 00:59:52 +0200 |Subject: [PATCH] Input boxes with setPattern validation should not contain | escape characters as they are already properly considered 'lists of | characters' even when not escaped. | |(cherry picked from commit 8ea3fd0569ac2b1681de5ba3fbc2a2cc20981ad6) |--- | src/usr/local/www/firewall_nat_1to1_edit.php | 4 ++-- | src/usr/local/www/firewall_nat_out_edit.php | 4 ++-- | src/usr/local/www/firewall_rules_edit.php | 2 +- | src/usr/local/www/services_igmpproxy_edit.php | 2 +- | src/usr/local/www/services_router_advertisements.php | 2 +- | src/usr/local/www/services_unbound_domainoverride_edit.php | 2 +- | 6 files changed, 8 insertions(+), 8 deletions(-) | |diff --git a/src/usr/local/www/firewall_nat_1to1_edit.php b/src/usr/local/www/firewall_nat_1to1_edit.php |index aa25ff4..b0f1d02 100644 |--- a/src/usr/local/www/firewall_nat_1to1_edit.php |+++ b/src/usr/local/www/firewall_nat_1to1_edit.php -------------------------- Patching file usr/local/www/firewall_nat_1to1_edit.php using Plan A... Hunk #1 succeeded at 472 (offset 1 line). Hunk #2 succeeded at 499 (offset 1 line). Hmm... The next patch looks like a unified diff to me... The text leading up to this was: -------------------------- |diff --git a/src/usr/local/www/firewall_nat_out_edit.php b/src/usr/local/www/firewall_nat_out_edit.php |index 6b5d076..1fc3a62 100644 |--- a/src/usr/local/www/firewall_nat_out_edit.php |+++ b/src/usr/local/www/firewall_nat_out_edit.php -------------------------- Patching file usr/local/www/firewall_nat_out_edit.php using Plan A... Hunk #1 succeeded at 514 (offset -2 lines). Hunk #2 succeeded at 538 (offset -2 lines). Hmm... The next patch looks like a unified diff to me... The text leading up to this was: -------------------------- |diff --git a/src/usr/local/www/firewall_rules_edit.php b/src/usr/local/www/firewall_rules_edit.php |index d1f1858..7a4862e 100644 |--- a/src/usr/local/www/firewall_rules_edit.php |+++ b/src/usr/local/www/firewall_rules_edit.php -------------------------- Patching file usr/local/www/firewall_rules_edit.php using Plan A... Hunk #1 succeeded at 1356 (offset 1 line). Hmm... The next patch looks like a unified diff to me... The text leading up to this was: -------------------------- |diff --git a/src/usr/local/www/services_igmpproxy_edit.php b/src/usr/local/www/services_igmpproxy_edit.php |index 44628a7..3513369 100644 |--- a/src/usr/local/www/services_igmpproxy_edit.php |+++ b/src/usr/local/www/services_igmpproxy_edit.php -------------------------- Patching file usr/local/www/services_igmpproxy_edit.php using Plan A... Hunk #1 succeeded at 257 (offset 1 line). Hmm... The next patch looks like a unified diff to me... The text leading up to this was: -------------------------- |diff --git a/src/usr/local/www/services_router_advertisements.php b/src/usr/local/www/services_router_advertisements.php |index 5cd5c7c..bd031e2 100644 |--- a/src/usr/local/www/services_router_advertisements.php |+++ b/src/usr/local/www/services_router_advertisements.php -------------------------- Patching file usr/local/www/services_router_advertisements.php using Plan A... No such line 467 in input file, ignoring Hunk #1 succeeded at 413 (offset -55 lines). Hmm... The next patch looks like a unified diff to me... The text leading up to this was: -------------------------- |diff --git a/src/usr/local/www/services_unbound_domainoverride_edit.php b/src/usr/local/www/services_unbound_domainoverride_edit.php |index 36be9af..76d25e7 100644 |--- a/src/usr/local/www/services_unbound_domainoverride_edit.php |+++ b/src/usr/local/www/services_unbound_domainoverride_edit.php -------------------------- Patching file usr/local/www/services_unbound_domainoverride_edit.php using Plan A... Hunk #1 failed at 165. 1 out of 1 hunks failed while patching usr/local/www/services_unbound_domainoverride_edit.php done -
If it doesn't apply cleanly then either you're not on 2.3.2 or something has changed the files it is patching.
If you're not on 2.3.2, upgrade. If you have changed something else, then you might have to apply the patch manually. Looks like it was just services_unbound_domainoverride_edit.php – perhaps it was manually edited?
-
If it doesn't apply cleanly then either you're not on 2.3.2 or something has changed the files it is patching.
If you're not on 2.3.2, upgrade. If you have changed something else, then you might have to apply the patch manually. Looks like it was just services_unbound_domainoverride_edit.php – perhaps it was manually edited?
Sorry, just realised i'm still on 2.3-RELEASE. Can't update during the day, so it'll have to wait.
-
I switched over to Microsoft Edge and it worked fine.
-
Is that patch/fix en route for 2.3.2_1 or something alike? We normally don't want to include hot patches into our live clusters as the upgrade to a newer version shall be without hitch. On the test cluster it works fine.
-
It will be in 2.3.2_1.
