How to make equipment from different Vlans/Subnets interact?

Question

Computer networks

Good afternoon Sensei!
There is a level 3 router with virtual interfaces:
-Vlan 10 - 192.168.10.1/24
-Vlan 20 - 192.168.20.1/24;
Computer 192.168.10.2/24 gw 192.168.10.1;
V/camera 192.168.20.2/24 gw 192.168.20.1
The essence of the problem is that the Comp pings the camera and enters the Web interface, but the CMS, IVMS 4200, Orion Video Pro, etc. applications do not find it, scanning the network automatically, they also do not see when manually entering IP. Probably because they only scan the adapter's subnet?
But if there are too many cameras or there is a need to "drive" the stream from another network, what should be done in this case? Do the hosts need to be kept together with the cameras? Maybe someone came across?

Answer 1

I constantly use static routing and separation of cameras in a subnet using vlan. Camera search Software, proprietary and multi-vendor, does not work outside its network segment as it uses ARP (Hikvision), Multicast/uPnP (Dahua) mechanisms. But for the camera to work, only IP accessibility is needed, there is no special "starting information" that will pass only within its subnet. Check firewalls, check routes, check correct gateways on camera. If you have an l2 + or l3 core switch, then try transferring inter-area routing to it, it is not very clear how you have connected the l2 network to the router there.
I have 500 cameras from different manufacturers in 10 vlans that work on different software and do not complain. And if you dump them into the same network, then you get a broadcast ass, there is up to 20% of parasitic SHV traffic, securos, for example, from this, pictures start to flicker

Answer 2

In general, all cameras work with software or according to their own protocols (respectively, with their own dedicated software) or, if with other VMS, then according to generally accepted ones, this is often rtsp or onvif.
For example, the date port for the Hikvision protocol is 8100 or sometimes 8000, their IVMS 4200 works just for them.
In general, all that needs to be done here is, as already mentioned above, to make sure that the ports necessary for work are open and allow data to pass through. And which ports it depends on the method of adding (protocol).

Answer 3

I will assume that between firewall subnets with port forwarding, i.e. you need to open access on the onvif port to another subnet, perhaps also nat on the gw subnet

Answer 4

MihaTronik , What Monday brought us. First things first I turned off the firewall, nothing changed .. I'll skip the uninteresting part. Now it
's interesting. An automatic search in Orion did not find anything, BUT by unchecking Onvif and entering the address manually, I was able to add it to the system and specify the manufacturer. Vuolla Hick's camera *.20.3 wound up on Orion *.10.2. But this is Hick, and there is simply no LTV in the list of vendors of the car. I tried to sort out Hick models for LTV - nothing.
Do you know how it turned out to start Hick? When the camera is initialized in the subnet of the Bolid, the LTV vendor is determined automatically, the camera starts up. Then we return the camera to Vlan 20 and correct the address of the previously initiated camera from Vlan 10 to *20.2 in Orion and it starts up
. . In addition, this solution is only with the car, but what about CMS, IVMS, etc. software.
Are there people whose servers and cameras in different Shuttlecocks work fine?