IPVMU Certified | 01/06/15 09:47pm
Something else? I've always been a 192.168.1.x man myself.
Aren't the private subnets actually:
I typically use a 192.168.x.x scheme with a brand new install and when the customer doesn't necessarily care.
I have used a 10.x.x.x scheme for larger installs and to leave room for future growth.
We used to use 192.168.x.x but IndigoVision defaults to 10.5.x.x so it was easier to go with the flow.
Really Depends on who it is for.
VPNs usually allow me to build my own with in thier network
so if i choose the 192.168.0.0/1 or what , it wont matter
Some require I build with in thier protection platform.
10.0.0.0/ what ever i choose for the build.
If Im lazy then i use the default for the basic systems with alot of tricky passwords,user names
lots of number,capital,lower case, and letters , numbers so if you try you will really have to work hard at decoding and usually get tired of it.
IPVMU Certified | 01/07/15 01:51am
Something in the 10.xxx network other than 10.0.0.xxx. Much less likely there will be a customer network using that scheme. A router should not influence it since 95%(?) of the time the camera network is standalone and not part of a customer LAN or have an Internet connection.
90% of customer networks are in the 192 and 172 IP address range schemes.
I use what the client's requirements dictate. I prefer to utilize something in the 10.xxx.xxx.xxx network, but often the client's hardware limits the options available. Almost all of my installs require the ability to connect to the system from the Internet. In some cases, the client wants email alerts for some cameras when motion has been detected which necessitates the connectivity. If the hardware permits creating a separate subnet/network for the cameras, then I will do so. This adds the ability to create ACLs and firewall rules to restrict access according to the needs of the client.
It is worth noting that the "switch" manufacturer is not typically determining the network in use. A typical switch operates at layer 2 which has no knowledge of IP addresses. It is the layer 3 device (router/bridge) that determines the IP range that is capable of connecting to other networks. It is an easily confused situation given that many SOHO routers have built-in switch ports for the LAN.
IPVMU Certified | 01/07/15 04:54pm
Most of our installations are done using 192.168.1.X. In some situations the IT group at the customer site may want us to put our devices (whether camearas or door controllers) onto their network and in such cases we provide the MAC and they will proving an IP Address.
The 10.x.x.x subnet is shorter to type!
IPVMU Certified | 01/07/15 05:14pm
All of the above? We have no set standard and it will vary job to job but 192. and 10. are the most common by far. We will usually base it on the equipment being installed. If it is our own network I like to turn DHCP off and use a non standard subnet scheme.
If I am designing the camera network I almost always use a 192.168.187.xxx/24 network. Depending on camera count subnet will be changed to accomadate for the additinonal cameras. If I am doing a multi building install then we will have a different network at each location. I never use 192.168.0.xxx or 192.168.1.xxx because those are too common and sometimes can have negative effects when going in through a VPN.
IPVMU Certified | 01/14/15 05:30pm
we have taken over several sites in the past month where the previous dealer has kept the zeroconf (169.254.x.x) ip addresses that were assigned to the camera on intial startup...
Tailored IT Solutions
This is one reason I believe that IP camera installers should carry low level IP/networking certifications. The IP range you choose should be dictated by the size of the environment. Class A, Class B, and Class C addresses each allow a certain number of maximum hosts to be present in a subnet, or for a maximum number of subnets to be designated in a network. The class range should be chosen based on those determining factors. For virtually every install, this will fall into the Class C range of 192.168.x.x. It is good practice to have cameras on a separate subnet from any other traffic. This isolates security traffic. It also keeps the security equipment off of default plastic addresses so that it is harder to find. Additionally, because it's on a separate subnet, firewall rules become much easier to manage.
Tailored IT Solutions
VLANs are really for segregating traffic on the same subnet. I was suggesting separate address ranges using different subnet masks. It's fine if they run on the same hardware (though for fault tolerance, I typically like security on its own switch). Having separate subnets means that security traffic is not routable with LAN traffic unless specific firewall rules allow it. i.e. John Doe salesman can't hop on your WiFi hotspot and run an IP scan to find your cameras. Neither can a burglar in your parking lot.) If the traffic is segregated on different hardware, it also prevents disgruntled LAN users from attacking your security system from the inside. Aside from that, video traffic tends to come at a huge bandwidth cost for most networks so that should be a consideration as well.
Great Debut Guys
Keep on , Im learning a lot
Private lan? Add your own router then DHCP with reservations.
IPVMU Certified | 05/14/20 03:33pm
192.168.0.xxx has been all which I usually work with. For one testing site I was issued 172.16.0.xxx. Other than that, 192.168.0.xxx gets the jobs done.