Traffic logs

[Bunz]

I just set up a WAP filtering bridge using 1.0-beta1 and all seems to be working.

ADSL(192.168.5.1) <–> pfsense, fxp0(192.168.5.254) -- pfsense, ath0 (192.168.5.254) <--> wifi pcs

My question is to do with traffic log constantly logging

1. 457076 rule 36/0(match): block in on fxp0: 192.168.5.254 > 0.0.0.0:  pfsync 676
000059 rule 36/0(match): block in on bridge0: 192.168.5.254 > 0.0.0.0:  pfsync 676
000033 rule 36/0(match): block in on fxp0: 192.168.5.254 > 0.0.0.0:  pfsync 676
1. 542835 rule 36/0(match): block in on fxp0: 192.168.5.254 > 0.0.0.0:  pfsync 228
000064 rule 36/0(match): block in on bridge0: 192.168.5.254 > 0.0.0.0:  pfsync 228
000024 rule 36/0(match): block in on fxp0: 192.168.5.254 > 0.0.0.0:  pfsync 228
2. 000307 rule 36/0(match): block in on fxp0: 192.168.5.254 > 0.0.0.0:  pfsync 228
000058 rule 36/0(match): block in on bridge0: 192.168.5.254 > 0.0.0.0:  pfsync 228
000023 rule 36/0(match): block in on fxp0: 192.168.5.254 > 0.0.0.0:  pfsync 228
2. 000387 rule 36/0(match): block in on fxp0: 192.168.5.254 > 0.0.0.0:  pfsync 676
000056 rule 36/0(match): block in on bridge0: 192.168.5.254 > 0.0.0.0:  pfsync 676
000023 rule 36/0(match): block in on fxp0: 192.168.5.254 > 0.0.0.0:  pfsync 676
2. 000352 rule 36/0(match): block in on fxp0: 192.168.5.254 > 0.0.0.0:  pfsync 228
000056 rule 36/0(match): block in on bridge0: 192.168.5.254 > 0.0.0.0:  pfsync 228

Why?

Also rules on WAN work fine, I don't have any rules on LAN except to allow DHCP back to WAN but everything works anyway. I can ssh or connect to 80 without any problem. Are there implied rules on the LAN?

[sullrich]

What version are you running?  This is fixed in the latest prebeta2 version.

[Bunz]

1.0-BETA1
built on Mon Dec 26 03:18:19 UTC 2005

[sullrich]

You need to update: http://www.pfsense.com/~sullrich/BETA2-BUGVALIDATION5/

[Bunz]

I understand from previous threads that the filtering bridge blocks everything unless there's a rule.

I don't see this though. WAN blocks everything by default, LAN allows everything by defualt.

If I set BLOCK rule on LAN

Proto  Source  Port  Destination  Port  Gateway  Description 
X *         *              *     *                 * *               block all

I can stilll connect to 80 and ssh. there doesn't seem to be any filtering on LAN

[sullrich]

System -> Advanced -> Enable Filtering Bridge

[hoba]

@Bunz:

I understand from previous threads that the filtering bridge blocks everything unless there's a rule.

I don't see this though. WAN blocks everything by default, LAN allows everything by defualt.

If I set BLOCK rule on LAN

Proto  Source  Port  Destination  Port  Gateway  Description 
X *         *              *     *                 * *               block all

I can stilll connect to 80 and ssh. there doesn't seem to be any filtering on LAN

There is an anti logout rule at lan (so you don't shut down access to the webgui accidently). You can disable that at system>advanced as well.