IP Camera Subnet

My router is set up with a 192.168.1.1 address scheme.

I would like to create a separate subnet on port 4 of 192.168.2.1 just for ip cameras.

The reason I want to do this is simply to keep the ip camera traffic away from the main subnet so the cameras don’t slow down the network.

I would like the 2 subnets to be able to talk to one another and “see” one another, but not effect bandwidth or cause bottlenecking or any type of network slowdown.

Basically segregating the camera traffic from all other traffic.

Is this the correct way to accomplish this?

You should maybe check first where the network is choking, where is the bottleneck.

The network is not bottlnecking… I don’t have the ip cameras set up yet.

I just want to do it right from the beginning so I don’t have any bottlenecks.

Draw the network picture for yourself. Include the expected data volumes flow and you will see. Maybe you don’t need to do anything special…

I would like to set it up regardless.

If anyone can help me out with what I am asking I would appreciate it.

just remove port 4 from the switch (master port) or bridge

then ip adresses add 192.168.2.1/24 to port 4

that is all you need to do i think

Yes, I believe that is correct.

My question remains, if I do that will it ease the traffic on subnet 192.1681.1?

For those of you that do this with ip cameras, is this how you are doing it?

Thanks.

Yes, as long as the 2 ports are not bridged or switched, they will be routed. When routing it keeps the network on separate broadcast domains. You are still limited to the capacity of the MikroTik, but for a SOHO you should be fine.

I plan on connecting the ip camera port to a poe switch which will connect to the nvr and the ip cameras. The switch will not have any other traffic.

Does this also help with easing traffix on the 192.168.1.1 subnet?

in the beginning there where hubs , then your trafic goes to all devices in the network.

since the invention of switch the trafic only goes to the devices that need the trafic … so if you put a POE switch in between and also connect the NVR to it, than there wil be no trafic going to the main switch. unless someone is watching

Some NVR systems have 2 ethernet ports, then you can create a separate network …

You are on the right track. For our IP cameras we just created a VLAN and assigned the VLAN to a port. Then the cameras are on their own broadcast domain. If you want the two subnets to communicate with each other just put the VLAN on the master port of your primary subnet and then the port will be able to route traffic between the two subnets.

In my opinion VLANS are the way to go, I use they to separate cameras and wifi etc.

Why not put the cameras on a lan… say you make port 3 a different subnet for the cameras, like 192.168.2.1, and connect it to a switch.

Port 2 would be 192.168.1.1, which would be normal traffic. Port 3 would be on it’s own subnet for the cctv.

Wouldn’t they still be able to communicate?

Why do you need a vlan if you can do it that way?

That may work just fine too. I am just a fan of VLANs since I trunk multiple VLANS traffic on a single physical port when the need arises. You would have to have a heck of a lot of traffic to bog down even a single gigabit port… And even if I get to the point of reaching those limits I will just trunk my 10g fiber port :slight_smile:

How many cameras are you talking about implementing?

No more than 16 cameras at max 3mp each.

I see your point about trunking. I would never need to trunk because I’m going direct to the poe switch which is connected to the NVR and ip cameras.

In theory, is my way (like I invented it!) a better solution for bandwidth and traffic separation, or does it not really matter?

With that many cameras I don’t know that it matters. I just like the flexibility of VLANS I can assign them to any physical ports that I want and never have to physically move cables around. Now I am dealing with a handful of different subnets that I am trying to manage so my application is a little different. You are right thought just assigning a physical port on the router to handle a specific subnet is fine.

Now in order for them to communicate I think you will have to bridge the two physical ports. If that is the case remember that bridging is logical and eats at your processor speed… I may be wrong about needing a bridge, I have not experimented with doing it that way before.

You are right. If I have to bridge them to make them communicate, then it’s not worth it.

Does anyone know if I will have to bridge them?

If you put cameras and nvr on their own switch, the traffic will not leak outside as the switch will send the traffic to the port it belongs to. Switches learn connected mac addresses so they are not acting as dumb hub. No need to set anything. No need of separate network addresses.

Are you saying I can use the main subnet 192.168.1.1 for everything, and because I am sending the ip cameras and nvr to a poe switch there will be no effect whatsoever on the network?

If that’s true, why do people put things on different subnets and vlans? You could just have each system go to a switch.

I guess the answer may be because you would run out of ip addresses.

You need separate networks if you want to secure them differently and each against the others. Or in case the cameras will broadcast instead just reply to the requests of nvr.

For me it’s more a question of traffic, not security. Since that’s the case, in a perfect world, what is the best solution?

different subnet on port 3?

Vlan?

same subnet for everything?