Traffic seems to be ignoring rules
-
@NightlyShark said in Traffic seems to be ignoring rules:
because it is an all in all out rule.
You understand rules on an interface are only evaluated as traffic enters the interface from the network its attach.. It is not an "out" rule - you can only block in the outward connection with a floating rule.
Yes the traffic allows outbound from a client on network X.. But it is an inbound rule to the pfsense interface.. Users quite often misunderstand rule directions.. Rules are in relation to pfsense point of view.. Like your inside of pfsense... In what direction is the traffic flowing - is it inbound to pfsense or outbound..
If you want to block OUTbound traffic - that can only be done in the floating tab by selecting the outbound direction. Rules placed on an interface are always in relation to inbound traffic into that interface.
edit: but I am with you on the NVR rule - negate rules or ! (bang) rules can be easy to misinterpret. If your goal is to allow the NVR to talk to the internet.. Then create a very explicit rule that allows that..
An intelligent man is sometimes forced to be drunk to spend time with his fools
If you get confused: Listen to the Music Play
Please don't Chat/PM me for help, unless mod related
SG-4860 25.07.1 | Lab VMs 2.8, 25.07.1 -
@johnpoz What I meant is that, technically, you should not allow packets from a subnet to be able to leave using a non-subnet address (broadcasts, advertisements...) as, while a NAT does exist, it is just bad practice. Unless one uses multicasting or something. Unless I again misunderstand... Thanks anyway, man!
-
@johnpoz In any case, you just incentivized me to review all my rules again, because the part about the perspective eluded me.
-
@NightlyShark multicast or broadcast wouldn't ever be routed anyway..
If you allow say lan X to go to lan Y.. in your lan X rules, this creates a state.. The return traffic from lan Y would be allowed by the state that was created.
-
@johnpoz Just finished with the rules... The got a lot simpler... And I now understand why most of them had 0 Kb, hahaha
-
@spgeise It just hit me: if your cameras are getting their IP via DHCP, (in some models/brands) the manually set NTP could be overridden by the NTP given by DHCP (pfsense ?). I haven't observed this with hikvision, but some cheaper brands, I have seen doing all sorts of crazy stuff.
-
I just setup a NVR and some poe cameras.. I don't recall what the nvr ntp was on before I set it to mine.
But I can tell you the camera's are not reaching out to the internet via their own IP. Because they connect to the switch on the back of the NVR for poe and talking to the NVR. And this is on a different network than the network the NVR is on.. The NVR gets the ip from the network I connected it to 192.168.110.110
I created a leg into this 10.1.1 network behind the nvr, so I can get to the cameras directly - you can see from their settings they are talking to the NVR 10.1.1.1 IP for its gateway.. Which must be doing nat if the cameras are going to talk to the internet, because some 10.1.1.x address would never work via the rules on my 192.168.110 network
I just looked at the cameras directly and they don't even have ntp enabled - they must be pulling time from the NVR.. They have the correct time.. So will have to look into that a bit more..
An intelligent man is sometimes forced to be drunk to spend time with his fools
If you get confused: Listen to the Music Play
Please don't Chat/PM me for help, unless mod related
SG-4860 25.07.1 | Lab VMs 2.8, 25.07.1 -
@johnpoz That is the setup meant here? I thought they had ONVINF cameras via WiFi or something... In my hikvision poe nvr at least, your mind doesn't even go there, because the security camera streams are from the beginning only accessible via the NVR and its app. Only the doorbells and remote-location cameras have anything to do with the internet... I suspect they got in this whole mess because of some video timestamp thing...
-
@johnpoz No, they specifically say: I have a VLAN with 3 cameras and an NVR. Must be one of those NVR that have a LAN iface only.
-
@NightlyShark yeah I have a NVR on my camera vlan ;) But the cameras are actually behind the NVR in my setup.. I am new to the whole NVR scene.. I have played with stand alone IP cameras before that you just setup on whatever network you connect them too, etc. But my take which maybe flawed and only how this company does it.. The cameras are behind the NVR.. This is an isolated L2, running its own L3 space.. And it is not bridged that is for sure - I tried to see if I could see the camera's macs from my network through the NVR.. Its not bridging the interface it has on my network to the camera network.
To get to the cameras directly I had to connect another network into the poe switch on the nvr, and then outbound nat (source) nat on pfsense so my PC could even talk to the camera's IPs.
I will play with having the camera's directly try talking to my ntp server and see what I see for source IPs, etc.. I will have to do some reading on how the cameras actually sync time - would assume off the NVR..
edit: ok yeah my system is using IPC to sync the cameras time with the nvr time.. So there is zero need for the cameras to talk to any ntp server
-
Thanks everyone for the conversation. Got some interesting takeaways. This is what ultimately got things working correctly for me:
"Cameras" alias is my 3 IP cameras on the VLAN.
"Cameras_NTP" are 0.north-america.pool.ntp.org and DNS servers 9.9.9.9,4.4.4.4
"Cam_External_Ports" are 53 (DNS) and 123 (NTP).The cameras have 0.north-america.pool.ntp.org set as their NTP server. Everything working correctly now.
-
@spgeise said in Traffic seems to be ignoring rules:
"Cameras_NTP" are 0.north-america.pool.ntp.org and DNS servers 9.9.9.9,4.4.4.4
You understand that that pool.ntp.org is going to be constantly changing right.. Why would you not just allow NTP on port 123 if you want your devices to be able to talk to NTP servers out on the internet?
Also why not just use pfsense as your ntp for any devices on your network.. Now you know all your devices are syncing to the exact same source.. And the traffic is local..
-
@johnpoz said in Traffic seems to be ignoring rules:
You understand that that pool.ntp.org is going to be constantly changing right.. Why would you not just allow NTP on port 123 if you want your devices to be able to talk to NTP servers out on the internet?
Of course I understand that. That's why quad 9s and 4s are allowed out.
@johnpoz said in Traffic seems to be ignoring rules:
Also why not just use pfsense as your ntp for any devices on your network
I still haven't been able to get that to work for some reason. Not sure if the cameras are being stupid or if the rules aren't quite right. But ntp.org is the only thing to work so far.
-
@spgeise Quad 9 and quad 4 are DNS servers, not NTP...You have the option to just setup the PfSense NTP server, and allow the cameras to access the VLAN 25 address(that means the pfsense address on that subnet) port 123 UDP. You can also setup the PfSense DNS Resolver and allow the cameras to access VLAN 25 address port 53 TCP/UDP.
-
@NightlyShark said in Traffic seems to be ignoring rules:
Quad 9 and quad 4 are DNS servers, not NTP...
You are correct. I was answering the other question asking if I understood about the pool address changing. By allowing access to those DNS servers, they can resolve the pool address.
@NightlyShark said in Traffic seems to be ignoring rules:
You have the option to just setup the PfSense NTP server,
I understand this as well. The problem is that, so far, I have not been able to get this to work on my camera VLAN. I'm still trying to figure out what the issue is in my rules.
I appreciate all input in this. But I would THINK that no one digging this deep into VLANs, deny rules, DNS, NTP, etc. would need to be asked if they understand the difference between the protocols.
-
@spgeise Can you please provide all rulesets from all active subnets (LAN, VLAN25...)? Don't forget to erase any public IPs in the photos.
-
@spgeise Also, show us what you tried when attempting to activate the PfSense NTP and DNS.
-
NTP was always configured in the pfSense, with all interfaces included. It just refused to function on the VLAN25 interface. Strangely enough, specifying the VLAN25 address wasn't enough. Once I set the port to 123 I started to get some hits.
We'll go with this for now.
-
@spgeise Do you have any floating rules, by any chance?
-
@NightlyShark Nope.
