V3 local_conf.json "serv_gw_key": "what value?"

Just having a quick experiment with migrating my v2 gateway to v3 (obviously without deleting my v2 definition so I can swiftly swap back)

However mp_pkt_fwd is hitting an issue with: “ERROR: [TTN] Connection to server “eu1.cloud.thethings.network” failed, retry in 30 seconds”

I have managed to convince myself that the issue is the value in local_conf.json “serv_gw_key”: “value”

With v2 the Gateway Key is generated for me by the console and is of the form ttn-account-v2.blahblahblah

But how do I generate an equivalent Gateway Key in v3 to go into my “serv_gw_key”: “value” ?

I see “Add API key” function in the v3 console but obviously cannot see the wood for the trees :wink:
Do I use one of those to generate a Gateway Key ? And if so which?

Any comments much appreciated!

(If I can just satisfy myself that the migrated gateway can talk to eu1.cloud.thethings.network I will feel much happier about the looming v2 switch off, but I’ll keep the v2 gateway running for as long as possible)
Thanks

You need an API key with

Link as Gateway to a Gateway Server for traffic exchange, i.e. write uplink and read downlink

For the host entry you need to append :1881 for the correct port.

And with MP forwarder you could consider connecting to both V2 and V3 by adding entries for both.

1 Like

Thanks @kersing I will give that a try.

Update:
Fantastic - that worked!

13:03:16 INFO: [Transports] Initializing protocol for 2 servers
13:03:16 INFO: [TTN] server “bridge.eu.thethings.network” connected
13:03:16 INFO: [TTN] server “eu1.cloud.thethings.network” connected
13:03:16 INFO: [main] Starting the concentrator
13:03:19 INFO: [main] concentrator started, radio packets can now be received.
13:03:19 INFO: [up] Thread activated for all servers.

The subtle bit I was missing was the port 1881
Thank you so much :smiley:

1 Like