I've had BI up for a couple of years now with 15 h.264 and h.265 cameras, and I bought an Annke 5MP to replace one of the older h.264 models. I ran their SADP software network camera discovery tool and it said the camera was set to port 192.168.0.167 (attachment #1). I don't think I have anything as high as 167, so I hooked up in place of an older camera at 192.168.0.113, and told BI to use 192.168.0.167 (attachment #2). There's something (lots, evidently) that I don't understand about networking and subnets. My internet connection router has 4 ports on it and one of them goes to an 8-port switch, and the BlueIris computer and a 16 POE port switch are plugged into that, and all 15 cameras work except the new one. Sorry so stupid - can anybody tell me what's wrong? Maybe I can find some freeware to draw me a picture of the network.
Trying to add a new camera to Blue Iris
- Thread starter BillRitz
- Start date
Flintstone61
Known around here
your allowed addresses go up to 254. the networking scheme you are in has addresses from 192.168.0.1 to 192.168.0.254
So you can type that address into a browser and log into the camera. and then assign a non-manufacturer default Ip ( usually Static) of your choosing, ( stay away from ...108 though, thats the Dahua and OEMS like Amcrest default NVR and Cam address.
One of the very basic rules in IP networks is that every... logical network, no matter how small or big it is, must have a network identifier address and a network broadcast address. To make things simple, the engineers that designed all the above though it would be a great idea to use the first and last addresses of each logical network to do their job!
So, as you've already correctly guessed, networks ending in .0 or .255 are not usable… in most cases! The reason for this is because we tend to allocate full Class C type addresses to our networks, making it obviously very simple for us to administer.
A standard Class C network consists of 256 addresses (0 to 255 inclusive), of which one is the network address (.0) and the other is the network broadcast address (.255).
To help make this clear, if we selected network address 192.168.0.0/255.255.255.0 for our office, then we can say that:
The network identifier would be 192.168.0.0
The broadcast address would be 192.168.0.255
Valid (or usuable) ip addresses would be 192.168.0.1 to 192.168.0.254.
www.techtarget.com
.
So you can type that address into a browser and log into the camera. and then assign a non-manufacturer default Ip ( usually Static) of your choosing, ( stay away from ...108 though, thats the Dahua and OEMS like Amcrest default NVR and Cam address.
One of the very basic rules in IP networks is that every... logical network, no matter how small or big it is, must have a network identifier address and a network broadcast address. To make things simple, the engineers that designed all the above though it would be a great idea to use the first and last addresses of each logical network to do their job!
So, as you've already correctly guessed, networks ending in .0 or .255 are not usable… in most cases! The reason for this is because we tend to allocate full Class C type addresses to our networks, making it obviously very simple for us to administer.
A standard Class C network consists of 256 addresses (0 to 255 inclusive), of which one is the network address (.0) and the other is the network broadcast address (.255).
To help make this clear, if we selected network address 192.168.0.0/255.255.255.0 for our office, then we can say that:
The network identifier would be 192.168.0.0
The broadcast address would be 192.168.0.255
Valid (or usuable) ip addresses would be 192.168.0.1 to 192.168.0.254.
Can you assign an IP address ending in .0 or .255? | TechTarget
Learn how to assign an IP address ending in .0 or .255 from networking fundamentals expert Chris Partsenidis in this Q&A.
But in my attachments the SADP tool from Annke shows .167, and I set the address in BI to .167, so what am I doing wrong?
Flintstone61
Known around here
What happens if you surf to that address on Edgernet Explorer or Chrome, Or whatever browser you use on the BI computer
Flintstone61
Known around here
Flintstone61
Known around here
Mike A.
Known around here
- May 6, 2017
- 4,199
- 7,067
The Amcrest cams don't come with a static address; rather, they come by default using DHCP. It pulled the .167 address from the DHCP server on your router.
Looks like you're using the same subnet if your other cam was working at 192.168.0.113 so that's probably OK. Not sure what's/how it's not working but you need more to the connection string in BI. Where it says Main, try adding the string below:
Generally better to set the address to static at some point once you have it up and running.
Looks like you're using the same subnet if your other cam was working at 192.168.0.113 so that's probably OK. Not sure what's/how it's not working but you need more to the connection string in BI. Where it says Main, try adding the string below:
Code:
/cam/realmonitor?channel=1&subtype=0&unicast=true&proto=OnvifGenerally better to set the address to static at some point once you have it up and running.
Last edited:
Flintstone61
Known around here
I wonder what Annke Ships as the default IP and Pass?
It's kinda funny how if you plug a new Dahua or Empiretech or Amcrest into a POE switch right outta the box, you'll find it at 192.168.1.108,
But if you take the same camera and hook it to an NVR, it will be assigned an Address on the 10.10.x.x range.
It's kinda funny how if you plug a new Dahua or Empiretech or Amcrest into a POE switch right outta the box, you'll find it at 192.168.1.108,
But if you take the same camera and hook it to an NVR, it will be assigned an Address on the 10.10.x.x range.
Flintstone61
Known around here