3.1.0_9 Advanced Inbound Firewall Rule Settings broken

[Tzvia]

Hello- I had updated PFBlocker from 3.1.0_7 to 3.1.0_9 yesterday (on PFS 2.6), and started seeing something amiss. While I do set my chosen IPV4 feeds to "Deny Both" it's with a custom 'DST port' in Advanced Inbound Firewall Rule Settings on INBOUND- an alias with what I need open on WAN for a road-warrior VPN. No reason otherwise as PFS normally blocks unsolicited inbound. It was working in 3.1.0_7, I could see on clicking the packet count on the PFB section of the PFS dashboarad, PFB blocking just those ports. On going into PFB/IPV4 to edit, for example, PRI1, to see the Advanced Inbound... Custom DST Port is still checked, but my alias is missing, the field is blank. So I put it back in there, saved, did an update CRON, went back, and still missing. And I still see PFB 'blocking' any port inbound and not just my alias... Same problem with IPV6.

[aumuelle]

@tzvia
same problem here;
any solutions yet?

[BBcan177]

See the patch here and report back pls.

From the Shell or pfSense GUI > Diagnostics > Command Prompt > Execute Shell Command, run this command to download the patch.

curl -o /usr/local/www/pfblockerng/pfblockerng_category_edit.php "https://gist.githubusercontent.com/BBcan177/1a33c42d0a61f3ddd9c2f1b1d514ed83/raw"

[SashLi]

• Is this issue still a problem in version 3.2.0_3 ?
• I ran into the same problem on pfsense+ ( 23.01 ) with pfBlock 3.2.0_3
• I can not set a "Custom Destination" in the Advanced Inbound Firewall Rule Settings
  • Saving the IPV4 list , always leave the "Custom Destination" field empty

[SashLi]

The overlay for selecting a Alias out of the already created ones does not appear and leave empty. Just entering a "known" alias and try to save lead in a empty field of the "Custom Destination"