[SOLVED] Bug or feature: selection all / no interfaces in a floating rules

[imagmbh]

Hello,

we found an irritating beaviour: Creating a floating rule and selecting the the correct interface (WAN) or all interfaces for the the rule (e.g. IN-Rule for Port 443 for configuration) results in a non-accessibility of the configuration page. Explicit selecting none interfaces ("Select Interfaces ...") results in the desired behavior, the configuration page ist accessible from the WAN-side.

We find this behavior illogical, is it a bug or a feature?

Martin

[Fright]

the configuration page ist accessible from the WAN-side

wow

results in a non-accessibility of the configuration page

testing from host in wan subnet or behind gateway?

[imagmbh]

It was tested from a host in the WAN-Subnet.

[Fright]

in this case it is a feature )
look for reply-to directive in this rule (Firewall: Diagnostics: pfInfo: Rules). response packets are sent to the router mac.

[imagmbh]

Thanks for your answer and your hint!