I have an overly complicated network with VLANs and firewall rules, I would like to simplify things with Blue Iris and my cameras. I want to add a second nic to my Blue Iris machine (Dell Optiplex) but I don't see an option within the Blue Iris software to do so. How do I add the second nic and allow camera traffic only on one connection and regular internet traffic on the other?
Adding NIC
- Thread starter OSU_BuckeyesFan
- Start date
cyberwolf_uk
Getting comfortable
- Sep 27, 2014
- 636
- 802
Install the second nic into the desktop, configure it to the same subnet as your cameras i.e main LAN is 192.168.1.x Camera LAN is 192.168.10.x
In BI settings navigate to the the settings below and choose that IP range.
In BI settings navigate to the the settings below and choose that IP range.
You shouldn't have to do anything in BI (at least I didn't).
My NIC with internet has one IP subnet range.
My camera NIC without internet just cameras has a different IP subnet range.
When I added the cameras I simply typed in the IP address of the camera.
The computer acts as a firewall of sorts so unless you do something like bridge the two NICs, they are separate.
My NIC with internet has one IP subnet range.
My camera NIC without internet just cameras has a different IP subnet range.
When I added the cameras I simply typed in the IP address of the camera.
The computer acts as a firewall of sorts so unless you do something like bridge the two NICs, they are separate.
Thank you to all that has replied.
cyberwolf_uk: For example, the main lan is 192.168.1.xxx with internet access and the camera lan is 192.168.2.xxx with no internet access, if I set the adapter setting to the camera lan, how does the machine send out pushover notifications?
wittaj: "The computer acts as a firewall of sorts so unless you do something like bridge the two NICs, they are separate." This is what I don't (didn't) understand, how does the machine know which nic to send out the pushover notifications on.
cyberwolf_uk: For example, the main lan is 192.168.1.xxx with internet access and the camera lan is 192.168.2.xxx with no internet access, if I set the adapter setting to the camera lan, how does the machine send out pushover notifications?
wittaj: "The computer acts as a firewall of sorts so unless you do something like bridge the two NICs, they are separate." This is what I don't (didn't) understand, how does the machine know which nic to send out the pushover notifications on.
The PC sends out pushover via the PC's LAN (192.168.1.XXX) to the Internet.
So there is nothing I need to do within the PC to route notifications, it will just know and do so?
Yes, it will look for the avenue to send it out automatically.
You will see the dual NIC is way easier than VLAN lol
This is so much easier lol, all the wasted time I wasted with VLANs and firewall rules. Plus, this keeps the traffic off of my firewall.
Absolutely!
When I was first entering this hobby LOL, I was thinking of going down the VLAN route.
I looked at the EdgeRouter X is claimed to be somewhere between 800Mbps to 1Gbps, but you see tests all over where people are only getting in the 700Mbps range and there was a lot of work to set it up properly.
On my isolated NIC, my cameras are streaming non-stop between 400Mbps. This is full-on, never stopping to take a breath sending of data with no buffering. Even if someone has a gigabit router, a 3rd of non-buffering 24/7 data will impact its speed.
I would just as soon not have that much video data going thru a device if it doesn't need to. Has to slow the system down.
So how can you test that a camera does or does not have an internet connection to the outside? I would like to test my current setup to confirm what I have is actually working. I ordered a nic card via Amazon and it will be here next week but would love to do some testing prior to changing things.
You can try to access it from outside the network.
You could set up the camera to send an email and if it fails, it isn't connected to internet.
I also point the camera back to itself for the Default gateway and DNS server - doesn't mean it isn't hardcoded internally that it will try another IP, but it doesn't hurt either.