Maybe a bug on NAT source alias/IP field

[RadicalEntity]

I spent much of last night trying to figure out if this is simply just my installation that’s doing this (I’ve also started fresh w/ restoring my backup yesterday too). I’m wanting to put in GeoIP aliases in that field to only allow American IPs to my various open ports. (I have a port open for BitTorrent, but I’m not going to block any IPs to it.) I am not sure if this was the case before the very recent update

However, when I select “single host or alias“, the field to enter an alias remains grayed out and this is true for all other types. It is also reproducible on any browser on all of my computers in my LAN and smartphones.

See a screenshot of such right here: https://imgur.com/OFbGFWH

I haven’t tried this on a totally new pfSense installation, but I’d rather not do such unless I have to.

If this is indeed reproducible by any of you, the only workaround that I have come up with is forcing the text box to become editable by editing the JavaScript by hand. Namely, the typesel_change function by putting just a one in the parameter for the switch block so only “case 1:” will be true. I’ve tried debugging it, but I got nowhere in the stack trace as it just ends in the middle of the jQuery js file. I’m not a programmer by any means, so I have no idea if I’m doing this right or not. I find it very hard to believe that there’s a bug in jQuery causing this.

Anyways, if you guys can’t reproduce this then it looks like I’m going to have to start fresh with no backup restored.

Thanks in advance!

[johnpoz]

Not seen this, and use this quite often.

As you can see as soon as set source or dest to single host or alias those fields become editable.

If this was something on pfsense - I would think the forums would be on fire with people having the issue.

[RadicalEntity]

@johnpoz yeah. The fact that I’ve found no prior post about this issue that I’m having and you having no problems, I may have to start with a brand new installation.

[jimp]

I can't reproduce that on anything I have handy, but the last time I did see something like that, it was the browser. I can't remember if it was an ad blocker or script blocker or the browser itself, though.

[RadicalEntity]

@jimp I've tried to get the text box editable on several different browsers on iOS, macOS and Windows w/ no extensions installed. The Windows VM was a completely clean installation as I set up the VM

macOS:
MS Edge (Chromium)
Safari
Google Chrome
Mozilla Firefox
Brave Browser

Windows:
MS Edge (Chromium)
Google Chrome
Mozilla Firefox
Brave Browser

iOS:
Safari

Again, the aforementioned issue with the text box was still present w/ no extensions added and history, cookies, offline data and such completely cleared.

The only step I haven't tried was testing this on a clean VM and building up my configuration with my favorite packages and checking for this issue as I go to see what's triggering this bug.

EDIT: I should also mention that my hardware is a PCEngines APU2 with 3 i210 NICs.

[RadicalEntity]

UPDATE: So, I was able to get the text box editable with no changes to the code. However, for the text box to change, I have to select my desired option twice in a row in the dropdown. At least I can add my aliases now.

How this happened, I haven't a clue. Anyways, something is still clearly wrong and really don't know what's causing it. If any of the developers would like to remote into my box to assess what's happening, I will happily give you access for the better of the project. I'm not a programmer as I'm just familiar with some programming concepts, so my ability to troubleshoot this any further is quite limited.

[jimp]

Which version of pfSense is this?

Does it happen if you setup a fresh install of pfSense (perhaps in a test VM?)