TTN network stack V3 central 1


soon to be released… the long awaited TTN V3 stack



webinair stack V3 -
slides -
forum search -

more txt …

Class C Status
The Things Network Stack V3
OTAA Join Takes A Long Time - Murata CMWX1ZZABZ-091 and LAIRD RG191 Gateway
(Joerg Wende) #2

Just wondering about the timing of V3 development - I know it will be ready if its ready - but are there any new plans or estimates ?



htdvisser on Slack :
There has been long discussions about what to do with gateway locations. For now we won’t make any changes, but with our upcoming v3 stack, we will rely on the registered location only, and not on the location that the gateway may or may not send (we will just ignore it completely).

The reasons for this are that (1) many gateways don’t have a GPS, or are located in places with bad GPS coverage and thus have an inaccurate location (2) people started hard-coding GPS locations into config files that are difficult to update and may therefore be outdated.

For the relatively rare case of mobile (moving) gateways we still have to define a “spec”.

(Verkehrsrot) #4

Will this work with lmic?
Lmic does not support 1.1 until now (?)


On Slack today :

We’re all really looking forward to the entire v3 stack. It will make so many things easier and better.
It’s indeed completely written in Go (including the Gateway Agent), so it can be cross-compiled for many CPU architectures (including several arm versions).

It’s still too early for nightly builds, I can imagine it will still take several weeks, maybe months before everything is working properly.

We want to open up the source code around this time (Q2), but the actual launch is planned for Q4 this year, so we still have enough time to actually make it work on all gateways.

(Hylke Visser) #6

From @johan’s presentation:

(Acourt) #8

Will the release for v3 contain the source code?


Almost one year back we decided to rebuild our backend server from scratch. The 3rd generation of the network stack takes into account all the lessons learned on security, scalability, speed and developer friendliness.

The future is Connected Private Networks. The V3 stack is designed to run well privately, either in a private cloud or on-premises. Private networks can use the long-awaited feature of exchanging traffic (peering) between public and private networks. This allows any private network to use community coverage while contributing back to the community network.

Want to know more? Read along.