Introduction

In this document, we are going to see the full VeeaHub deployment in an existing network environment that provides an internet connection. No specific knowledge about Veea eco-system is required, but a VeeaHub and an account on Control Center will be necessary to perform the steps.

Use case

Let’s imagine a existing building situation where a network infrastructure is already available. And for this scenario, this network infrastructure doesn’t provided any internet connectivity. The system administrator will select a VeeaHub as the IoT platform that will handle the LoRaWAN local coverage.

In this topology, the VeeaHub is set in Bridge mode LAN.

WAN and LAN support

A VeeaHub gateway node (also called the MEN) is connected to the existing LAN as a client. Its local LAN takes its IP addresses from the DHCP server in the existing LAN router. Or, in case of no DHCP server, the administrator defines a static IP that satisfy the LAN router. Therefor, any peripheral connected to the VeeaHub LAN will be attached to the existing building LAN. Please see this page to configure a bridge mode: https://veea.atlassian.net/wiki/spaces/~738842769/pages/304516202597/Configure+a+bridge+mode

In Bridge mode, the WAN and the LAN are bridged, the VeeaHub will automatically detect which of its ethernet port is connected to the work and auto-configure itself appropriately.

All the steps to setup this topology are covered in the next Section.

All the details about the Veea Mesh configuration can the found here: https://support.veea.com/hc/en-us/article_attachments/17755798668563

VeeaHub configuration

Once your VeeaHub is up and running, you can access the administration space in the Control Center.

As explained earlier, in Bridge mode, the WAN and the LAN are bridged. The VeeaHub automatically detects which of its ethernet port is connected to the work and auto-configure itself appropriately. So, the VeeaHub can be connected with either Port 1 or Port 2 to the existing Network. But, please keep in mind that only Port 1 has PoE.

Extending the LoRaWAN coverage

A single LoRa VeeaHub has a limited coverage based on the local environment (outdoor/indoor, wall thickness, etc.). Based on the coverage target of a specific area, more than one LoRa VeeaHub might be necessary.

Using the VeeaHubs meshing capability (over Wifi or over Ethernet), one can add more LoRa Hubs to extend the local LoRa coverage. In the case of an existing network (not a VeeaHub) supporting the local LAN, any additional VeeaHub will be automatically configured as an MN and will require only a direct ethernet connection to the existing LAN on any of its port.