Laird: Sentrius RG1XX

[cjg]

Guys thanks for the replies, I was able to connected it! So it is showing online now! I just need it to replace the preset server with the current one! That did the trick!

[benoki]

Hi All,

I’ve run out of ideas on this one after RTFM’ing my little heart out and following all of the guides. I’m failing to connect to TTN due to a certificate validity error (see below). I’ve logged a ticket with Sentrius as well, just thought I would ask here incase anyone knows a fix… firmware version gatwick-laird-93.9.6.44

RG1xx29DDFF	lora	user.notice	Mar 9 23:18:57	2023-03-09 23:18:57.633 [TCE:INFO] INFOS reconnect backoff 80s (retry 1)
RG1xx29DDFF	lora	user.notice	Mar 9 23:18:57	2023-03-09 23:18:57.627 [AIO:DEBU] [6] WS connection shutdown…
RG1xx29DDFF	lora	user.notice	Mar 9 23:18:57	2023-03-09 23:18:57.627 [AIO:INFO] TLS server certificate verification failed: The certificate validity starts in the future
RG1xx29DDFF	lora	user.notice	Mar 9 23:18:57	2023-03-09 23:18:57.507 [AIO:XDEB] [6] ws_connecting state=1
RG1xx29DDFF	lora	user.notice	Mar 9 23:18:57	2023-03-09 23:18:57.506 [AIO:XDEB] [6] ws_connecting state=1
RG1xx29DDFF	lora	user.notice	Mar 9 23:18:57	2023-03-09 23:18:57.472 [AIO:XDEB] [6] ws_connecting state=1
RG1xx29DDFF	lora	user.notice	Mar 9 23:18:57	key usage : K
RG1xx29DDFF	lora	user.notice	Mar 9 23:18:57	basic constraints : CA=true
RG1xx29DDFF	lora	user.notice	Mar 9 23:18:57	RSA key size : 4096 bits
RG1xx29DDFF	lora	user.notice	Mar 9 23:18:57	signed using : RSA with SHA-256
RG1xx29DDFF	lora	user.notice	Mar 9 23:18:57	expires on : 2035-06-04 11:04:38
RG1xx29DDFF	lora	user.notice	Mar 9 23:18:57	issued on : 2015-06-04 11:04:38
RG1xx29DDFF	lora	user.notice	Mar 9 23:18:57	subject name : C=US, O=Internet Security Research Group, CN=ISRG Root X1
RG1xx29DDFF	lora	user.notice	Mar 9 23:18:57	issuer name : C=US, O=Internet Security Research Group, CN=ISRG Root X1
RG1xx29DDFF	lora	user.notice	Mar 9 23:18:57	serial number : xxx
RG1xx29DDFF	lora	user.notice	Mar 9 23:18:57	cert. version : 3
RG1xx29DDFF	lora	user.notice	Mar 9 23:18:57	2023-03-09 23:18:57.433 [AIO:INFO] /opt/lora/basicstation/tc.trust:

Thanks…

[benoki]

Solved it. For anyone who gets stuck with the same, I updated the firmware out of the box using this link -
https://connectivity-firmware.s3.amazonaws.com/rg1xx-lora-gateway/firmware/newest/fw.txt
Laird Linux gatwick-laird-93.9.6.44

to try and solve the problem I found a link to an old firmware -
https://connectivity-firmware.s3.amazonaws.com/rg1xx-lora-gateway/firmware/latest/fw.txt
Laird Linux gatwick-laird-93.7.2.10 (March 2018)

…that didn’t work, but then I rolled forward again to the latest and the error went away.

Cheers

[rcespinosa]

I’d like to ask I got my Gateway and i’m having problems connecting to the web interface via ethernet. Connecting through the wifi is working, however I cannot get the Gateway to connect to The Things Stack even though I’m following the steps given in their guide. I’ve tried updating the firmware, but that failed too.

I’ve tried connecting both my PC and Gateway to the router to try and access the interface through https://rg1xxMACID.local (where MACID is the last 6 characters of the gateway’s macid) but it won’t work no matter what I did.

