>That's what happens when you have a rule with an interface that is
>deleted and you don't remove the rule, though that should never be the
>case for LAN. Email me a backup of your config.
Possibly a better method on my end given the Opt ints have vlans associated
with them is not to use "OPTn Sub
On Thu, Oct 8, 2009 at 7:09 PM, Joseph L. Casale
wrote:
>>Please switch to raw logs and show us the entry text and syntax error
>>from the alert.
>>
>>Sanitize before-hand if you want.
>
> I am not sure if this is what you want, but:
>
> php: : There were error(s) loading the rules: /tmp/rules.deb
>Please switch to raw logs and show us the entry text and syntax error
>from the alert.
>
>Sanitize before-hand if you want.
I am not sure if this is what you want, but:
php: : There were error(s) loading the rules: /tmp/rules.debug:256: syntax
error pfctl: Syntax error in config file: pf rules
On Thu, Oct 8, 2009 at 6:58 PM, Joseph L. Casale
wrote:
> I all of a sudden am getting syntax errors in the logs which I don't recall
> seeing before with respect to a few generic block rules I have on an opt
> interface.
>
> Action: Reject
> Interface: OPT2
> Protocol: Any
> Source: Any
> Destina
I all of a sudden am getting syntax errors in the logs which I don't recall
seeing before with respect to a few generic block rules I have on an opt
interface.
Action: Reject
Interface: OPT2
Protocol: Any
Source: Any
Destination: LAN Subnet
I use this to block anything destined to the LAN interfa
