Bug #4708
closed
LAN Firewall Blocking 443 out on Default deny rule IPv4 (IPv6 Enabled Router)
0%
Description
I'm using pfSense 2.2.2-RELEASE (amd64), and have configured IPv6 through a tunnel broker. Everything is working fine that i can tell, but the router is logging that it's blocking Lots of 80 & 443 traffic from my local Lan out?
I have added more rules trying to allow this traffic but it hasn't helped.
Screen shot of FW settings & Pcap attached.
block/1000000103 May 16 16:18:19 LAN 192.168.y.z:60356 74.125.226.64:443 TCP:PA
block/1000000103 May 16 16:18:17 LAN 192.168.y.z:45975 65.199.32.59:443 TCP:FPA
block/1000000103 May 16 16:18:09 LAN 192.168.y.z:45975 65.199.32.59:443 TCP:FPA
block/1000000103 May 16 16:18:06 LAN 192.168.y.z:45975 65.199.32.59:443 TCP:FPA
block/1000000103 May 16 16:18:04 LAN 192.168.y.z:45975 65.199.32.59:443 TCP:FPA
block/1000000103 May 16 16:18:03 LAN 192.168.y.z:45975 65.199.32.59:443 TCP:FPA
block/1000000103 May 16 16:18:02 LAN 192.168.y.z:45975 65.199.32.59:443 TCP:FPA
block/1000000103 May 16 16:18:02 LAN 192.168.y.z:45975 65.199.32.59:443 TCP:FA
Files
| Blocked.pcap (760 Bytes) Blocked.pcap | Capture of traffic blocked | ||
| Lan FW settings.png (31.4 KB) Lan FW settings.png | Firewall Settings |
Updated by 
Updated by Marc Riley almost 9 years ago
Okay, that link makes sense, so is there a way to Stop Logging these packets that arrive after the connection has been closed?
If the Firewall is tracking these packets then I would assume that it should be able to label them as something else and not the Default Deny Rule, AND have an option not to be Logged.
Updated by Chris Buechler almost 9 years ago
- Status changed from New to Not a Bug
it's correct all around as is. the default deny is what blocks them, logging of default deny can be user-controlled.