LoRaWAN with >1 Conduits
- This topic has 3 replies, 3 voices, and was last updated 6 years, 2 months ago by .
Viewing 4 posts - 1 through 4 (of 4 total)
Viewing 4 posts - 1 through 4 (of 4 total)
- You must be logged in to reply to this topic.
Home › Forums › Conduit: AEP Model › LoRaWAN with >1 Conduits
We would like to deploy a single LoRaWAN with multiple Conduit gateways. This piece from Mbed https://os.mbed.com/docs/v5.8/reference/building-your-own-private-lora-network.html using TTN contemplates a router to send data from the gateways to the cloud. This piece http://www.multitech.net/developer/software/lora/lora-network-server/networking-conduits/ uses a Conduit to perform the routing function (ie, it uses a Conduit to act as the “Network Server”). It remains unclear to me, however, as to where the real LoRa network specific/management functions (ie, ADR) are supposed to happen.
If we set up a single private LoRaWAN with two Conduits configured to receive packets from the same group of xDots/mDots (ie, those part of the same network), would one act as a packet forwarder and one as a network server? And if so, can the one acting as network server receive packets from Dots as well as the other Conduit (configured as a packet forwarder)?
Yes the network server conduit can also have a packet forwarder running.
Does the Packet Forwarder require an Ethernet connection to send readings to the conduit functioning as a network server? How are the packets sent from the packet forwarding conduit to the network server conduit?
An Ethernet connection is required. Packets are forwarded via UDP.