Does anybody know that ttn LNS support China region? is there a LNS wss://lns.cn.thethings.network:443? Is it possible that i use basic station and ttn in China？
Unfortunately not, we don’t support that at the moment.
feel free to try the balena based TTN Basics Station gateway following these instructions https://www.balena.io/blog/deploy-a-basics-station-lora-gateway-with-ttn-and-balena/
hope this can simplify installation of the newest gateways.
After TTC presentation of @jmarcelino I got inspired and setup basics station with Balena on my RAK 831 gateway. Connection to V2 went flawless and the gateway runs fine. However, it fails to connect to V3.
I am informed that:
2021-01-26 20:24:13.108 [TCE:INFO] Connecting to INFOS: wss://eu1.cloud.thethings.network:8887
2021-01-26 20:24:13.152 [AIO:INFO] TLS server certificate verification failed: The certificate is not correctly signed by the trusted CA
At Deploy a Basics Station The Things Network LoRa gateway with balena I find: In some cases the certificate may change from the one used at the TTN gateway. In that case, set up the variable TC_CERT with the certificate.
Unsure where to get the certificate I cannot make it work with V3.
Can anyone help me out? Thanks in advance.
1 Like
These instructions should be similar enough.
http://www.multitech.net/developer/software/lora/running-basic-station-on-conduit/
Hi!
I’m using the X3 certificate (which is the default if you supply none) successfully with TTC Things Stack
I’m using this one https://letsencrypt.org/certs/trustid-x3-root.pem.txt
26.01.21 22:28:00 (+0000) basicstation 2021-01-26 22:28:00.692 [TCE:INFO] Connecting to INFOS: wss://ttc.eu1.cloud.thethings.industries:8887
26.01.21 22:28:01 (+0000) basicstation 2021-01-26 22:28:01.042 [any:INFO] ./tc.trust:
26.01.21 22:28:01 (+0000) basicstation cert. version : 3
26.01.21 22:28:01 (+0000) basicstation serial number : 44:AF:B0:80:D6:A3:27:BA:89:30:39:86:2E:F8:40:6B
26.01.21 22:28:01 (+0000) basicstation issuer name : O=Digital Signature Trust Co., CN=DST Root CA X3
26.01.21 22:28:01 (+0000) basicstation subject name : O=Digital Signature Trust Co., CN=DST Root CA X3
26.01.21 22:28:01 (+0000) basicstation issued on : 2000-09-30 21:12:19
26.01.21 22:28:01 (+0000) basicstation expires on : 2021-09-30 14:01:15
26.01.21 22:28:01 (+0000) basicstation signed using : RSA with SHA1
26.01.21 22:28:01 (+0000) basicstation RSA key size : 2048 bits
26.01.21 22:28:01 (+0000) basicstation basic constraints : CA=true
26.01.21 22:28:01 (+0000) basicstation key usage : Key Cert Sign, CRL Sign
26.01.21 22:28:01 (+0000) basicstation 2021-01-26 22:28:01.043 [AIO:INFO] tc has no cert configured - running server auth and client auth with token
26.01.21 22:28:01 (+0000) basicstation 2021-01-26 22:28:01.091 [TCE:VERB] Connecting to MUXS...
26.01.21 22:28:01 (+0000) basicstation 2021-01-26 22:28:01.467 [TCE:VERB] Connected to MUXS.
26.01.21 22:28:01 (+0000) basicstation 2021-01-26 22:28:01.516 [RAL:WARN] Ignoring unsupported/unknown field: antenna_gain
26.01.21 22:28:01 (+0000) basicstation 2021-01-26 22:28:01.516 [RAL:INFO] Lora gateway library version: Version: 5.0.1;
Did you change the TC_TRUST in some way?
For eu1.cloud.thethings.network, we use the Let’s Encrypt ISRG X1 as the LNS certificate. Root Certificates | The Things Stack for LoRaWAN
The reason why we don’t want to make these cert chains official is that TTI CUPS (which will be available soon after the conference) will solve the cert management problems for you.
When in doubt, you can cross check the chain used by the server
$ HOST="eu1.cloud.thethings.network"
$ PORT="8887"
$ openssl s_client -host $HOST -port $PORT -prexit -showcerts
Hi @jmarcelino I followed exactly the instructions from yesterday at TTC and installed also the wifi container. I did not change the pull from git.
This is the complete log:
26.01.21 21:32:37 (+0100) 2021-01-26 20:32:37.791 [any:INFO] ./tc.trust:
26.01.21 21:32:37 (+0100) cert. version : 3
26.01.21 21:32:37 (+0100) serial number : 44:AF:B0:80:D6:A3:27:BA:89:30:39:86:2E:F8:40:6B
26.01.21 21:32:37 (+0100) issuer name : O=Digital Signature Trust Co., CN=DST Root CA X3
26.01.21 21:32:37 (+0100) subject name : O=Digital Signature Trust Co., CN=DST Root CA X3
26.01.21 21:32:37 (+0100) issued on : 2000-09-30 21:12:19
26.01.21 21:32:37 (+0100) expires on : 2021-09-30 14:01:15
26.01.21 21:32:37 (+0100) signed using : RSA with SHA1
26.01.21 21:32:37 (+0100) RSA key size : 2048 bits
26.01.21 21:32:37 (+0100) basic constraints : CA=true
26.01.21 21:32:37 (+0100) key usage : Key Cert Sign, CRL Sign
26.01.21 21:32:37 (+0100) 2021-01-26 20:32:37.791 [AIO:INFO] tc has no cert configured - running server auth and client auth with token
26.01.21 21:32:37 (+0100) 2021-01-26 20:32:37.829 [TCE:INFO] Connecting to INFOS: wss://eu1.cloud.thethings.network:8887
26.01.21 21:32:37 (+0100) 2021-01-26 20:32:37.871 [AIO:INFO] TLS server certificate verification failed: The certificate is not correctly signed by the trusted CA
26.01.21 21:32:37 (+0100) 2021-01-26 20:32:37.871 [AIO:DEBU] [3] WS connection shutdown...
26.01.21 21:32:37 (+0100) 2021-01-26 20:32:37.871 [TCE:INFO] INFOS reconnect backoff 60s (retry 6)
Any reason what could make the difference?
Did you succeed? I get out one of my custom GW, spend a couple of hours trying and got same result as your. I followed this video but it’s for TTN V2/Basic Station
No success. I got the same error than you.
If someone with working configuration could post exact values to put in balena.io in env fields TC_CERT and TC_URI it would really help to debug 
Anyway, sometime keeping things easy, I put back my old SD card, deleted GW on V2, created gateway on V3 with same EUI, changed server_address in local_conf.json as follow
"server_address": "eu1.cloud.thethings.network"
and voila, GW up and running on V3 in old school mode
root@loragw-61a4:/opt/loragw # systemctl stop loragw
root@loragw-61a4:/opt/loragw # systemctl start loragw
root@loragw-61a4:/opt/loragw # journalctl -f -u loragw
-- Logs begin at Fri 2020-11-06 15:33:48 CET. --
Feb 04 19:13:09 loragw-61a4 loragw[954]: INFO: Description configured to "ch2i-gw03-iC880a"
Feb 04 19:13:14 loragw-61a4 loragw[954]: INFO: Successfully contacted server eu1.cloud.thethings.network
Feb 04 19:13:14 loragw-61a4 loragw[954]: INFO: [main] Starting the concentrator
Feb 04 19:13:17 loragw-61a4 loragw[954]: INFO: [main] concentrator started, radio packets can now be received.
Feb 04 19:13:17 loragw-61a4 loragw[954]: INFO: [up] Thread activated for all servers.
Feb 04 19:13:17 loragw-61a4 loragw[954]: INFO: [down] Thread activated for all server eu1.cloud.thethings.network
Feb 04 19:13:17 loragw-61a4 loragw[954]: INFO: [down] for server eu1.cloud.thethings.network PULL_ACK received in 26 ms
Feb 04 19:13:24 loragw-61a4 loragw[954]: INFO: [#2601239B] uUP CRC:Bad Freq:867.50MHz ch:5 RFch:0 LORA[SF7 125Khz 4/5] RSSI:-87dB SNR:-4.0dB Size:21b
Feb 04 19:13:24 loragw-61a4 loragw[954]: INFO: [#2601279B] uUP CRC:OK Freq:867.30MHz ch:4 RFch:0 LORA[SF7 125Khz 4/5] RSSI:-36dB SNR:+9.0dB Size:21b Data:'QJsnASYA3rcBkckfCBYXXxueWW86'
Feb 04 19:13:24 loragw-61a4 loragw[954]: INFO: [#2515279D] RFU CRC:Bad Freq:868.30MHz ch:1 RFch:1 LORA[SF7 125Khz 4/5] RSSI:-99dB SNR:-6.8dB Size:21b
Feb 04 19:13:24 loragw-61a4 loragw[954]: INFO: [up] PUSH_ACK for server eu1.cloud.thethings.network received in 97 ms
Feb 04 19:13:27 loragw-61a4 loragw[954]: INFO: [down] for server eu1.cloud.thethings.network PULL_ACK received in 25 ms
Feb 04 19:13:37 loragw-61a4 loragw[954]: INFO: [down] for server eu1.cloud.thethings.network PULL_ACK received in 25 ms
Feb 04 19:13:47 loragw-61a4 loragw[954]: INFO: [#1A8D5DFD] uDN CRC:Bad Freq:868.30MHz ch:8 RFch:1 LORA[SF7 250Khz 2/3] RSSI:-100dB SNR:-11.2dB Size:225b
Feb 04 19:13:47 loragw-61a4 loragw[954]: INFO: [#30401B35] Prp CRC:Bad Freq:867.90MHz ch:7 RFch:0 LORA[SF7 125Khz 4/5] RSSI:-107dB SNR:-11.5dB Size:101b
Feb 04 19:13:47 loragw-61a4 loragw[954]: INFO: [#2AFF6E50] jAC CRC:Bad Freq:868.50MHz ch:2 RFch:1 LORA[SF7 125Khz 4/7] RSSI:-107dB SNR:-11.5dB Size:140b
Feb 04 19:13:47 loragw-61a4 loragw[954]: ##### 2021-02-04 18:13:47 GMT #####
Hi Charles, not sure what your conclusion is here.
My story is that I try to setup basics station with the Balena specific deployment om my gateway.
When I follow your video I link it to V2 which perfectly works fine without modification
However, when I follow instructions from TTC (https://youtu.be/e3HO3Q0qYqM) to connect basics station to V3 it fails. I get this message:
main 2021-02-05 07:17:30.253 [any:INFO] ./tc.trust:
main cert. version : 3
main serial number : 44:AF:B0:80:D6:A3:27:BA:89:30:39:86:2E:F8:40:6B
main issuer name : O=Digital Signature Trust Co., CN=DST Root CA X3
main subject name : O=Digital Signature Trust Co., CN=DST Root CA X3
main issued on : 2000-09-30 21:12:19
main expires on : 2021-09-30 14:01:15
main signed using : RSA with SHA1
main RSA key size : 2048 bits
main basic constraints : CA=true
main key usage : Key Cert Sign, CRL Sign
main 2021-02-05 07:17:30.253 [AIO:INFO] tc has no cert configured - running server auth and client auth with token
main 2021-02-05 07:17:30.288 [TCE:INFO] Connecting to INFOS: wss://eu1.cloud.thethings.network:8887
main 2021-02-05 07:17:30.329 [AIO:INFO] TLS server certificate verification failed: The certificate is not correctly signed by the trusted CA
main 2021-02-05 07:17:30.329 [AIO:DEBU] [3] WS connection shutdown...
main 2021-02-05 07:17:30.330 [TCE:INFO] INFOS reconnect backoff 20s (retry 2)
I have successfully connected gateways using UDP and protobuf with V3 but basics station keeps failing on certificates.
Not sure to have a conclusion, but butter explanations with your video link shame on me didn’t aware of.
I’ll try again testing with parameters of the video and post results here.
Thanks
1 Like
[SOLVED]
I just got info from twitter that the repository was updated with the right certificate. It works now for me.
1 Like
Awesome, does this means device will self update or do we need to build new image and flash back SD card?
From this site (Deploy a LoRa Basics™ Station gateway with TTN and balena - balena Blog) I followed the link to deploy basics station using their template: balena dashboard
There I “deployed to existing application” where I chose my previous created application:
Now the existing Balena deployments are being updated with the new repository.
In my case, all existing settings were kept and the docker containers was updated.
1 Like
Oh yes thanks, to the trick : deploy to existing application. That did the job 
I got another issue not related to TTN, just giving a try here, balenaOS does not detect the WiFi interface on RPI 3B (not B+) V1.2, even if I plug a USB WiFi dongle, anyone has experienced this issue?
Is there any documentation on configuring Raspberry Pi running basicstation with a RAK2287 pi hat?
I set up gateway with appropriate API for LNS and CUPS. Most of the docs I’ve found leave a lot to guess work ie what directory for CUPS_KEY? Using example corecell it gives error TLS server certificate verification failed… Tried updating raspberry pi certificates with no change in symptom. Most examples and post refer to 1301 products, or enabling port forwarding on gateway configuration - it’s gone! Any direction of where to look next would help.
The basics are the same for all raspberry pi based gateways so you should be able to use the instructions with just minor changes (mostly change the reset pin to match you hardware and make sure the chipset configuration (sx1301 vs sx1302) is correct.)
I’m not using BasicStation on any of my gateways so I don’t have instructions I can point to without googling and I trust you’re able to search the web yourself.
Here you can find a tutorial for a RasperryPI + IC880A-SPI gateway setup.
I think colul help with your setup.