TTN GATEWAY central 3

[LoRaTracker]

Of interest to me would be to know if there is any kind of benchmark that can be used.
TTN’s objective as an organisation is (among others) to encourage individuals and companies to deploy gateways in as many optimum locations and configurations as possible. To that end, such individuals would benefit from being able to verify that they have deployed more than a parrot perch!

I mentioned that earlier;

> The only practical method I can think of to benchmark a gateways RF performance is to measure it under open field line of sight conditions, i.e. take it away from an urban environment.

Whilst that sort of testing is actually quite easy and some of the techniques I use are discussed here;

https://github.com/LoRaTracker/AntennaTesting

Its way to much work for a lot of people.

Similar comparisions in ‘urban’ areas are quite difficult. The diference in reception distance between true line of sight conditions and what you get in ‘urban’ areas can be vast, 1200:1 or ever more. The implication is that variations between one urban area and another can be significant.

The only alterantive I can think of is if people would first post data and pictures of their gateway locations and setups. Then post pictures from locations looking towards the gateways together with the reception results from the nodes. At least then you have a photo guide to typical scenarios.

[TonySmith]

I then fitted an outdoor antenna high on the roof - a Delock Lora 868 omnidirectional antenna fed via about 10 metres of 50 ohm coax.

You can see it perched on the left of the TV aerial.

I would suggest the TTN antenna’s location relative to the TV antenna is going have a huge influence on its performance. It looks like the active part of the antenna is about the same height as the TV antenna and as a result the radiation pattern of the TTN antenna will no longer be uniform in all directions but distorted and directional. In comparison, the antenna to the right of the TV antenna would work correctly as it’s above the TV antenna.

To explain: if you look closely at the TV antenna you will see the cable is connected to 2 or 3 of the metal elements on the TV antenna (driven elements), the rest of the metal elements are passive. However they have the correct length and location to interact with driven elements to achieve a highly directional pattern to improve the performance of the television.

Now back to the TTN antenna: The TV antenna is going to act as Passive Elements to the TTN antenna and influence its radiation pattern. I realise the distance between the two is quite a few wavelengths and at that distance a single upright pole (like the pole that supports the TV antenna) has very little effect, however the TV antenna is large and will influence the performance of the TTN antenna.

When you conduct your “line of sight tests”, see if you can repeat this in a number of directions and see if you observe the gain is different for each direction.

[BoRRoZ]

I finally got around to booting it up and it connected to Ethernet and showed up on my console immediately! Woohoo!

Whooho

Is there a Wiki someplace where I can find

not that I know

I did find this: https://www.thethingsnetwork.org/docs/gateways/gateway/programhexfile.html

Is this what I have to do to get it updated?

select “Automatically update gateway” in TTN Console

BTW … how do I get invited to the Slack channel?

you’d need to request an automatic invite on https://account.thethingsnetwork.org

[kersing (Jac Kersing)]

I see people talking about firmware updates - and obviously mine needs an update - but I’m not seeing a Wiki page or specific instructions on how to force the OTA update they claim exists. Or is my firmware too old to support the OTA? And if I have to use the SD card, where is the Wiki page that explains the process?

Did you check the documentation and github site for this device? There you’ll find information on SD card updates.

[Humancell]

Did you check the documentation and github site for this device? There you’ll find information on SD card updates.

Hello! Thank you for the reply!

Yes … I read everything on the “documentation” link that you provided, and it only shows someone programming the gateway using a hardware programmer. Yet when I read elsewhere, it says that the gateways are automatically updated via OTA. Mine, after numerous reboots, and days of operation has not been updated. How is the OTA triggered?

I also looked on Github, and read there the README in the firmware directory where, again, it states: “Installing the firmware is usually done using over-the-air updates from our official releases. Here are the steps to install custom firmware:”

So … is there somewhere explaining that I need to do the SD Card update and that OTA is not working?

Thank you for the response!

[kersing (Jac Kersing)]

My gateway recently updated automatically so OTA is certainly working. However there has been an updated firmware with an update for certificates some time ago that might (I didn’t look into it to check) have some impact on the ability to update over the air.

I would suggest you use the SD card mechanism to update to a recent (last 2 months) firmware and see what happens when a new version is released.
Make sure you have ‘Automatically update gateway’ checked in the gateway settings.

[Humancell]

I would suggest you use the SD card mechanism to update to a recent (last 2 months) firmware and see what happens when a new version is released.
Make sure you have ‘Automatically update gateway’ checked in the gateway settings.

Ok … that seemed to work and get me closer! I’m now at v1.06?

Version Info	
Hardware:  v1
Bootloader:  r1-7167873a (2017-06-02T13:48:18Z)
Firmware:  v1.0.6-d8cb4c30 (2019-05-17T07:19:39Z)

Are most people running the “Beta” version to get to v1.0.7?

Also … as a side note …

When booting WITHOUT the SD Card in place, my gateway seems to sit FOREVER and doesn’t appear to want to connect to the Ethernet. (No lights on my hub)

When booting WITH the SD Card in place, my gateway boots immediately, and connects the Ethernet and is off and running.

Ideas on why?

[ScottM]

Does The Things Gateway implement the full US sub-band 2? (channels 8-15 + 65?)

