Alias edits causing firewall rule black holes
-
@Dakpan I assume you're applying after the alias change.
Check:
Diagnostics > Tables of the alias (before and after removing the IP?)
Diagnostics > Filter Reload for errors -
@Dakpan what pfSense version are you using? No floating rules in play this time ;)?
Btw, referring to another thread from you back in July: floating rules are evaluated before interface rules pfSense documentation: Rules Processing Order
-
@patient0 I remember very well, thats why I started the Setup simplified with "I have no floating rules" ;)
The box having the issue is a 2.7.2 Release -
@SteveITS you might be on to something here. The filter reload states no errors, but it stops at:
Pre-caching BLOCK ANYWhile when I reload the filter on any other PF box, it ends with:
Running plugins
DoneI'll try to find out what there is about this rule first and keep you posted.
And to be complete: The tables act as expected before and after removal. -
@SteveITS lets post the first addon right away:
The Filter Reload page stopped on a rule with this value in the description:
BLOCK ANY | No internet via this deviceApparently the refresh script crashed on the pipe character, I renamed the description to:
BLOCK ANY - No internet via this device and the Filter Reload page reached the end line DoneFor now it is to soon to tell if this character messed up the filter or just the Filter Reload output.
To be continued...
-
@Dakpan is the IP in the table, though?
-
@SteveITS yes when I add a subnet to the alias it appears in the table, when I remove the subnet from the alias it disappears in the table. So that works as expected.
-
said in Alias edits causing firewall rule black holes:
@SteveITS lets post the first addon right away:
The Filter Reload page stopped on a rule with this value in the description:
BLOCK ANY | No internet via this deviceApparently the refresh script crashed on the pipe character, I renamed the description to:
BLOCK ANY - No internet via this device and the Filter Reload page reached the end line DoneFor now it is to soon to tell if this character messed up the filter or just the Filter Reload output.
To be continued...
No difference, client still unable to mail. I'll start by setting up a test lab in front of the PF so I can impersonate his public IP...
-
@Dakpan said in Alias edits causing firewall rule black holes:
but it stops at:
Pre-caching BLOCK ANYI see a lot of these Pre-caching
If your reload stops (breaks ?) at the first then changes are great that the firewall get only partially reloaded ... and that would explain strange filter results (is think I would call this a critical salutation I guess).
That said, I 'Filter reload' yesterday and didn't saw any "Pre-caching ...".
My thoughts : you have firewall rule that 'breaks' things ?
Btw : while I could find :
in my /etc/inc/filter.inc (I'm using 25.07.1)
If you have an issue, it happens around that place.
The same file on github :
pfsense/src/etc/inc/filter.incis way different ?!?!! (a lot of work in progress)
The github == the source, has ... a lot of recent modifications in it ...
-
@Gertjan if I run this little bit of php:
$file = 'test.txt';
file_put_contents($file, "BLOCK ANY | No internet via this device". PHP_EOL, FILE_APPEND);The piped text is appended just fine to my testfile, so I think the script crash is more related to the code printing the contents of the filter_reload_status file.