Automatic configuration of a wired mesh
VeeaHubs can be connected into a mesh using Ethernet cable as easily as they can be connected using the default wireless mesh. The wired mesh is automatically configured to provide full connectivity and redundancy. The mesh can include both wired and wireless connections between VeeaHubs or it can be entirely wired or wireless.
The first VeeaHub in the mesh becomes the gateway node (MEN), as normal. VeeaHubs can then be connected into the mesh using cables and the mesh will configure itself as necessary.
If the mesh is intended to be entirely wired, the wireless mesh can be turned off using the vMesh screen in Node Manager or VeeaHub Manager, but this is not essential.
A variety of wired topologies can be supported, and specific examples are described below.
Note: MEN = gateway/manager node, MN = other node in the VeeaHub network.
A. In this example, Veeahubs in a wired mesh are directly connecting to an external router with active DHCP server. The MEN provides network address translation (NAT) to the WAN. IP addresses for devices connected to the VeeaHubs are assigned by the MEN.
When a VeeaHub is connected into this network the port of connection shows ‘DHCP conflict’ in VeeaHub Manager and Node Manager, because there are two DHCP servers on that port. This is a warning to the user that the LAN role on that port is automatically disabled. This does not cause problems in normal use, but may cause a problem if the network goes down and is then restored and the mesh comes up before the WAN. For this reason, we recommend that the LAN function is manually disabled by the user on this port as a precaution. To do this, go to the Physical Ports option in VeeaHub Manager or Node Manager.
B. In this example, VeeaHubs in a wired mesh are directly connecting to an external router with active DHCP server. The VeeaHub mesh is configured with a bridge connection to the WAN. IP addresses within the mesh are assigned by the DHCP server on the external router, so the VeeaHubs are part of the WAN.
C. In this example, the VeeaHubs are connected to the LAN of the MEN. The MEN can be NAT or bridged to the WAN. The MNs can be connected to the MEN using a switch if there are too many VeeaHubs for the available ports on the MEN.
D. In this example, the VeeaHubs are connected to the LAN of the MEN. This is similar to C, but in this case the VeeaHubs are daisy-chained to the MEN.