Once again I need some BI help. Networking

Sparkey

Pulling my weight
Joined
Apr 3, 2015
Messages
237
Reaction score
159
My BI server has 2 network interfaces. The first is 192.168.1.x. this is the interface that's connected to the internet. The second interface is 192.168.5.x. This is the interface that the ip cameras are on and they are not connected to the internet except through BI.

I just set this new server up and it's showing the web server as being on 192.168.5.x which is entirely wrong and I cannot change it no matter what I do.

Now here's the stupid part. Locally I can access the web server via 192.168.1.x even tho BI isn't showing that subnet in it's config.

I just ran through the wizard and it changed nothing. As is I cannot access the cams remotely obviously because 192.168.5.x isn't routed to the internet.

My previous server set the web server ip correctly. I have no idea why this one didn't.

If someone could tell me how to correct this I'd be forever greatfull.

TIA
 

TonyR

IPCT Contributor
Joined
Jul 15, 2014
Messages
16,433
Reaction score
38,153
Location
Alabama
Some clarity needed, IMO:
The second interface is 192.168.5.x. This is the interface that the ip cameras are on and they are not connected to the internet except through BI.
OK, cams are on NIC 192.168.5.x
I just set this new server up and it's showing the web server as being on 192.168.5.x which is entirely wrong....
OK, if the cams are on NIC 192.168.5.x......how is that "wrong" for the web server?


Is your setup anything like this below?

Network Topology 2NICs.JPG
 

Sparkey

Pulling my weight
Joined
Apr 3, 2015
Messages
237
Reaction score
159
Thanks for replying Tony. I managed somehow to stumble upon the solution. It was in a drop down that listed 192.1.x. I selected it and am now able to access the BI locally. Still have an issue with remote access but I'll work through it.

In answer to your question, I'd rather not expose my cams directly to the internet so they are on a subnet, 192.168.5.x which is not connected to the internet. Blue Iris is on 192.168.1.x and does have access to the internet and the cams through a second NIC. By connecting to BI web server I can access the cams both locally and remotely (as soon as I sort out the problem with OPNsense).
 

wittaj

IPCT Contributor
Joined
Apr 28, 2019
Messages
24,428
Reaction score
47,544
Location
USA
Um, Tony's diagram is showing cameras not exposed directly to the internet and are on a different subnet...
 

Sparkey

Pulling my weight
Joined
Apr 3, 2015
Messages
237
Reaction score
159
Some clarity needed, IMO:

OK, cams are on NIC 192.168.5.x

OK, if the cams are on NIC 192.168.5.x......how is that "wrong" for the web server?


Is your setup anything like this below?

View attachment 158220
Because I cannot access 192.168.5.x from any other computer unless it has a second NIC, they are all on 192.168.1.x. And then I can only access the cams directly and not through BI. If I connect to the web server via 192.168.1.x then it works like it should. It seems to me that the web server only works through the "primary" NIC, the one that can access the Internet.
 

wittaj

IPCT Contributor
Joined
Apr 28, 2019
Messages
24,428
Reaction score
47,544
Location
USA
Because I cannot access 192.168.5.x from any other computer unless it has a second NIC, they are all on 192.168.1.x. And then I can only access the cams directly and not through BI. If I connect to the web server via 192.168.1.x then it works like it should. It seems to me that the web server only works through the "primary" NIC, the one that can access the Internet.
That is the way it works. The web server is your BI computer that is on the LAN with internet.

But you can access the 192.168.5.x from any computer on your 192.168.1.x by RDP or TeamViewer or any other type of remote desktop by remoting in to your BI computer on the 192.168.1.x LAN.
 

Sparkey

Pulling my weight
Joined
Apr 3, 2015
Messages
237
Reaction score
159
That is the way it works. The web server is your BI computer that is on the LAN with internet.

But you can access the 192.168.5.x from any computer on your 192.168.1.x by RDP or TeamViewer or any other type of remote desktop by remoting in to your BI computer on the 192.168.1.x LAN.
True, but it's much simpler to forget about 192.158.5.x and just deal with BI. When I need to I remote into the BI server to access BI itself but the cams I never have to bother with.
 

wittaj

IPCT Contributor
Joined
Apr 28, 2019
Messages
24,428
Reaction score
47,544
Location
USA
I was just pointing out your incorrect statement "Because I cannot access 192.168.5.x from any other computer unless it has a second NIC" as the other computers don't need a second NIC to access the 192.168.5.x subnet as they can remote into the BI computer to access that aubnet of needed.
 

Sparkey

Pulling my weight
Joined
Apr 3, 2015
Messages
237
Reaction score
159
I was just pointing out your incorrect statement "Because I cannot access 192.168.5.x from any other computer unless it has a second NIC" as the other computers don't need a second NIC to access the 192.168.5.x subnet as they can remote into the BI computer to access that aubnet of needed.
Yea, BI is the only computer that has access to 192.168.5.x, the rest just access the web server to see the cams. It's been like this for years. I recently upgraded my BI computer because the old one was struggling to manage 11 cams. The new one is much better. but I still have issues to work out. The old one worked perfectly but I got tired of the herky jerky video. FPS stays pegged at max with the new one.
 
Top