#Pfsense ntopng file system full how to#
#Pfsense ntopng file system full full#

Otherwise, the other 2 allow rules aren't using aliases and full details are shown. Neither of which are relevant to the issue.

For the 2 block rules, one is pointing to the wifi subnet on a separate vlan, and the other is pointing to my SNMP server's IP. Not sure why the screenshot didn't upload before, but here are the NAT rules:ДЄll the LAN rules are shown in the screenshot in the original post, nothing was hidden. Yeah, I just read something that made me realize that the WAN rules were inbound, so throwing out that idea.

#Pfsense ntopng file system full how to#

The one I'm most suspicious of being the culprit is the RFC 1918 rule, and I'm not sure how to enable logging for that one. I've done that for a few rules, but didn't see any relevant logs. I will try turning on logging on the firewall rules. Not sure why this UDP stream isn't doing the same. I've been able to ping the decoder and see the traffic on WAN interface with the pfSense's IP as the source. And that's not happening, which has led to my suspecting of NAT somehow not working for this particular traffic. If NAT is working correctly then you'd see traffic on WAN interface of pfsense with source=pfsenseWanIp Is the decoder public IP in the same subnet as the pfsense's own public IP? Here are the outbound NAT rules (they're just the auto-created ones) What do your pfsense NAT rules look like on the firewall NAT page? To clarify: encoder on LAN with a private IP can't communicate with decoder on a public IP?

GerardBeekmansВ Much thanks for the quick response! I'm new to networking, so any help is greatly appreciated. So my hunch is there's something up with the firewall not NAT'ing traffic from the Encoder (and if so, I don't know what to do about it), or the RFC 1918 rule on the WAN interface is blocking it (again, not sure what to do about that because I can't expose my network to those addresses). However, I've tried pinging the decoder from my laptop (also on the LAN network) and all the traffic is properly NAT'd and shows up on the WAN interface during packet captures. There's no traffic for either device on the WAN interface. I've run packet captures on the pfsense, and it only detects traffic for the encoder and decoder on the LAN interface. I've tested the encoder on one of our other public IP's and it streams just fine when not behind our firewall, so I know there's some sort of configuration issue on my firewall end.Д«asic layout of where the aforementioned devices sit on our network: I'm having an issue with a video encoder that I've set up behind my firewall reaching our decoder which is set up on a public IP.В The encoder sends a UDP stream to the decoder on port 4444.