You are here

Integration in to existing network for IP Camera's

3 posts / 0 new
Last post
Integration in to existing network for IP Camera's

Hey guys!

I know this has been posted and asked a few times in the forum but I'm still having some difficulty figuring this out. I have built two portable nodes (with one static node) utilizing Ubiquiti Bullet M2 HP's. I'm looking to integrate these with a network that is in the 10.240.x.x/24 range. My router is a cradle point MBR1700 trunked to a POE switch. I was able to assign the node attached to this network via NAT a static IP and view the nodes status page/change additional settings. I can see the IP's of the other two nodes on the mesh status page however, I cannot see any of the portable nodes status pages nor any device I attach to them.

I believe I need to set some static routing and modify some DNS settings in the cradle point to accomplish some integration into the AREDN network.

My router and switch defaults VLAN 1 as WAN traffic. I have other VLANS setup internally on the 10.240 networks for that earmark VOIP and IP Camera traffic (all VLANs are cross routed).

What I'm looking to do is view and record a remote ONVIF camera on one of the portable nodes via an NVR that is on the 10.240.x.x network.

Any suggestions on the best way to go about this?

More info.?
Hi. How is the remote cam connected? (directly to the remote node using the remote node for a DHCP; through a router in in access point/pass through; etc.) It sounds like you may have to do some port forwarding if the static node is dealing with NAT etc. What device is controlling the IPs on the static node side? It seems like the connection isn't getting through the 10.240.... (assuming this is inside a network on the static node) path across the mesh.
As an example:
I have a NetGear GS108PEv3 8 port, 4 of which are POE. I have 2 nodes (1 2.4GHz & 1 5GHz) DtD on the Netgear with a remote node (5GHz). The DHCP is turned off on the DtD 5 GHz and the Netgear is set to use an assigned IP so all IPs are controlled through the 1 2.4 node. The remote has its DHCP server running. All of my extras (laptop, RasPi, etc.) are DHCP clients from whichever node they are connected to and they can all communicate with each other.
I hope this helps some!
AE6XE's picture
kc1efx, Out of the gate there
kc1efx, Out of the gate there is a conflict with the devices since a node on the mesh may have assigned a node an IP address in this range.   You would not be able to communicate with that mesh node directly or other mesh services and hosts that may have an IP address conflict.    The IP addresses are derived from the MAC of the wireless interface on the device.     

If you want to roll the dice, assuming there will be no conflict,  then the way to do this is in basic setup of the node, make the node's LAN subnet, change the "LAN Mode" to 'NAT'.  Then set the IP Address and netmask for your network.  Connect the node's LAN (untagged) to your network.  incoming connections from the mesh would require a port forward across this NAT to reach your devices, however all the devices on your network could access everything on the mesh.    All your devices on the network would need to manually define a default route that points to the mesh node's LAN IP address you assigned.  

Joe AE6XE   

Theme by Danetsoft and Danang Probo Sayekti inspired by Maksimer