Error in NAT page
-
I get something similar on editing the firewall NAT port forward screen. version 2.4 beta.
http://192.168.1.1/firewall_nat_edit.php?id=1
The following input errors were detected:
Invalid characters detected ["eth1.30","pppoe0","eth0","eth1"]. Please remove invalid characters and save again.Only in chrome, on multiple computers. No issues on IE Edge though.
-
eth1.30
There is no such interface designation in pfSense. That looks like Linux.
-
I did used to have a vlan 30 on that Ethernet port, the LAN, but deleted the vlan.
Just thought it was odd. I had no chrome extensions running, I shall test it on Firefox next.
-
pfSense would be something like igb1_vlan30
-
Interesting, I received a similar error with my new pfSense router hardware that has barely been configured. I'm using the latest 2.4RC and receive this message in chrome:
The following input errors were detected: Invalid characters detected ["eth0","eth1","eth7.2","eth6.13","eth6.12"]. Please remove invalid characters and save again.In my case, these names look familiar. They are the interface names I used on the previous router that I unplugged BEFORE starting pfSense configuration. In the old router, these interface names were also listed on the DNS page. The old router is a Ubiquiti Pro 8 port edgerouter and again, was unplugged before setting up the new router!
I'm in the midst of initial setup and I've not used these names at all. I've only setup the interfaces, some basic allow LAN rules, and completed aliases. My next step was to start port forwarding and I receive this error at the top of the port forwarding page before I've had a chance to fill anything out :)
I'm not sure how these names could have made their way in pfSense configuration?? Any ideas?
-
Interesting, I received a similar error with my new pfSense router hardware that has barely been configured. I'm using the latest 2.4RC and receive this message in chrome:
The following input errors were detected: Invalid characters detected ["eth0","eth1","eth7.2","eth6.13","eth6.12"]. Please remove invalid characters and save again.In my case, these names look familiar. They are the interface names I used on the previous router that I unplugged BEFORE starting pfSense configuration. In the old router, these interface names were also listed on the DNS page. The old router is a Ubiquiti Pro 8 port edgerouter and again, was unplugged before setting up the new router!
I'm in the midst of initial setup and I've not used these names at all. I've only setup the interfaces, some basic allow LAN rules, and completed aliases. My next step was to start port forwarding and I receive this error at the top of the port forwarding page before I've had a chance to fill anything out :)
I'm not sure how these names could have made their way in pfSense configuration?? Any ideas?
Switching from Chrome over to IE also worked for me. So I cleared out all browser history in chrome and logged back in and now all is well in chrome. Easy solution, but very odd that something is being passed from the browser to the form before editing.
-
Most likely, the browser autofill put that in there and you didn't catch it. It couldn't have come from pfSense as we don't use "eth<number>" names anywhere.</number>
-
Most likely, the browser autofill put that in there and you didn't catch it. It couldn't have come from pfSense as we don't use "eth<number>" names anywhere.</number>
I didn't perform a "post" or click anything. It literally appears the very first time (and every time thereafter) when you click the NAT link in the menu. No form filling out and no clicking save or any other action. It was consistent. I agree that something was being autofilled from the browser, but I dont' see how it's possible that the browser was saving anything. Perhaps pfSense performs some sort of post action on page load?
Doesn't really matter because it can be worked around, but just wanted to provide another data point as others might run into this.
-
For me this was caused by a cookie set by the TLD.
I have my router at pfsense.TLD.com. TLD.com set MixPanel and Google Analytics cookies. When firewall_nat_edit.php loops through $_REQUEST it barfs on these cookies.
See https://github.com/pfsense/pfsense/blob/153f09b8d344f24d0ecf549e90c8d6b75d472124/src/usr/local/www/firewall_nat_edit.php#L144
Seems like a bug to me.
-
There is a fix for this in 2.4.2 now. It should be in snapshots later today/early tomorrow.