I am trying to figure out why my gateway only appears to receive even frame upload packets from a OneThinx module and OneThinx thought the gateway might not implement channel 65. (I looked at the source from the last time I built the gateway firmware (1.0.5) and it looks like it implements 8+1 channels (8-15 & 65):

       SYS_DEBUG(SYS_ERROR_WARNING, "LORA: use default US config\r\n");
        status = status && configureRXChain(0, 1, 904200000);
        status = status && configureRXChain(1, 1, 905000000);
        status = status && configureIFChainX(0, 1, 0, -300000);
        status = status && configureIFChainX(1, 1, 0, -100000);
        status = status && configureIFChainX(2, 1, 0, 100000);
        status = status && configureIFChainX(3, 1, 0, 300000);
        status = status && configureIFChainX(4, 1, 1, -300000);
        status = status && configureIFChainX(5, 1, 1, -100000);
        status = status && configureIFChainX(6, 1, 1, 100000);
        status = status && configureIFChainX(7, 1, 1, 300000);
        status = status && configureIFChain8(1, 0, 400000, 500000, 8);
        status = status && configureIFChain9(0, 0, 0, 0, 0);

(Hoping someone can save me from having to go through the pain of building a debug image of the 1.0.7 firmware so I can poke around. )

Thanks, Scott.

[ankush_kapile]

I also got the 915 The Things Network Gateway and was looking for any work around to get that Gateway working with US ranges (but in India) just for the test purpose.
Please note: I do not want to connect any India specific LoRa devices to this Gateway. I already have 1 US based LoRa device which I can connect to this Gateway for my test.

By looking at other posts related to the Gateway setup and the India specific bands. I don’t think whatever I am trying is possible but still I am looking for some workaround to get 915 TTN activated and solve my test purpose.

Thanks in advance.

[BoRRoZ]

you probably need a hardware modification … if you really need to test another frequency band, best to import a gateway for that specific band imho.

[danmaneu]

Is there someone still experiencing reconnect issues? I want my gateway connected via WiFi and I was able to make some improvements in the firmware so I went from this:

to this:

Here is my current branch:

danielkucera/gateway

I can also provide firmware images if someone is interrested.
There are still some minor issues but it is at least acceptable now.

I’ve also created a esp8266 firmware which captures logs on TTNGW and sends them to my syslog so I have all logs stored on my server like this:
Sep 29 06:50:55 192.168.0.122 MON: heap usage: 280KB (284KB), free: 58KB
Sep 29 06:50:59 192.168.0.122 MQTT: Sending status packet
Sep 29 06:51:01 192.168.0.122 MQTT: Sending status failed
Sep 29 06:51:01 192.168.0.122 MAIN: MQTT error
Sep 29 06:51:01 192.168.0.122 MAIN: Leaving state 5
Sep 29 06:51:04 192.168.0.122 MAIN: Entering state 6
Sep 29 06:51:04 192.168.0.122 INET: State change to 0
Sep 29 06:51:04 192.168.0.122 INET: Gateway has WiFi
Sep 29 06:51:04 192.168.0.122 INET: State change to 2
Sep 29 06:51:04 192.168.0.122 INET: Connected to a network, waiting for DHCP lease, checking validity with ping
Sep 29 06:51:05 192.168.0.122 INET: State change to 3
Sep 29 06:51:05 192.168.0.122 INET: Ping probe
Sep 29 06:51:05 192.168.0.122 INET: Error sending probe on Eth
Sep 29 06:51:05 192.168.0.122 INET: Ping response from MRF24WN, set as default
Sep 29 06:51:05 192.168.0.122 INET: State change to 5
Sep 29 06:51:05 192.168.0.122 MAIN: Leaving state 6
Sep 29 06:51:05 192.168.0.122 MAIN: Entering state 5
Sep 29 06:51:05 192.168.0.122 MQTT: GOT IP: 52.169.76.203
Sep 29 06:51:05 192.168.0.122 MQTT: !NET_PRES_SocketIsConnected
Sep 29 06:51:05 192.168.0.122 MQTT: !NET_PRES_SocketIsConnected
Sep 29 06:51:05 192.168.0.122 MQTT: message repeated 23 times: [ !NET_PRES_SocketIsConnected]
Sep 29 06:51:05 192.168.0.122 MON: SYS Stack size: 2833
Sep 29 06:51:05 192.168.0.122 MON: TCPIP Stack size: 3581
Sep 29 06:51:05 192.168.0.122 MON: APP Stack size: 2213
Sep 29 06:51:05 192.168.0.122 MON: LoRa Stack size: 3877
Sep 29 06:51:05 192.168.0.122 MON: heap usage: 191KB (284KB), free: 148KB
Sep 29 06:51:05 192.168.0.122 MQTT: !NET_PRES_SocketIsConnected
Sep 29 06:51:05 192.168.0.122 MQTT: message repeated 7 times: [ !NET_PRES_SocketIsConnected]
Sep 29 06:51:05 192.168.0.122 MQTT: NET_PRES_SocketWasReset
Sep 29 06:51:05 192.168.0.122 MQTT: Connection Opened: Starting TLS Negotiation
Sep 29 06:51:05 192.168.0.122 MQTT: Wait for SSL Connect
Sep 29 06:51:06 192.168.0.122 MQTT: TLS ready: Connect MQTT
Sep 29 06:51:06 192.168.0.122 RQLORA: Kick LoRa module with ACK after not acked it for 60s
Sep 29 06:51:06 192.168.0.122 MQTT: Connected
Sep 29 06:51:06 192.168.0.122 *************************
Sep 29 06:51:06 192.168.0.122 MAIN: Gateway bridging
Sep 29 06:51:06 192.168.0.122 *************************
Sep 29 06:51:15 192.168.0.122 MON: SYS Stack size: 2833
Sep 29 06:51:15 192.168.0.122 MON: TCPIP Stack size: 3581
Sep 29 06:51:15 192.168.0.122 MON: APP Stack size: 2213
Sep 29 06:51:15 192.168.0.122 MON: LoRa Stack size: 3877
Sep 29 06:51:15 192.168.0.122 MON: heap usage: 280KB (284KB), free: 58KB
Sep 29 06:51:25 192.168.0.122 MON: SYS Stack size: 2833
Sep 29 06:51:25 192.168.0.122 MON: TCPIP Stack size: 3581
Sep 29 06:51:25 192.168.0.122 MON: APP Stack size: 2213
Sep 29 06:51:25 192.168.0.122 MON: LoRa Stack size: 3877
Sep 29 06:51:25 192.168.0.122 MON: heap usage: 280KB (284KB), free: 58KB
Sep 29 06:51:28 192.168.0.122 MQTT: Sending status packet
Sep 29 06:51:28 192.168.0.122 MQTT: Report config error: 0600000020
Sep 29 06:51:29 192.168.0.122 MQTT: Sending status succeeded: 1176

[pe1mew (Remko)]

Hi, Great work! It is the first serious attempt outside TTI and Tweetonig I know to improve this firmware. Thank you. As I cannot compile myself I am happy to test and share my experience.

[danmaneu]

Ok guys, here is the latest compiled version for you to try:
https://s.danman.eu/ttngw/

Upgrade the usual way: FAT formated SD card with folder “update” and these files in.

[pe1mew (Remko)]

Keep you posted about the results

[pe1mew (Remko)]

Today I found time to start the test. I have copied the new firmware to the uSD card and booted the gateway.

1. Without changing configuration (ethernet connected) the gateway came up after powering and started working with the uSD card installed.
2. Than I reset the gateway (pressing the reset button 3 seconds to erase wifi settings).
3. Disconnect ethernet and connect to WiFi accesspoint of gateway.
4. Reconfigured the gateway using the activation page to use wifi and provided the credentials for the local access point.
5. gateway restarts, connects to Wifi and works fine.

now we wait and see.

As can be seen I use V2 bootloader.

[pe1mew (Remko)]

Hi @danmaneu Here are the first results over last night. In my case it is not promising other than that it seems that connection is recovered faster with this firmware.

I have information from to types of logging:

1. Logging by mij gateway monitoring script that queries in a 10 minute interval to see if a gateways has not been responsive for a minute.
2. DHCP requests as recorded by my router. I assume that a DHCP request is the result of an newly initiated WiFi connection.

gateway logging
Where my gateway never goes doew when it is connected over ethernet, tonight is was idietified by the script multiple times:

11:10 PM Gateway "ttn_pe1mew_gateway_1" seems down! Last message was 9 minutes, 3 seconds ago.
11:20 PM Gateway "ttn_pe1mew_gateway_1" is back in operation since 22:20:00 2019-10-05.
1:50 AM Gateway "ttn_pe1mew_gateway_1" seems down! Last message was 7 minutes, 20 seconds ago.
2:10 AM Gateway "ttn_pe1mew_gateway_1" seems down! Last message was 27 minutes, 20 seconds ago.
2:20 AM Gateway "ttn_pe1mew_gateway_1" is back in operation since 01:20:02 2019-10-06.
4:10 AM Gateway "ttn_pe1mew_gateway_1" seems down! Last message was 4 minutes, 2 seconds ago.
4:30 AM Gateway "ttn_pe1mew_gateway_1" is back in operation since 03:29:09 2019-10-06.
6:00 AM Gateway "ttn_pe1mew_gateway_1" seems down! Last message was 10 minutes, 55 seconds ago.
6:20 AM Gateway "ttn_pe1mew_gateway_1" seems down! Last message was 8 minutes, 10 seconds ago.
6:30 AM Gateway "ttn_pe1mew_gateway_1" is back in operation since 05:28:59 2019-10-06.
7:00 AM Gateway "ttn_pe1mew_gateway_1" seems down! Last message was 6 minutes, 5 seconds ago.
7:10 AM Gateway "ttn_pe1mew_gateway_1" is back in operation since 06:09:56 2019-10-06.
8:10 AM Gateway "ttn_pe1mew_gateway_1" seems down! Last message was 7 minutes, 48 seconds ago.
8:30 AM Gateway "ttn_pe1mew_gateway_1" seems down! Last message was 27 minutes, 48 seconds ago.
9:00 AM Gateway "ttn_pe1mew_gateway_1" seems down! Last message was 57 minutes, 49 seconds ago.
9:30 AM Gateway "ttn_pe1mew_gateway_1" seems down! Last message was 1 hour, 27 minutes, 48 seconds ago.
9:50 AM Gateway "ttn_pe1mew_gateway_1" is back in operation since 08:50:01 2019-10-06.
11:00 AM Gateway "ttn_pe1mew_gateway_1" seems down! Last message was 4 minutes, 44 seconds ago.
11:10 AM Gateway "ttn_pe1mew_gateway_1" is back in operation since 10:10:00 2019-10-06.

router logging
Here is the log of my router:

Oct  5 16:26:41 dnsmasq-dhcp[239]: DHCPDISCOVER(br0) 00:1e:c0:3b:37:40 
Oct  5 16:26:41 dnsmasq-dhcp[239]: DHCPOFFER(br0) 192.168.20.152 00:1e:c0:3b:37:40 
Oct  5 16:26:41 dnsmasq-dhcp[239]: DHCPDISCOVER(br0) 00:1e:c0:3b:37:40 
Oct  5 16:26:41 dnsmasq-dhcp[239]: DHCPOFFER(br0) 192.168.20.152 00:1e:c0:3b:37:40 
Oct  5 16:26:41 dnsmasq-dhcp[239]: DHCPREQUEST(br0) 192.168.20.152 00:1e:c0:3b:37:40 
Oct  5 16:26:41 dnsmasq-dhcp[239]: DHCPACK(br0) 192.168.20.152 00:1e:c0:3b:37:40 THINGS-GATEWAY
-
Oct  5 17:30:28 dnsmasq-dhcp[239]: DHCPDISCOVER(br0) 00:1e:c0:3b:37:40 
Oct  5 17:30:28 dnsmasq-dhcp[239]: DHCPOFFER(br0) 192.168.20.152 00:1e:c0:3b:37:40 
Oct  5 17:30:28 dnsmasq-dhcp[239]: DHCPREQUEST(br0) 192.168.20.152 00:1e:c0:3b:37:40 
Oct  5 17:30:28 dnsmasq-dhcp[239]: DHCPACK(br0) 192.168.20.152 00:1e:c0:3b:37:40 THINGS-GATEWAY
-
Oct  5 17:33:42 dnsmasq-dhcp[239]: DHCPREQUEST(br0) 192.168.20.152 00:1e:c0:3b:37:40 
Oct  5 17:33:42 dnsmasq-dhcp[239]: DHCPACK(br0) 192.168.20.152 00:1e:c0:3b:37:40 THINGS-GATEWAY
-
Oct  5 18:52:29 dnsmasq-dhcp[239]: DHCPDISCOVER(br0) 00:1e:c0:3b:37:40 
Oct  5 18:52:29 dnsmasq-dhcp[239]: DHCPOFFER(br0) 192.168.20.152 00:1e:c0:3b:37:40 
Oct  5 18:52:29 dnsmasq-dhcp[239]: DHCPREQUEST(br0) 192.168.20.152 00:1e:c0:3b:37:40 
Oct  5 18:52:29 dnsmasq-dhcp[239]: DHCPACK(br0) 192.168.20.152 00:1e:c0:3b:37:40 THINGS-GATEWAY
-
Oct  5 19:25:03 dnsmasq-dhcp[239]: DHCPREQUEST(br0) 192.168.20.152 00:1e:c0:3b:37:40 
Oct  5 19:25:03 dnsmasq-dhcp[239]: DHCPACK(br0) 192.168.20.152 00:1e:c0:3b:37:40 THINGS-GATEWAY
-
Oct  5 19:59:17 dnsmasq-dhcp[239]: DHCPREQUEST(br0) 192.168.20.152 00:1e:c0:3b:37:40 
Oct  5 19:59:17 dnsmasq-dhcp[239]: DHCPACK(br0) 192.168.20.152 00:1e:c0:3b:37:40 THINGS-GATEWAY
-
Oct  5 20:00:37 dnsmasq-dhcp[239]: DHCPDISCOVER(br0) 00:1e:c0:3b:37:40 
Oct  5 20:00:37 dnsmasq-dhcp[239]: DHCPOFFER(br0) 192.168.20.152 00:1e:c0:3b:37:40 
Oct  5 20:00:37 dnsmasq-dhcp[239]: DHCPREQUEST(br0) 192.168.20.152 00:1e:c0:3b:37:40 
Oct  5 20:00:37 dnsmasq-dhcp[239]: DHCPACK(br0) 192.168.20.152 00:1e:c0:3b:37:40 THINGS-GATEWAY
-
Oct  5 20:33:25 dnsmasq-dhcp[239]: DHCPREQUEST(br0) 192.168.20.152 00:1e:c0:3b:37:40 
Oct  5 20:33:25 dnsmasq-dhcp[239]: DHCPACK(br0) 192.168.20.152 00:1e:c0:3b:37:40 THINGS-GATEWAY
-
Oct  5 20:58:26 dnsmasq-dhcp[239]: DHCPREQUEST(br0) 192.168.20.152 00:1e:c0:3b:37:40 
Oct  5 20:58:26 dnsmasq-dhcp[239]: DHCPACK(br0) 192.168.20.152 00:1e:c0:3b:37:40 THINGS-GATEWAY
-
Oct  5 20:59:17 dnsmasq-dhcp[239]: DHCPREQUEST(br0) 192.168.20.152 00:1e:c0:3b:37:40 
Oct  5 20:59:17 dnsmasq-dhcp[239]: DHCPACK(br0) 192.168.20.152 00:1e:c0:3b:37:40 THINGS-GATEWAY
-
Oct  5 21:01:14 dnsmasq-dhcp[239]: DHCPDISCOVER(br0) 00:1e:c0:3b:37:40 
Oct  5 21:01:14 dnsmasq-dhcp[239]: DHCPOFFER(br0) 192.168.20.152 00:1e:c0:3b:37:40 
Oct  5 21:01:16 dnsmasq-dhcp[239]: DHCPDISCOVER(br0) 192.168.20.152 00:1e:c0:3b:37:40 
Oct  5 21:01:16 dnsmasq-dhcp[239]: DHCPOFFER(br0) 192.168.20.152 00:1e:c0:3b:37:40 
Oct  5 21:01:16 dnsmasq-dhcp[239]: DHCPREQUEST(br0) 192.168.20.152 00:1e:c0:3b:37:40 
Oct  5 21:01:16 dnsmasq-dhcp[239]: DHCPACK(br0) 192.168.20.152 00:1e:c0:3b:37:40 THINGS-GATEWAY
Oct  5 21:01:20 dnsmasq-dhcp[239]: DHCPDISCOVER(br0) 192.168.20.152 00:1e:c0:3b:37:40 
Oct  5 21:01:20 dnsmasq-dhcp[239]: DHCPOFFER(br0) 192.168.20.152 00:1e:c0:3b:37:40 
Oct  5 21:01:28 dnsmasq-dhcp[239]: DHCPDISCOVER(br0) 192.168.20.152 00:1e:c0:3b:37:40 
Oct  5 21:01:28 dnsmasq-dhcp[239]: DHCPOFFER(br0) 192.168.20.152 00:1e:c0:3b:37:40 
Oct  5 21:01:28 dnsmasq-dhcp[239]: DHCPREQUEST(br0) 192.168.20.152 00:1e:c0:3b:37:40 
Oct  5 21:01:28 dnsmasq-dhcp[239]: DHCPACK(br0) 192.168.20.152 00:1e:c0:3b:37:40 THINGS-GATEWAY
Oct  5 21:01:50 dnsmasq-dhcp[239]: DHCPREQUEST(br0) 192.168.20.152 00:1e:c0:3b:37:40 
Oct  5 21:01:50 dnsmasq-dhcp[239]: DHCPACK(br0) 192.168.20.152 00:1e:c0:3b:37:40 THINGS-GATEWAY
-
Oct  5 21:12:28 dnsmasq-dhcp[239]: DHCPDISCOVER(br0) 00:1e:c0:3b:37:40 
Oct  5 21:12:28 dnsmasq-dhcp[239]: DHCPOFFER(br0) 192.168.20.152 00:1e:c0:3b:37:40 
Oct  5 21:12:29 dnsmasq-dhcp[239]: DHCPREQUEST(br0) 192.168.20.152 00:1e:c0:3b:37:40 
Oct  5 21:12:29 dnsmasq-dhcp[239]: DHCPACK(br0) 192.168.20.152 00:1e:c0:3b:37:40 THINGS-GATEWAY
-
Oct  5 21:45:52 dnsmasq-dhcp[239]: DHCPREQUEST(br0) 192.168.20.152 00:1e:c0:3b:37:40 
Oct  5 21:45:52 dnsmasq-dhcp[239]: DHCPACK(br0) 192.168.20.152 00:1e:c0:3b:37:40 THINGS-GATEWAY
-
Oct  5 21:51:17 dnsmasq-dhcp[239]: DHCPREQUEST(br0) 192.168.20.152 00:1e:c0:3b:37:40 
Oct  5 21:51:17 dnsmasq-dhcp[239]: DHCPACK(br0) 192.168.20.152 00:1e:c0:3b:37:40 THINGS-GATEWAY
-
Oct  5 21:52:16 dnsmasq-dhcp[239]: DHCPREQUEST(br0) 192.168.20.152 00:1e:c0:3b:37:40 
Oct  5 21:52:16 dnsmasq-dhcp[239]: DHCPACK(br0) 192.168.20.152 00:1e:c0:3b:37:40 THINGS-GATEWAY
-
Oct  5 21:59:55 dnsmasq-dhcp[239]: DHCPREQUEST(br0) 192.168.20.152 00:1e:c0:3b:37:40 
Oct  5 21:59:55 dnsmasq-dhcp[239]: DHCPACK(br0) 192.168.20.152 00:1e:c0:3b:37:40 THINGS-GATEWAY
-
Oct  5 22:12:57 dnsmasq-dhcp[239]: DHCPREQUEST(br0) 192.168.20.152 00:1e:c0:3b:37:40 
Oct  5 22:12:57 dnsmasq-dhcp[239]: DHCPACK(br0) 192.168.20.152 00:1e:c0:3b:37:40 THINGS-GATEWAY
-
Oct  5 22:46:30 dnsmasq-dhcp[239]: DHCPDISCOVER(br0) 00:1e:c0:3b:37:40 
Oct  5 22:46:30 dnsmasq-dhcp[239]: DHCPOFFER(br0) 192.168.20.152 00:1e:c0:3b:37:40 
Oct  5 22:46:30 dnsmasq-dhcp[239]: DHCPREQUEST(br0) 192.168.20.152 00:1e:c0:3b:37:40 
Oct  5 22:46:30 dnsmasq-dhcp[239]: DHCPACK(br0) 192.168.20.152 00:1e:c0:3b:37:40 THINGS-GATEWAY
-
Oct  5 23:10:21 dnsmasq-dhcp[239]: DHCPDISCOVER(br0) 00:1e:c0:3b:37:40 
Oct  5 23:10:21 dnsmasq-dhcp[239]: DHCPOFFER(br0) 192.168.20.152 00:1e:c0:3b:37:40 
Oct  5 23:10:21 dnsmasq-dhcp[239]: DHCPREQUEST(br0) 192.168.20.152 00:1e:c0:3b:37:40 
Oct  5 23:10:21 dnsmasq-dhcp[239]: DHCPACK(br0) 192.168.20.152 00:1e:c0:3b:37:40 THINGS-GATEWAY
-
Oct  5 23:13:56 dnsmasq-dhcp[239]: DHCPDISCOVER(br0) 00:1e:c0:3b:37:40 
Oct  5 23:13:56 dnsmasq-dhcp[239]: DHCPOFFER(br0) 192.168.20.152 00:1e:c0:3b:37:40 
Oct  5 23:13:58 dnsmasq-dhcp[239]: DHCPDISCOVER(br0) 00:1e:c0:3b:37:40 
Oct  5 23:13:58 dnsmasq-dhcp[239]: DHCPOFFER(br0) 192.168.20.152 00:1e:c0:3b:37:40 
Oct  5 23:13:58 dnsmasq-dhcp[239]: DHCPREQUEST(br0) 192.168.20.152 00:1e:c0:3b:37:40 
Oct  5 23:13:58 dnsmasq-dhcp[239]: DHCPACK(br0) 192.168.20.152 00:1e:c0:3b:37:40 THINGS-GATEWAY
-
Oct  5 23:29:15 dnsmasq-dhcp[239]: DHCPREQUEST(br0) 192.168.20.152 00:1e:c0:3b:37:40 
Oct  5 23:29:15 dnsmasq-dhcp[239]: DHCPACK(br0) 192.168.20.152 00:1e:c0:3b:37:40 THINGS-GATEWAY
-
Oct  5 23:31:24 dnsmasq-dhcp[239]: DHCPREQUEST(br0) 192.168.20.152 00:1e:c0:3b:37:40 
Oct  5 23:31:24 dnsmasq-dhcp[239]: DHCPACK(br0) 192.168.20.152 00:1e:c0:3b:37:40 THINGS-GATEWAY
-
Oct  5 23:33:36 dnsmasq-dhcp[239]: DHCPDISCOVER(br0) 00:1e:c0:3b:37:40 
Oct  5 23:33:36 dnsmasq-dhcp[239]: DHCPOFFER(br0) 192.168.20.152 00:1e:c0:3b:37:40 
Oct  5 23:33:39 dnsmasq-dhcp[239]: DHCPDISCOVER(br0) 00:1e:c0:3b:37:40 
Oct  5 23:33:39 dnsmasq-dhcp[239]: DHCPOFFER(br0) 192.168.20.152 00:1e:c0:3b:37:40 
Oct  5 23:33:39 dnsmasq-dhcp[239]: DHCPREQUEST(br0) 192.168.20.152 00:1e:c0:3b:37:40 
Oct  5 23:33:39 dnsmasq-dhcp[239]: DHCPACK(br0) 192.168.20.152 00:1e:c0:3b:37:40 THINGS-GATEWAY
-
Oct  6 00:16:11 dnsmasq-dhcp[239]: DHCPDISCOVER(br0) 00:1e:c0:3b:37:40 
Oct  6 00:16:11 dnsmasq-dhcp[239]: DHCPOFFER(br0) 192.168.20.152 00:1e:c0:3b:37:40 
Oct  6 00:16:11 dnsmasq-dhcp[239]: DHCPREQUEST(br0) 192.168.20.152 00:1e:c0:3b:37:40 
Oct  6 00:16:11 dnsmasq-dhcp[239]: DHCPACK(br0) 192.168.20.152 00:1e:c0:3b:37:40 THINGS-GATEWAY
-
Oct  6 02:10:11 dnsmasq-dhcp[239]: DHCPREQUEST(br0) 192.168.20.152 00:1e:c0:3b:37:40 
Oct  6 02:10:11 dnsmasq-dhcp[239]: DHCPACK(br0) 192.168.20.152 00:1e:c0:3b:37:40 THINGS-GATEWAY
-
Oct  6 02:13:15 dnsmasq-dhcp[239]: DHCPREQUEST(br0) 192.168.20.152 00:1e:c0:3b:37:40 
Oct  6 02:13:15 dnsmasq-dhcp[239]: DHCPACK(br0) 192.168.20.152 00:1e:c0:3b:37:40 THINGS-GATEWAY
-
Oct  6 02:18:12 dnsmasq-dhcp[239]: DHCPDISCOVER(br0) 00:1e:c0:3b:37:40 
Oct  6 02:18:12 dnsmasq-dhcp[239]: DHCPOFFER(br0) 192.168.20.152 00:1e:c0:3b:37:40 
Oct  6 02:18:12 dnsmasq-dhcp[239]: DHCPREQUEST(br0) 192.168.20.152 00:1e:c0:3b:37:40 
Oct  6 02:18:12 dnsmasq-dhcp[239]: DHCPACK(br0) 192.168.20.152 00:1e:c0:3b:37:40 THINGS-GATEWAY
-
Oct  6 02:21:18 dnsmasq-dhcp[239]: DHCPREQUEST(br0) 192.168.20.152 00:1e:c0:3b:37:40 
Oct  6 02:21:18 dnsmasq-dhcp[239]: DHCPACK(br0) 192.168.20.152 00:1e:c0:3b:37:40 THINGS-GATEWAY
-
Oct  6 02:24:30 dnsmasq-dhcp[239]: DHCPREQUEST(br0) 192.168.20.152 00:1e:c0:3b:37:40 
Oct  6 02:24:30 dnsmasq-dhcp[239]: DHCPACK(br0) 192.168.20.152 00:1e:c0:3b:37:40 THINGS-GATEWAY
-
Oct  6 02:26:43 dnsmasq-dhcp[239]: DHCPREQUEST(br0) 192.168.20.152 00:1e:c0:3b:37:40 
Oct  6 02:26:43 dnsmasq-dhcp[239]: DHCPACK(br0) 192.168.20.152 00:1e:c0:3b:37:40 THINGS-GATEWAY
-
Oct  6 02:27:28 dnsmasq-dhcp[239]: DHCPREQUEST(br0) 192.168.20.152 00:1e:c0:3b:37:40 
Oct  6 02:27:28 dnsmasq-dhcp[239]: DHCPACK(br0) 192.168.20.152 00:1e:c0:3b:37:40 THINGS-GATEWAY
-
Oct  6 02:28:21 dnsmasq-dhcp[239]: DHCPREQUEST(br0) 192.168.20.152 00:1e:c0:3b:37:40 
Oct  6 02:28:21 dnsmasq-dhcp[239]: DHCPACK(br0) 192.168.20.152 00:1e:c0:3b:37:40 THINGS-GATEWAY
-
Oct  6 02:38:39 dnsmasq-dhcp[239]: DHCPDISCOVER(br0) 00:1e:c0:3b:37:40 
Oct  6 02:38:39 dnsmasq-dhcp[239]: DHCPOFFER(br0) 192.168.20.152 00:1e:c0:3b:37:40 
Oct  6 02:38:39 dnsmasq-dhcp[239]: DHCPREQUEST(br0) 192.168.20.152 00:1e:c0:3b:37:40 
Oct  6 02:38:39 dnsmasq-dhcp[239]: DHCPACK(br0) 192.168.20.152 00:1e:c0:3b:37:40 THINGS-GATEWAY
-
Oct  6 02:53:23 dnsmasq-dhcp[239]: DHCPREQUEST(br0) 192.168.20.152 00:1e:c0:3b:37:40 
Oct  6 02:53:23 dnsmasq-dhcp[239]: DHCPACK(br0) 192.168.20.152 00:1e:c0:3b:37:40 THINGS-GATEWAY
-
Oct  6 02:57:57 dnsmasq-dhcp[239]: DHCPREQUEST(br0) 192.168.20.152 00:1e:c0:3b:37:40 
Oct  6 02:57:57 dnsmasq-dhcp[239]: DHCPACK(br0) 192.168.20.152 00:1e:c0:3b:37:40 THINGS-GATEWAY
-
Oct  6 03:10:32 dnsmasq-dhcp[239]: DHCPREQUEST(br0) 192.168.20.152 00:1e:c0:3b:37:40 
Oct  6 03:10:32 dnsmasq-dhcp[239]: DHCPACK(br0) 192.168.20.152 00:1e:c0:3b:37:40 THINGS-GATEWAY
-
Oct  6 03:23:42 dnsmasq-dhcp[239]: DHCPREQUEST(br0) 192.168.20.152 00:1e:c0:3b:37:40 
Oct  6 03:23:42 dnsmasq-dhcp[239]: DHCPACK(br0) 192.168.20.152 00:1e:c0:3b:37:40 THINGS-GATEWAY
-
Oct  6 03:27:51 dnsmasq-dhcp[239]: DHCPREQUEST(br0) 192.168.20.152 00:1e:c0:3b:37:40 
Oct  6 03:27:51 dnsmasq-dhcp[239]: DHCPACK(br0) 192.168.20.152 00:1e:c0:3b:37:40 THINGS-GATEWAY
-
Oct  6 03:36:11 dnsmasq-dhcp[239]: DHCPREQUEST(br0) 192.168.20.152 00:1e:c0:3b:37:40 
Oct  6 03:36:11 dnsmasq-dhcp[239]: DHCPACK(br0) 192.168.20.152 00:1e:c0:3b:37:40 THINGS-GATEWAY
-
Oct  6 03:38:33 dnsmasq-dhcp[239]: DHCPREQUEST(br0) 192.168.20.152 00:1e:c0:3b:37:40 
Oct  6 03:38:33 dnsmasq-dhcp[239]: DHCPACK(br0) 192.168.20.152 00:1e:c0:3b:37:40 THINGS-GATEWAY
-
Oct  6 03:47:01 dnsmasq-dhcp[239]: DHCPREQUEST(br0) 192.168.20.152 00:1e:c0:3b:37:40 
Oct  6 03:47:01 dnsmasq-dhcp[239]: DHCPACK(br0) 192.168.20.152 00:1e:c0:3b:37:40 THINGS-GATEWAY
-
Oct  6 04:11:19 dnsmasq-dhcp[239]: DHCPREQUEST(br0) 192.168.20.152 00:1e:c0:3b:37:40 
Oct  6 04:11:19 dnsmasq-dhcp[239]: DHCPACK(br0) 192.168.20.152 00:1e:c0:3b:37:40 THINGS-GATEWAY
-
Oct  6 04:27:03 dnsmasq-dhcp[239]: DHCPREQUEST(br0) 192.168.20.152 00:1e:c0:3b:37:40 
Oct  6 04:27:03 dnsmasq-dhcp[239]: DHCPACK(br0) 192.168.20.152 00:1e:c0:3b:37:40 THINGS-GATEWAY
-
Oct  6 04:30:18 dnsmasq-dhcp[239]: DHCPDISCOVER(br0) 00:1e:c0:3b:37:40 
Oct  6 04:30:18 dnsmasq-dhcp[239]: DHCPOFFER(br0) 192.168.20.152 00:1e:c0:3b:37:40 
Oct  6 04:30:18 dnsmasq-dhcp[239]: DHCPREQUEST(br0) 192.168.20.152 00:1e:c0:3b:37:40 
Oct  6 04:30:18 dnsmasq-dhcp[239]: DHCPACK(br0) 192.168.20.152 00:1e:c0:3b:37:40 THINGS-GATEWAY
-
Oct  6 05:02:12 dnsmasq-dhcp[239]: DHCPREQUEST(br0) 192.168.20.152 00:1e:c0:3b:37:40 
Oct  6 05:02:12 dnsmasq-dhcp[239]: DHCPACK(br0) 192.168.20.152 00:1e:c0:3b:37:40 THINGS-GATEWAY
-
Oct  6 05:20:20 dnsmasq-dhcp[239]: DHCPREQUEST(br0) 192.168.20.152 00:1e:c0:3b:37:40 
Oct  6 05:20:20 dnsmasq-dhcp[239]: DHCPACK(br0) 192.168.20.152 00:1e:c0:3b:37:40 THINGS-GATEWAY
-
Oct  6 07:40:58 dnsmasq-dhcp[239]: DHCPDISCOVER(br0) 00:1e:c0:3b:37:40 
Oct  6 07:40:58 dnsmasq-dhcp[239]: DHCPOFFER(br0) 192.168.20.152 00:1e:c0:3b:37:40 
Oct  6 07:40:58 dnsmasq-dhcp[239]: DHCPREQUEST(br0) 192.168.20.152 00:1e:c0:3b:37:40 
Oct  6 07:40:58 dnsmasq-dhcp[239]: DHCPACK(br0) 192.168.20.152 00:1e:c0:3b:37:40 THINGS-GATEWAY
-
Oct  6 08:35:41 dnsmasq-dhcp[239]: DHCPREQUEST(br0) 192.168.20.152 00:1e:c0:3b:37:40 
Oct  6 08:35:41 dnsmasq-dhcp[239]: DHCPACK(br0) 192.168.20.152 00:1e:c0:3b:37:40 THINGS-GATEWAY
Oct  6 08:35:43 dnsmasq-dhcp[239]: DHCPDISCOVER(br0) 192.168.20.152 00:1e:c0:3b:37:40 
Oct  6 08:35:43 dnsmasq-dhcp[239]: DHCPOFFER(br0) 192.168.20.152 00:1e:c0:3b:37:40 
Oct  6 08:35:47 dnsmasq-dhcp[239]: DHCPDISCOVER(br0) 192.168.20.152 00:1e:c0:3b:37:40 
Oct  6 08:35:47 dnsmasq-dhcp[239]: DHCPOFFER(br0) 192.168.20.152 00:1e:c0:3b:37:40 
-
Oct  6 08:36:13 dnsmasq-dhcp[239]: DHCPDISCOVER(br0) 192.168.20.152 00:1e:c0:3b:37:40 
Oct  6 08:36:13 dnsmasq-dhcp[239]: DHCPOFFER(br0) 192.168.20.152 00:1e:c0:3b:37:40 
Oct  6 08:36:44 dnsmasq-dhcp[239]: DHCPDISCOVER(br0) 192.168.20.152 00:1e:c0:3b:37:40 
Oct  6 08:36:44 dnsmasq-dhcp[239]: DHCPOFFER(br0) 192.168.20.152 00:1e:c0:3b:37:40 
Oct  6 08:36:44 dnsmasq-dhcp[239]: DHCPREQUEST(br0) 192.168.20.152 00:1e:c0:3b:37:40 
Oct  6 08:36:44 dnsmasq-dhcp[239]: DHCPACK(br0) 192.168.20.152 00:1e:c0:3b:37:40 THINGS-GATEWAY
-
Oct  6 08:38:49 dnsmasq-dhcp[239]: DHCPDISCOVER(br0) 00:1e:c0:3b:37:40 
Oct  6 08:38:49 dnsmasq-dhcp[239]: DHCPOFFER(br0) 192.168.20.152 00:1e:c0:3b:37:40 
Oct  6 08:38:49 dnsmasq-dhcp[239]: DHCPREQUEST(br0) 192.168.20.152 00:1e:c0:3b:37:40 
Oct  6 08:38:49 dnsmasq-dhcp[239]: DHCPACK(br0) 192.168.20.152 00:1e:c0:3b:37:40 THINGS-GATEWAY
-
Oct  6 08:40:59 dnsmasq-dhcp[239]: DHCPDISCOVER(br0) 00:1e:c0:3b:37:40 
Oct  6 08:40:59 dnsmasq-dhcp[239]: DHCPOFFER(br0) 192.168.20.152 00:1e:c0:3b:37:40 
-
Oct  6 08:41:02 dnsmasq-dhcp[239]: DHCPDISCOVER(br0) 00:1e:c0:3b:37:40 
Oct  6 08:41:02 dnsmasq-dhcp[239]: DHCPOFFER(br0) 192.168.20.152 00:1e:c0:3b:37:40 
Oct  6 08:41:02 dnsmasq-dhcp[239]: DHCPREQUEST(br0) 192.168.20.152 00:1e:c0:3b:37:40 
Oct  6 08:41:02 dnsmasq-dhcp[239]: DHCPACK(br0) 192.168.20.152 00:1e:c0:3b:37:40 THINGS-GATEWAY
Oct  6 08:41:27 dnsmasq-dhcp[239]: DHCPREQUEST(br0) 192.168.20.152 00:1e:c0:3b:37:40 
Oct  6 08:41:27 dnsmasq-dhcp[239]: DHCPACK(br0) 192.168.20.152 00:1e:c0:3b:37:40 THINGS-GATEWAY
-
Oct  6 08:49:38 dnsmasq-dhcp[239]: DHCPREQUEST(br0) 192.168.20.152 00:1e:c0:3b:37:40 
Oct  6 08:49:38 dnsmasq-dhcp[239]: DHCPACK(br0) 192.168.20.152 00:1e:c0:3b:37:40 THINGS-GATEWAY
-
Oct  6 09:01:27 dnsmasq-dhcp[239]: DHCPREQUEST(br0) 192.168.20.152 00:1e:c0:3b:37:40 
Oct  6 09:01:27 dnsmasq-dhcp[239]: DHCPACK(br0) 192.168.20.152 00:1e:c0:3b:37:40 THINGS-GATEWAY
-
Oct  6 09:02:21 dnsmasq-dhcp[239]: DHCPREQUEST(br0) 192.168.20.152 00:1e:c0:3b:37:40 
Oct  6 09:02:21 dnsmasq-dhcp[239]: DHCPACK(br0) 192.168.20.152 00:1e:c0:3b:37:40 THINGS-GATEWAY
Oct  6 09:03:01 crond[242]: crond: USER admin pid 15999 cmd service start_vpnserver2

My question is: what to do next? Can I connect a more sofisticated logger to the gateway? let me know how I can help you.

Cu, Remko.

[Henrikc (Henrik)]

My TT GW was working great, all 4 LED’s on and steady.

I was watching the GW traffic on my laptop, and when I pulled the same page up on my mobile, the packets stopped coming through and the GW’s LED status looks like:
1: On, steady
2: Blinking slowly
3: On, steady
4: Off

Does anyone know why the GW might be ‘crashing’ like this, and what this arrangement of LEDs means?

Cheers

[BoRRoZ]

Reset Button

• Pressing the button shortly while powered on restarts the gateway.
• Holding the button for 2 seconds while powered on it erased the WiFi settings.
• Holding the button for 5 seconds while powered on it erases the WiFi settings and activation settings.
• Holding the button while powering on it will erase the full serial flash

LED Indication

LED	State	Reason	Cause	User Action
1 - Power	Off	No software is running	No power; Incorrect firmware loaded.	Make sure the device is powered and the correct firmware is loaded.
	On	Software is loaded
	Slow	Software update in progress		Wait
2 - Internet	Fast	No Ethernet or WiFi connection. Only possible way to connect is via the Gateway’s AP.	No Ethernet link and WiFi connection failed	Connect to TTN gateway - AP
	Slow	Checking for internet
	On	Has internet
3 - Configuration	Fast	Bad configuration	No ID	Need to configure a gateway ID on the device
	Already activated	Need to configure valid key on the device
	Invalid key	Need to configure valid keey on the device
	No router	Need to configure router in the TTN console
	Invalid URL	Correct URL in the TTN console
	Slow	Activating
	On	Activation successful
4 - Connection	Slow	Connecting		MQTT
	On	Connected		MQTT
5 - Activity	Single	Uplink/Downlink

[psy0rz]

How many channels does TTN gateway have? I’ve searched everything and I cant find anything.

All the other types do specify the number of channels, except for this one??