Trying to move my Kona Micro Lite gateway from TTN v2 to v3. I’ve followed their guides exactly but have had zero luck getting it attached.
Anyone have any experience with the Kona Micro Lite on TTN v3?
as for steps…
Customer.json:
{"private_key_password":"","network":"bstn","bstn":{"cups_uri":"https://nam1.cloud.thethings.network:443","cups_use_token":true,"lns_uri":"","lns_use_token":false}}
cups.key:
Authorization: Bearer NNSXS. ...... omitted
isrgrootx1.pem
(ca certificate for https://nam1.cloud.thethings.network:443. confirmed correct CA per openssl cmd
tftp> bin
tftp> put ./bstn_4baeec1_release_.bin Gateway.bin
(Unit reboots, no issues)
tftp> put isrgrootx1.pem CaRootCertificate.pem
tftp> put cups.key PrivateKey.pem
tftp> put Customer.json Customer.json
Tried with / without bin. bin required for the firmware upgrade to happen. with / without bin for the config files makes no difference.
I can get the pushed files and confirm the gotten configs match what I have on disk.
Per the guide, my " Lora Basics Station LNS Authentication key" in the TNN gui matches my LNS api key. (NNSXS…etc)
Ran a tcpdump, I can definitely see the gateway talking to TTN… but it looks like something goes wrong.
root@ubnt:~# tcpdump -i eth1 host 192.168.1.108
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on eth1, link-type EN10MB (Ethernet), capture size 262144 bytes
22:41:38.725675 IP 192.168.1.1.bootps > 192.168.1.108.bootpc: BOOTP/DHCP, Reply, length 300
22:41:38.737264 IP 192.168.1.1.bootps > 192.168.1.108.bootpc: BOOTP/DHCP, Reply, length 300
22:41:38.737574 ARP, Request who-has 192.168.1.108 tell 0.0.0.0, length 46
22:41:39.222519 ARP, Request who-has 192.168.1.108 tell 0.0.0.0, length 46
22:41:39.722496 ARP, Request who-has 192.168.1.108 tell 192.168.1.108, length 46
22:41:40.035206 ARP, Request who-has 192.168.1.1 tell 192.168.1.108, length 46
22:41:40.035309 ARP, Reply 192.168.1.1 is-at XXX (oui Unknown), length 28
22:41:40.035476 IP 192.168.1.108.49153 > 192.168.1.1.domain: 0+ A? pool.ntp.org. (30)
22:41:40.038018 IP 192.168.1.108.49154 > time.cloudflare.com.ntp: NTPv4, Client, length 48
22:41:40.060052 IP time.cloudflare.com.ntp > 192.168.1.108.49154: NTPv4, Server, length 48
22:41:42.799703 IP 192.168.1.108.49153 > 192.168.1.1.domain: 1+ A? nam1.cloud.thethings.network. (46)
22:41:42.819168 IP 192.168.1.1.domain > 192.168.1.108.49153: 1 2/0/0 A 54.219.100.33, A 13.56.119.10 (78)
22:41:42.819541 IP 192.168.1.108.49153 > ec2-54-219-100-33.us-west-1.compute.amazonaws.com.https: Flags [S], seq 6511, win 2920, options [mss 1460], length 0
22:41:42.886396 IP ec2-54-219-100-33.us-west-1.compute.amazonaws.com.https > 192.168.1.108.49153: Flags [S.], seq 2976915342, ack 6512, win 26883, options [mss 1460], length 0
22:41:42.886645 IP 192.168.1.108.49153 > ec2-54-219-100-33.us-west-1.compute.amazonaws.com.https: Flags [.], ack 1, win 2920, length 0
22:41:43.055238 IP ec2-54-219-100-33.us-west-1.compute.amazonaws.com.https > 192.168.1.108.49153: Flags [.], ack 430, win 27872, length 0
22:41:44.280173 IP 192.168.1.108.49153 > ec2-54-219-100-33.us-west-1.compute.amazonaws.com.https: Flags [F.], seq 924, ack 4367, win 2920, length 0
22:41:44.341436 IP ec2-54-219-100-33.us-west-1.compute.amazonaws.com.https > 192.168.1.108.49153: Flags [F.], seq 4398, ack 925, win 28944, length 0
22:41:44.341505 IP 192.168.1.108.49153 > ec2-54-219-100-33.us-west-1.compute.amazonaws.com.https: Flags [R.], seq 925, ack 4398, win 2920, length 0
22:41:44.341627 IP 192.168.1.108.49153 > ec2-54-219-100-33.us-west-1.compute.amazonaws.com.https: Flags [R.], seq 925, ack 4399, win 2920, length 0
Ugh. Figured it out. The gateway EUI in TNN was one hex digit off. Pretty sure the first time I created it I left the EUI blank as well.
Recreated the gateway, retyped the EUI, new keys. Working now
rying to move my Kona Micro Lite gateway from TTN v2 to v3 . I’ve followed their guides exactly but have had zero luck 192.168.l.254 getting it attached. Kona Micro FAQ. On this page. #1 Accessing the battery and SIM slot; #2 SIM installed but not detected; #3 SSH Client no longer connects after gateway …