VLAN an Firewall rule not matching
-
@johnpoz What table you want to see?
-
The table alias you created the 192_netz table.
What version of pfsense are you running exactly? There was some issues in the dev versions the other day where state tables not counting.. and all showing 0/0
Alias tables normally do not populate until used in a rule.. But lets make sure the alias you created actually created the table and put in the 192.168.1.0/24 network.
-
-
@interessierter dude that is not the actual TABLE that is created from the alias..
Go to the diagnostic menu, pick tables then select your 192_netz table.. Does it list this network, do you see the table in the table drop down?
See my above example showing my rfc1918 table created from my rfc1918 alias.
What I am trying to verify is this
-
@johnpoz said in VLAN an Firewall rule not matching:
@interessierter dude that is not the actual TABLE that is created from the alias..
Go to the diagnostic menu, pick tables then select your 192_netz table.. Does it list this network, do you see the table in the table drop down?
See my above example showing my rfc1918 table created from my rfc1918 alias.
What I am trying to verify is this
Sorry do you mean here? If yes, the 192_Netz is not here:
-
@interessierter well if you do not see your table populated, then that would explain why that rule is not working.
As I highlighted, tables that you create with an alias are not populated until they are put into a rule, and the rule is loaded.
If your not seeing the table listed under diagnostics. Then no it wouldn't work..
-
@johnpoz said in VLAN an Firewall rule not matching:
@interessierter well if you do not see your table populated, then that would explain why that rule is not working.
As I highlighted, tables that you create with an alias are not populated until they are put into a rule, and the rule is loaded.
If your not seeing the table listed under diagnostics. Then no it wouldn't work..
But what did I wrong? I have saved and applied the rule after creating, and I m sure that the firewall was also rebooted in the time between (what should be anyway not required).
-
@interessierter You sure your not seeing a error about memory? You sure look to have a lot of aliases..
And none of your rules show any hits at all - they all show 0/0 for states.
When you have lots entries in your tables - it can cause a memory issue.
There are many a thread related to this about. Here for example
Have you increased your table entries?
This setting is system / advanced / firewall & nat
-
This post is deleted! -
@bob-dig said in VLAN an Firewall rule not matching:
It looks like an alias can't start with a number
Looks to be working here..
-
@johnpoz You are right, I had no rule using it. Working here too.
-
@bob-dig no problem - it was a good check to be sure.
if I had to "GUESS" from how many aliases he has setup, and I see some there labeled IPv6, etc..
He needs to adjust his max table entries.. Maybe his not seeing the error that should show up when rules don't load because of allocation of memory.. I would assume that TOP_v6 rule would be quite large..
I also don't like that none of his rules showing any hits at all 0/0 there for states..
His any any IPv4 rule he shows for sure should show something vs 0/0.. That is if anything is hitting that interface at all for traffic. But tables in rules don't actually have to trigger to populate - they just need to be used in a rule. And the rules reloaded, which would happen when you hit apply.
-
@johnpoz said in VLAN an Firewall rule not matching:
@bob-dig no problem - it was a good check to be sure.
if I had to "GUESS" from how many aliases he has setup, and I see some there labeled IPv6, etc..
He needs to adjust his max table entries.. Maybe his not seeing the error that should show up when rules don't load because of allocation of memory.. I would assume that TOP_v6 rule would be quite large..
I also don't like that none of his rules showing any hits at all 0/0 there for states..
His any any IPv4 rule he shows for sure should show something vs 0/0.. That is if anything is hitting that interface at all for traffic. But tables in rules don't actually have to trigger to populate - they just need to be used in a rule. And the rules reloaded, which would happen when you hit apply.
I can change the name of the alias. This appliance have 16GB memory, and the utilization show 9%.
-
@interessierter said in VLAN an Firewall rule not matching:
This appliance have 16GB memory, and the utilization show 9%.
that has nothing to do with the max entries that can be put into a table.. Well almost nothing ;) Check the max table entries I showed.. Increase it!! To something quite large.. Or turn off all your other pfblocker aliases, etc.. See mine is set to 1.6Million ;)
What I can tell you for sure - is if the table does not show populated in the diagnostic menu - its never going to be able to do anything in a rule with that table.
-
@johnpoz said in VLAN an Firewall rule not matching:
@interessierter said in VLAN an Firewall rule not matching:
This appliance have 16GB memory, and the utilization show 9%.
that has nothing to do with the max entries that can be put into a table..
I have changed the Name, it still does not show in the table. By the way I don t see ANY of the Alias and IP section in the table under Diagnostics. The only lists that I see if from snort, and all that is added under Alias / URL
-
@interessierter If you do not see any table populated - that also points to a problem - most likely related to your max table size.
What is it set to currently? Increase it to something very large!!
-
@johnpoz this here?
-
@interessierter Is this my problem?
-
@interessierter yeah that there.. Well 2mil should be quite large, unless you have more aliases not showing?
-
@interessierter why would you have that set? That would only ever be used if you were running multiple layer 3 on the same layer 2..
And that sure shouldn't have anything to do with the tables loading.
