Yes, you can.
A number of VeeaHub commercial and enterprise models are available for indoor and outdoor support. These models have different capabilities but can be deployed as a single mesh network.
VeeaHub models can be mixed in the same mesh network using wired and wireless capabilities. All VeeaHub devices, regardless of model, are designed to interoperate using vMesh technology.
vMesh automatically configures a mesh network over any combination of wired and wireless links. It discovers the topology and configures the network for optimum performance in the environment.
This flexibility allows you to tailor your deployment based on coverage needs, environmental factors, and available connectivity options. For example, you might use an outdoor‐rated VeeaHub model to extend coverage beyond building walls while using smaller or less expensive units indoors. Regardless of the combination, the VeeaHub nodes will discover each other and self‐organize into a unified mesh.
There is some consideration with wireless meshing for different VeeaHub models discussed later but there are no restrictions for wired topologies using different VeeaHub models.
Things to Keep in Mind
- All VeeaHubs must be registered to the same user group.
- vMesh will automatically adapt to differences in hardware capabilities and roles (e.g., gateway, edge, or relay).
- Firmware versions should be up to date across all devices to ensure compatibility and performance.
Mixing models provides greater flexibility in how and where you deploy your VeeaHubs, allowing you to build a network that meets your exact coverage and capacity requirements.
VeeaHub Models
VeeaHub models are summarized in the following table.
| VeeaHub Model | Ethernet Ports | 2.4 GHz Radios | 5 GHz Radios | Description | Mounting |
| VHE09 | 2 | 1 | 1 | Enterprise Indoor | Floor, Wall, Ceiling |
| VHE10 | 2 | 1 | 2 | Enterprise Indoor | Floor, Wall, Ceiling |
| VHH09 | 2 | 1 | 1 | Enterprise Outdoor | Wall, Pole |
| VHH10 | 2 | 1 | 2 | Enterprise Outdoor | Wall, Pole |
| VHC25 | 2 | 1 | 2 | Commercial Indoor | Floor, Ceiling |
| VHC25 PoE | 3 | 1 | 2 | Commercial Indoor | Floor, Ceiling |
All models optionally support 4G/5G cellular.
VHE09 and VHH09 units optionally support LoRaWAN.
VHC25 and VHC25 PoE also support Bluetooth and Zigbee.
The VHE09, VHH09, VHE10 and VHH10 are sometimes referred to using a combined term.
| VeeaHub Term | VeeaHub Models |
| VHE09/10 | VHE09, VHE10 |
| VHH09/10 | VHH09, VHH10 |
| VHE/VHH09 | VHE09, VHH09 |
| VHE/VHH10 | VHE10, VHH10 |
| VH09/10 | VHE09, VHE10, VHH09, VHH10 |
Considerations
There are some considerations for establishing wireless links between some VeeaHub models.
- Different wireless mesh protocols with VeeaHub models
- The VHC25 and VHC25 PoE use WDS wireless meshing
- The VH09/10 and VHH09/10 use IBSS wireless meshing
- The VHC25 cannot form a wireless mesh with VH09/10
- The VHE/VHH09 and VHE/VHH10 models have different 5GHz radios
- The VHE/VHH09 uses the full 5GHz band for wireless mesh
- The VHE/VHH10 uses the lower 5GHz band for wireless mesh by default
- The VHE/VHH09 cannot be sited upstream of a VHE/VHH10 in a wireless mesh
You can use wireless links between compatible models and wired links between any models. In this way a mesh can combine different wireless mesh protocols with wired connectivity. The remainder of this document gives more information on combining VeeaHub models in the same mesh.
VeeaHub Ethernet Ports
A VeeaHub supports PoE and high speed Ethernet according to the model.
| VeeaHub Model | Ethernet Ports | PoE Port Number | 1 Gbps Port Number(s) | 5/10 Gbps Port Number(s) |
| VHE09 | 2 | 1 | 1 | 2 |
| VHE10 | 2 | 1 | 1 | 2 |
| VHH09 | 2 | 1 | 1 | 2 |
| VHH10 | 2 | 1 | 1 | 2 |
| VHC25 | 2 | 1, 2 | ||
| VHC25 PoE | 3 | 3 | 1, 2 | 3 |
The VHE09/10 Ethernet RJ45 ports are located at the rear of the unit (underside if wall mounted).
The VHH09/10 Ethernet M12 ports are located at the underside of the unit when wall or pole mounted.
The VHC25 Ethernet ports are located on the underside of the base unit.
Additionally, the VHC25 PoE Ethernet port is located on the underside of the bottom stacker.
PoE Ports
This is a consideration when planning a deployment.
The VHE09/10, VHH09/10 and VHC25 PoE all have PoE ports.
If the preference is for PoE operation, then VHC25 base units (without PoE) are not suitable.
High Speed Ports
This is also a consideration when planning a deployment.
A high speed Ethernet connection may be preferred on the Gateway VeeaHub.
The VHE09/10, VHH09/10 and VHC25 PoE all have a single 5/10 Gbps Ethernet port.
VeeaHub Wi‑Fi Radios
The use of the 2.4GHz and 5GHz radios on the different VeeaHub models is shown below.
| VeeaHub Model | 2.4 GHz AP Radio | 5 GHz AP Radio | 5GHz Mesh Radio | Wireless Mesh Protocol |
| VHE09 | 1 | 1 (shared) | 1 (shared) | IBSS |
| VHE10 | 1 | 1 | 1 | IBSS |
| VHH09 | 1 | 1 (shared) | 1 (shared) | IBSS |
| VHH10 | 1 | 1 | 1 | IBSS |
| VHC25 | 1 | 1 | 1 | WDS |
| VHC25 PoE | 1 | 1 | 1 | WDS |
2.4 GHz Radio
All models have a single 2.4 GHz radio used to configure APs.
Currently, this cannot be used as a 2.4 GHz wireless mesh radio.
VHE09 and VHH09 5GHz Radio
The VHE09 and VHH09 have a single 5GHz radio that is shared for 5GHz AP and mesh operation. The bandwidth is partitioned between AP and mesh operation when both functions are enabled.
5GHz AP operation can be disabled if 5GHz mesh operation with a dedicated radio is required. Likewise, the 5GHz mesh can be disabled for dedicated AP operation with the 5GHz radio. Configuring dedicated AP or dedicated mesh operation avoids the need to share bandwidth.
A channel in the 5GHz band is selected using ACS (Automatic Channel Selection). The 5GHz mesh and/or AP operation then uses the selected channel. It is also possible to configure the selected channel manually.
VHE10 and VHH10 5GHz Radio
The VHE10, VHH10 and VHC25 have 2 5GHz radios each dedicated to mesh and AP operation. One radio uses the lower 5GHz band, the other the upper 5GHz band.
By default, the wireless mesh is assigned use of the lower 5GHz band radio. A channel in the lower 5GHz band is selected by the mesh using ACS. It is also possible to configure the selected channel manually.
The 5GHz AP operation is assigned the upper 5GHz band radio by default. Again, a preferred channel in the upper band is selected using ACS. It is also possible to configure the selected channel manually.
The 5GHz upper band may include DFS (Dynamic Frequency Selection) channels. In a given regulatory domain these are also designated for use by radar systems. The radio listens for radar signals and switches to a different channel if radar is detected.
The use of non‑DFS channels is preferred to avoid service interruption during normal operation. The wireless mesh is assigned to the lower band by default for this reason.
The radio assignment can be reconfigured so that APs use the 5GHz lower band radio, and the mesh uses the 5GHz upper band radio. However, this is a manual configuration and the VeeaHub does not switch radios automatically to scan the entire 5GHz band.
Wired Mesh
Any mix of VeeaHub model can be used for a wired mesh topology.
The wired mesh works seamlessly across all models with no interoperability considerations.
The only considerations are the Ethernet port speed and whether PoE is required.
High Speed Port
High speed ports may be preferred for the Gateway VeeaHub.
A high speed port is likely not required within the mesh. The only potential scenario is for an application which requires fast data transfer between peer VeeaHubs.
The VHC25 PoE, VHE09/10 and VHH09/10 support a 5/10 Gbps port.
PoE Port
PoE may be a requirement of the installation.
VHC25 PoE, VHE09/10 and VHH09/10 models can be used.
Wireless Mesh
There are 2 considerations when deploying a wireless mesh with mixed VeeaHub models:
- IBSS and WDS protocols
- Default Mesh Channels
Wireless Mesh Protocols
IBSS
An IBSS VeeaHub can form bidirectional wireless links with a large number of ad‑hoc peers.
For communication between distant neighbors and the wider internet, the most direct route via peer nodes in the mesh is found.
It is particularly suited to forming a wireless network over a large distributed area and direct communication between all neighboring peers is supported.
The VHE09/10 and VHH09/10 models support IBSS.
WDS
A WDS VeeaHub may have an upstream connection to a single peer and a downstream connection to multiple peers, resulting in a tree topology from a single root VeeaHub.
For internet access, VeeaHub traffic is routed back up the tree to the gateway root, and for peer communication, VeeaHub traffic is routed up and/or down the tree.
It is particularly suited to directional or linear deployments.
The VHC25 PoE and VHC25 base models support WDS.
Interoperability
WDS and IBSS are not interoperable. This means that VHC25 or VHC25 PoE models cannot form a wireless mesh with VHE09/10 or VHH09/10 units.
However, a VeeaHub mesh can include wireless links between units that support the same protocol. Wired connections must then be used between, for example, VHC25 and VH09/10 units.
Default Mesh Channels
In a wireless mesh, a VeeaHub must be capable of connecting to the 5GHz channel selected by an upstream VeeaHub.
Limitations
The only scenario where this is a problem is for an upstream VHE/VHH09 and a downstream VHE/VHH10.
The upstream VHE/VHH09 will select a channel from the whole 5GHz band. However, the VHE/VHH10 mesh radio only operates on the lower 5GHz band by default.
This means that if the VHE/VHH09 selects a channel from the upper band, the VHE/VHH10 will not be able to wireless connect. The VHE/VHH10 does not automatically switch radios to scan the upper band in the current software release.
Mitigation
There are a number of ways to avoid the upstream VHE/VHH09 and downstream VHE/VHH10 channel selection issue:
- Do not deploy a VHE/VHH09 upstream of a wireless VHE/VHH10
- Configure fixed lower channels on the upstream VHE/VHH09
Deployment Scenarios
Mesh deployments with the same VeeaHub model have no limitations and are not included here.
VHC25 PoE Gateway VeeaHub and VHC25 Mesh VeeaHubs (wired)
In this example a VHC25 PoE model is used as the Gateway VeeaHub.
Other units in the mesh are VHC25 base units.
The high speed Ethernet port is used for the WAN to increase the wired uplink bandwidth available to the rest of the mesh.
VHE09/10 Gateway VeeaHub and VHC25 Mesh VeeaHubs (wired and wireless)
This is similar to the previous section except a VHE10 is used in place of the VHC25 PoE model.
The high speed port on the VHE10 is port 2 and so this is used for the WAN. The VHE10 only has one spare LAN port so only one VHC25 is wired.
The VHE10 cannot form a wireless mesh with the VHC25 units. However, the 2nd VHC25 base can form a wireless mesh with the wired VHC25 base.
The VeeaHub mesh is agnostic to whether the transport is wired or wireless and all VeeaHubs are part of the same network.
VHC25 PoE Gateway VeeaHub and VHC25 Mesh VeeaHubs (wireless)
This is similar to the first scenario except the VHC25 base units form a wireless mesh.
The ports on the VHC25 PoE unit are then available for connected devices.
The uplink capacity accommodates traffic from the wired devices and all traffic from the wireless mesh.
VHC25 Indoor VeeaHubs and VHH10 Outdoor VeeaHubs (Wired and Wireless)
In this example, a wired connection links indoor VHC25 units to outdoor VHH10 units.
The indoor VHC25s use a wired and WDS wireless link.
The outdoor VHH10s use an IBSS wireless link.
The operation of vMesh is agnostic to the transport link and the network spans all VeeaHub units shown in the diagram.
VHE10 Gateway VeeaHub and VHE09 Wireless VeeaHubs
In this example a VHE10 is used as an upstream VeeaHub in a wireless mesh with a downstream VHE09.
The VHE10 selects a channel for the mesh from the lower 5GHz band by default, and the VHE09 is able to scan all channels in the 5GHz band in order to join.
There is no issue with the wireless mesh in a mixed VH09/10 deployment if the Gateway VeeaHub is a VHE/VHH10.
VHE09 Gateway VeeaHub and VHE10 Wireless Mesh VeeaHubs
In this example a VHE09 is used as an upstream VeeaHub in a wireless mesh with a downstream VHE10.
By default, the Gateway VHE09 can select any 5GHz channel for the mesh. If it selects a channel in the upper 5GHz band then
- the VHE09 Mesh VeeaHub will be able to scan, find the channel and join the mesh.
- the VHE10 Mesh VeeaHub will be unable to join as it is configured to use the lower 5GHz band by default.
To address this problem the options are:
- Do not use a VHE09 as a Gateway VeeaHub, use a VHE10 instead.
- Configure the VHE09 Gateway VeeaHub to only use lower 5GHz band channels.
It could be that the VHE09 has to be the Gateway VeeaHub, in which case the second option can address this issue.
VHE09 Upstream Wired VeeaHub and VHE10 Wireless VeeaHubs
The previous issue with a VHE09 Gateway VeeaHub applies more generally.
A wireless mesh can be used at any point in a VeeaHub network. If the upstream wireless VeeaHub is a VHE/VHH09 then any downstream VHE/VHH10s may be unable to join the wireless mesh.
The Gateway VHE09 or VHE10 VeeaHub is cabled to a VHE09 Mesh VeeaHub.
The Gateway VeeaHub either has wireless mesh disabled or the Gateway VeeaHub is out of wireless range for other VeeaHubs in the network.
The cabled VHE09 Mesh VeeaHub starts a wireless mesh so that other remote VeeaHubs are able to join.
In this case the remote VeeaHub is a VHE10. The same problem highlighted in figure 6 is seen and the remote VeeaHub is unable to join because the VHE09 has selected a 5GHz upper band channel.
So the issue raised in section 7.6 applies more generally. Any upstream VHE09 that can provide a wireless mesh link for a downstream VHE10 must have the mesh channels configured only for the lower 5GHz band.