There were error(s) loading the rules: /tmp/rules.There is a lot in there that I probably can't help with but I'll try where I can! That said, not expecting to tweak over time might have been better suited for an out-of-the-box solution and not something so custom and flexible. Is it that perhaps that was the last rule I created before the NAT rule, and nothing created after was able to load properly? Otherwise, not sure I get the connection between that rule and forwarding along incoming connections.įor completeness, here's the error given in the filter load progress. What I don't really understand is what that rule had to do with preventing my NAT rule from working. So I deleted that rule, and everything works fine. The last line was an error loading that IPv6 rule. I couldn't see that anything was really wrong as everything worked internally, but in fumbling around and reading troubleshooting guides one mentioned that I should monitor the filter reload progress to make sure it actually completed. So I found the IPv6 IP address of the server using ipconfig, copied the IPv4 rule and just changed it to IPv6 type with that address. In my ignorance, I figured I may need that BlueIris server to also be able to reach out via IPv6 for whatever reason. The IPv4 rule works fine and I can see that traffic from all the cameras on that interface attempting to reach the internet and do who knows what bad things is blocked. One of my firewall rules on the BlueIris interface (192.168.7.xx) was an IPv6 version of the IPv4 rule that was to allow the BlueIris server and only the BlueIris server on that interface to reach the internet. OK, so after continued fumbling around I found the cause of the problem and a working solution, though I don't really "understand" the cause. Usually that means it's something really simple I'm just not aware of! Is there some other global setting or something somewhere that I may have missed? Scratching my head.
So in all attempts, everything is just getting denied right up front. I checked the log and the source address in the denied connection matches the address in that new rule too. I noticed in system logs that the source address reported for that attempt is different (because it is coming from my browser, not an app, and cellular company routes that differently maybe?), so I created a wide open rule for that too. I also tried to just connect to my WAN IP address on my phone, assuming it might take me to the pfsense login or page or something.
The source address listed in system log that came from my phone matches the rule source address I had just created. I tried to connect using the Blue Iris mobile app, and default deny denied it. OK, I used the Easy Rule: Pass this traffic option in the system logs/firewall page to create rules from the IP my mobile phone seems to be trying to connect to that allow traffic to any destination address, any port, any protocol. I'm sure I'm missing some important step, but not sure where. can't confirm that I did it correctly since I don't get a ping return.Īt a bit of a loss here.
#Blue iris setup how to#
I looked at a guide on how to create an echo type rule that allows that. However, in my troubleshooting I have also realized I can't ping my pfsense from outside my network either.
I just confirmed (I suppose) with their tech support that C-spire is not blocking anything from their side.
I'm wondering what else I may need to so?
#Blue iris setup Pc#
I've created a NAT rule that forwards any external IP/port combo with my WAN IP destination on port 81 to the Blue Iris PC IP on port 81, and auto created the firewall rule that allows that traffic. But I do not have the camera IPs exposed to the internet.Īs I said, this is working internally, but I can not reach the Blue Iris PC from outside my network. I have created firewall rules that allow any address on the LAN interface to access the Blue Iris PC IP address, allow everything on the 192.168.7.x interface to talk to each other, and allow the Blue Iris PC IP to reach the internet. The Blue Iris PC and all cameras are on a separate NIC and POE switch, on 192.168.7.x. 192.168.1.x is the primary LAN for all home hardwired ethernet ports. My network architecture: celeron based network appliance with multiple Intel gigabit NICs. Blue Iris has a connection wizard that walks through some of the basic settings to accomplish that but so far I have failed. I'm trying to forward the port, open a firewall hole, and whatever other settings are needed to allow a Blue Iris mobile app to access the system and view video streams from outside my network. I have Blue Iris (PC based video surveillance NVR) setup and working fine inside my private network. Not sure if this question/issue is more firewall rule, NAT, DHCP reservation, or something else.
0 kommentar(er)
