VeeaHubs support both wired and wireless vMesh configurations, giving you flexibility in how you deploy and connect your devices. Wired meshes offer enhanced performance, reliability, and reduced wireless congestion—especially useful in environments with dense interference or strict connectivity requirements.
Seamless Integration
You can connect VeeaHubs together using Ethernet cables just as easily as using the default wireless mesh. When connected by wire, the mesh configures itself automatically to establish full connectivity and failover redundancy.
The mesh can be:
- Entirely wireless
- Entirely wired
- A hybrid of both
Regardless of connection type, the system automatically detects and integrates all nodes.
Gateway Assignment
The first VeeaHub in a mesh becomes the Gateway Node. Additional VeeaHubs are termed Mesh Nodes and can be connected directly to the gateway or to each other, forming daisy-chained or branched topologies.
Turning Off Wireless Mesh (Optional)
If you’re setting up an entirely wired mesh and wish to disable the wireless mesh function:
- Go to the vMesh screen in either Control Center or the VeeaHub Manager (VHM) mobile app
- Disable the wireless mesh option
Note: Disabling the wireless mesh is not required for wired operation—it’s purely optional for performance tuning or RF interference reduction.
VeeaHub Ports
A VeeaHub Ethernet port can be configured for a number of roles.
| Port Role | Description |
| WAN | A port on the Gateway Node connects the mesh to an upstream network |
| LAN | A port on a Gateway or Mesh Node for use by one of up to 4 LAN networks |
| No role | None of the roles above are assigned but can be used for mesh networking |
As well as the roles above, all ports are used simultaneously for mesh networking.
WAN Port Role
The WAN port provides the upstream connection for the VeeaHub mesh and is the gateway to the external network.
A VeeaHub does not have a dedicated WAN port. This is because:
- A WAN port is configured on a Gateway VeeaHub and not on a Mesh VeeaHub
- VeeaHub ports have different capabilities and either may be preferred
The VHE09/10 has a PoE 1Gbps port as well as a 5/10Gbps non-PoE port. Some networks may use a PoE port for WAN, others a high speed port.
The WAN port is assigned automatically when the Gateway Node is enrolled. Each port is checked in turn to find an upstream DHCP server. If none is found then port 1 is selected as the default WAN.
LAN Port Role
A LAN port connects the external network or client device to one of four LAN networks operating across
the mesh.
Any port on a Gateway or Mesh Node can be used as a LAN port and connected to an external
network.
However, there are reasons why it may not be possible to use a LAN port.
- Bridging the port may result in a DHCP conflict
- A Layer 2 loop may result if the port is bridged
A DHCP conflict results if both the internal LAN and external network have active DHCP servers. The
servers will be managing different IP subnets and clients will likely lose internet access.
To prevent 1, the VeeaHub performs a DHCP conflict detection procedure.
A Layer 2 loop occurs if the physical network connects back on itself. For example, two VeeaHubs may
have LAN ports connected to the same external LAN segment.
To prevent 2, the VeeaHub performs a Layer 2 loop detection procedure.
For a LAN port to connect to the external network, both DHCP conflict detection and Layer 2
loop detection must complete without identifying any issues.
If a problem is detected then no internal connection between the VeeaHub LAN and Ethernet port is
made. The Ethernet LAN port is still physically cabled to the external network.
VeeaHub LANs
A VeeaHub mesh supports up to 4 user‑defined LAN networks that operate across the mesh according
to a WAN mode configuration.
| WAN Mode | Description |
| Routed (NAT) | A new LAN subnet operates over the mesh with NAT egress to the external WAN |
| Bridged | The WAN port is directly bridged, extending the WAN network across the mesh |
Routed (NAT) LAN
A routed (NAT) LAN provides a separate network for client devices. NAT is used for IPv4 LAN traffic to
and from the external WAN network.
The VeeaHub runs a DHCP server that provides IP addresses to connecting clients. The pool of IP
addresses that can be assigned is defined by the configured IP subnet.
When the first VeeaHub in the mesh is enrolled it becomes the Gateway Node and a default LAN is
automatically configured. This is a routed (NAT) LAN.
The IP subnet that is selected is specific to the model of the Gateway VeeaHub.
| VeeaHub Type | Primary Subnet | Secondary Subnet |
| VHE09/10, VHH09/10 | 10.100.1.0/24 | 172.20.1.0/24 |
| VHC25, VHC25 PoE | 10.100.21.0/24 | 172.20.21.0/24 |
During enrolment or a restart, the VeeaHub checks the external subnet of the WAN network. If it detects
a conflict with the primary subnet, the secondary subnet is used instead.
The Gateway VeeaHub runs a DHCP server to manage the LAN IP subnet.
A routed LAN is preferred if:
- The external network is a simple gateway providing a single IP address to a downstream device.
- A Guest network is configured to allow Wi-Fi access to visiting wireless devices
Bridged LAN
A bridged LAN is used to extend the external WAN network across the VeeaHub mesh. Clients that
connect are on the same Layer 2 segment as the external WAN network.
Layer 2 procedures for devices connected to the VeeaHub LAN will work in exactly the same way as for
devices connected to the external network.
This includes DHCP IP address assignment. Clients connecting on the VeeaHub LAN receive an IP
address from a DHCP server running on the external WAN network.
LAN Clients use a gateway IP address on the WAN, provided in the DHCP response. The VeeaHub is
not responsible for assigning IP addresses on a bridged LAN.
The WAN and the LAN networks are effectively one and the same.
A bridged LAN is preferred if:
- The external network has its own DHCP server supporting a larger subnet and this network is to be extended
Supported Topologies
The vMesh system supports multiple Ethernet configurations and automatically adapts regardless of the topology. Up to 4 LANs can be configured and these co-exist across the mesh.
The examples presented here can be combined in any manner and vMesh automatically adapts.
There are different considerations for a routed (NAT) LAN compared to a bridged LAN.
For a bridged LAN, the internal LAN and external WAN network are the same.
Routed (NAT) LAN
For a routed LAN, the internal traffic and external WAN traffic cannot use the same Layer 2 segment and must be kept separate.
Daisy Chain
In a daisy chain topology, VeeaHubs are cabled together directly.
LAN traffic uses the wired daisy chain directly. The WAN network and LAN network are physically separated and use different VeeaHub ports.
The physical separation means that Layer 2 and the DHCP subnets are not in conflict.
In the diagram below, Wi-Fi devices are connected to the LAN.
A wired device can also use the spare port on the last VeeaHub in the daisy chain.
Dedicated LAN Switch
With a dedicated switch on the Gateway node LAN port, routed LAN traffic can use the switch and its ports directly.
The laptop can be directly connected to the switch port to use the VeeaHub routed LAN.
The switch also frees up ports on Mesh Nodes and a laptop can be connected to a spare VeeaHub LAN port.
Existing WAN Switch
In this topology, the Gateway and Mesh Nodes are connected to the same network using an existing switch.
In the diagram below, the laptop and mobile devices connect to the LAN using a VeeaHub Wi-Fi access point.
VeeaHub LAN traffic is isolated by a VXLAN overlay to encapsulate LAN packets sent over the network.
- vMesh automatically determines that the routed LAN requires a VXLAN for this topology
- vMesh is plug-and-play requiring no external network configuration regardless of topology
- a VLAN overlay can be used instead, but requires matched VeeaHub and managed switch configuration
If the laptop is cabled to the switch it uses the WAN network.
If the laptop is cabled to a VeeaHub LAN port it uses the routed LAN network.
Bridged LAN
Here, the WAN and LAN ports on the Gateway Node are bridged internally, extending the WAN network.
The LAN network is a daisy chain with ports also connected internally on the first Mesh Node.
The laptop can also use a spare port on the last VeeaHub in the daisy chain.
Here, a dedicated switch connects the Gateway Node to the Mesh Nodes.
A wired client can be connected to the switch port.
The switch also frees up ports on the Mesh Nodes that a wired client can use.
The Gateway and Mesh Nodes can also be connected to an existing switch used by the WAN network.
Unlike the routed LAN, where a VXLAN overlay has to be used to encapsulate the traffic, the bridged LAN traffic can use the external switch and Layer 2 segment directly.
The laptop can be cabled to the switch.
Or a VeeaHub LAN port and in both cases receives an IP lease from the external network.