Connection to v3 of The Things Network

I have a RAK7249 r209. It worked perfectly on v2 of The Things Network. I deleted it and re-added it to v3 of TTS. It will no longer connect in basic station mode. ( nam1.cloud.thethings.network). It only connects as a packet forwarder.

Does anyone have any advice?

Hei @TimothyLa ,

Can you walk us through the steps you took to onboard it via Basics Station?
For example what Authentication method are you using? Certificates. etc?

Regards
Vladislav

Steps taken:
It was working as packet forwarder…
I switched to basic station , LNS Server
URI wss://nam1.cloud.thethings.network
Port 8887
Authentication Mode TLS Server Auth
Certificate is the one suggested by TTS - ISRG Root X1

Log shows this-

basic constraints : CA=tFri Apr 9 07:57:42 2021 user.info basicstation[6830]: [AIO:INFO] tc has no key+cert configured - running server auth only
Fri Apr 9 07:57:42 2021 user.info basicstation[6830]: [TCE:INFO] Connecting to INFOS: wss://nam1.cloud.thethings.network:8887
Fri Apr 9 07:57:42 2021 user.err basicstation[6830]: [S2E:ERRO] Failed to send gps event, no buffer space
Fri Apr 9 07:57:42 2021 user.info basicstation[6830]: [TCE:INFO] Infos: acxxxxx muxs-::0 wss://nam1.cloud.thethings.network:8887/traffic/eui-ACxxxxxxxxx
Fri Apr 9 07:57:42 2021 user.info basicstation[6830]: [any:INFO] /var/etc/station/tc.trust:
cert. version : 3
serial number : 82:10:CF:B0:D2:40:E3:59:44:63:E0:BB:63:82:8B:00
issuer name : C=US, O=Internet Security Research Group, CN=ISRG Root X1
subject name : C=US, O=Internet Security Research Group, CN=ISRG Root X1
issued on : 2015-06-04 11:04:38
expires on : 2035-06-04 11:04:38
signed using : RSA with SHA-256
RSA key size : 4096 bits
basic constraints : CA=tFri Apr 9 07:57:42 2021 user.info basicstation[6830]: [AIO:INFO] tc has no key+cert configured - running server auth only
Fri Apr 9 07:57:43 2021 user.err basicstation[6830]: [S2E:ERRO] Failed to send gps event, no buffer space
Fri Apr 9 07:57:43 2021 user.err basicstation[6830]: [AIO:ERRO] [5] WS upgrade failed with HTTP status code: 401
Fri Apr 9 07:57:43 2021 user.info basicstation[6830]: [TCE:INFO] INFOS reconnect backoff 10s (retry 1)
Fri Apr 9 07:57:44 2021 user.err basicstation[6830]: [S2E:ERRO] Failed to send gps event, no buffer space
Fri Apr 9 07:57:45 2021 user.err basicstation[6830]: [S2E:ERRO] Failed to send gps event, no buffer space
Fri Apr 9 07:57:46 2021 user.err basicstation[6830]: [S2E:ERRO] Failed to send gps event, no buffer space
Fri Apr 9 07:57:47 2021 user.err basicstation[6830]: [S2E:ERRO] Failed to send gps event, no buffer space
Fri Apr 9 07:57:48 2021 user.err basicstation[6830]: [S2E:ERRO] Failed to send gps event, no buffer space
Fri Apr 9 07:57:49 2021 user.err basicstation[6830]: [S2E:ERRO] Failed to send g

Hei @TimothyLa ,

This is indeed weird. I will have to dig into this a bit more. I am facing the same issues with a couple of gateways that I have been running on the V3 stack for week. Now I get the same error you do. I am hoping it is something on TTNs end as I see no reason for this seeing as RAK did not change a thing.
Could it be they changed their certificate policy or something?

Regards
Vladislav

At present anything could be going on with BasicStation as one of the road blocks to transitioning from v2 is that the TTIG can’t be used on v3 yet. So they may well be hacking on it.

The solution seems to be to change the Authentication mode. Guidelines referencing connecting the RAK7249 to v2 TTN advise using Server Authentication. For v3TTS it appears you must use Server and Client Token Authentication. You create the API token in the v3 console and copy it into the gateway console into the token field. It appears you must preface the your API key like this “Authorization: Bearer NNxxxxxxxx” .

Saw that already, does not seem to work on my end. Will poke the bear some more :slight_smile:

I see data in v3 with this new configuration. However the system log of the RAK7249 continues to show many odd errors which may be related. Like this

Mon Apr 12 13:48:34 2021 user.err basicstation[1538]: [LOG:ERRO] Lora mode error, mode value: 0
Mon Apr 12 13:48:34 2021 user.err basicstation[1538]: [LOG:ERRO] Lora mode error, mode value: 0
Mon Apr 12 13:48:34 2021 user.err basicstation[1538]: [LOG:ERRO] Lora mode error, mode value: 0
Mon Apr 12 13:48:34 2021 user.err basicstation[1538]: [LOG:ERRO] Lora mode error, mode value: 0
Mon Apr 12 13:48:34 2021 user.err basicstation[1538]: [LOG:ERRO] Lora mode error, mode value: 0
Mon Apr 12 13:48:34 2021 daemon.err uhttpd[1485]: connect ERROR: Connection refused

We are looking into it will keep you posted.

Are these posts of any use?

and

I saw them already, I hope it is just me, but the method doesn’t work on my side. I would say they are useful though.