[Jeff-UK]

If on same router just go direct to the GW’s IP address in your browser - I find that reliable.

[Jeff-UK]

@rcespinosa

access the interface through https://rg1xxMACID.local (where

Also I need to check but may be http vs https - long time since I tried that!

[descartes (Nick McCloud)]

A .local address is reliant on random versions of mDNS / Bonjour - if you can tell us what OS & browser you are using on the PC I can comment appropriately.

If you don’t, I’ll comment in-appropriately.

[rcespinosa]

@descartes

.local address is reliant on random versions of mDNS

PC is running on Windows 10 and the browser i’m using is Chrome

[rcespinosa]

i’ve tried using the IP Address listed in the DHCP didn’t work either. When I ping it it says host is unreachable.

[rcespinosa]

@Jeff-UK

Also I need to check but may be http vs https - long time since I tried that!

but i might try this tomorrow

[Jeff-UK]

Both wireline (recommended until you are fully up and running) or are you on wifi to/via router>

[descartes (Nick McCloud)]

That should work, but it’s dependent on how often the device broadcasts mDNS packets so it can take a few attempts for the dots to be joined up. But at the end of the day the IP address is, if configured correctly, a dead cert.

[rcespinosa]

@Jeff-UK

Both wireline (recommended until you are fully up and running) or are you on wifi to/via router>

When accessing the web interface, I have to use the AP Config Mode of the router to change some settings.

[rcespinosa]

@Jeff-UK

Also I need to check but may be http vs https - long time since I tried that!

didn’t work for me either sadly…

tried it while connecting both GW and PC to the router via ethernet

[rcespinosa]

@Jeff-UK

If trying MAC be sure to use Enet vs WiFi MAC and only last 3 Byte Pairs (Last 6 digits), also try to log onto its DHCP aquired IP address directly if it has taken one from the local network? If Reset then perhaps log on using WiFi quick config mode to default WiFi AP of 192.168.1.1? (I often just access using Phone or iPad this way).

Question here…

what is the difference between accessing the web interface using ethernet(https://rg1xxmacis.local) and wifi(192.168.1.1)?

[thulsadoom]

@rcespinosa

Question here…

what is the difference between accessing the web interface using ethernet(https://rg1xxmacis.local) and wifi(192.168.1.1)?

https://rg1xxmacis.local SHOULD be the IP address assigned to the ethernet interface of the gateway from your local networks DHCP server - assuming you have not configured it for a Static IP Address

When connecting to wifi 192.168.1.1 (RG1xx is in WiFi Quick Config Mode) - the RG1xx configures its radio module into Host AP mode - and your wireless device (phone, laptop, etc) joins the private WLAN created by the RG1xx.

Even if your normal network uses 192.168.1.0 addresses - the 192.168.1.1 you are connecting to in this case is completely isolated.

You can always connect to the RG1xx via WiFi Quick Config mode to determine what IP address is assigned to the gateways ethernet interface - if any, and then connect to THAT IP instead.

[rcespinosa]

@thulsadoom

You can always connect to the RG1xx via WiFi Quick Config mode to determine what IP address is assigned to the gateways ethernet interface - if any, and then connect to THAT IP instead.

Did this and found out that the IP Address given to the gateway was 192.168.1.17, used that to access the ethernet interface and still no luck.

[Jeff-UK]

…and you did that with your PC on wireline on the same router as gave the Laird the 192.168.1.17 address? What is your PC assigned IP address?..

…is the Laird new or had it been used before?

[rcespinosa]

yes, it’s also connected to the same router via an ethernet cable. The IP Address of the PC is 192.168.1.23.

@Jeff-UK

…is the Laird new or had it been used before?

It has been used before, but I did factory reset it while trying to get it to work.

[kersing (Jac Kersing)]

What is address does the gateway assign to your PC when using AP mode? If that is 192,168.1.x there might be an issue if your LAN uses the same IP range.
Using the AP connection you could try to set the IP range used to something else (probably in the advanced WLAN settings)