GW connected but no traffic diplayed on console

1

I m trying to set up a Kerlink IOT gw for the fisrt time on TTN network.
On the console when i power my GW i can see my GW eui-7276ff0008060264 is connected but unfortunalely statistics remains

Received Messages 0

Transmitted Messages 0

I dont see any traffic for the GW
i use SPF packet forwarder in the GW

Below my GW status

root@Wirnet_08060264 ~]# get_version -u

KERNEL_VER=3.10.104-3.10.104-klk7

PIC_VER=8.3

BOOTSTRAP_VER=""

UBOOT_VER=“U-Boot 2009.03-2009.03-klk1 (Feb 25 2019 - 18:10:47)”

SCRIPT_VER=v1.0

INITRAMFS_VER=v1.3

FILESYSTEM_VER=2016.05v1.13

KNETD_VER=“wirma2_v4.10 WAN_3.16 (Dec 21 2018-15:52:45)”

PROD_FW=wirmaV2_wirnet_v3.6

LORABOARD_MANUFACTURER=00

LORABOARD_TYPE=“868-27dBm”

LORABOARD_HWVERSION=05

LORABOARD_SERIALNO=000473

[root@Wirnet_08060264 ~]#

did someone already face such issue ?

I have tried to configure a thing uno node
AppEUI: 70B3D57ED0025D52
DevEUI: 0004A30B001E0C4F

Version: 1.0.3

Sending: mac set deveui 0004A30B001E0C4F

Sending: mac set adr off

Sending: mac set deveui 0004A30B001E0C4F

Sending: mac set appeui 70B3D57ED0025D52

Sending: mac set appkey 79C6AB308FCC5CD037D4E7E454B081E3

Sending: mac save

Sending: mac set rx2 3 869525000

Sending: mac set ch drrange 1 0 6

Sending: mac set ch dcycle 0 799

Sending: mac set ch dcycle 1 799

Sending: mac set ch dcycle 2 799

Sending: mac set ch dcycle 3 799

Sending: mac set ch freq 3 867100000

Sending: mac set ch drrange 3 0 5

Sending: mac set ch status 3 on

Sending: mac set ch dcycle 4 799

Sending: mac set ch freq 4 867300000

Sending: mac set ch drrange 4 0 5

Sending: mac set ch status 4 on

Sending: mac set ch dcycle 5 799

Sending: mac set ch freq 5 867500000

Sending: mac set ch drrange 5 0 5

Sending: mac set ch status 5 on

Sending: mac set ch dcycle 6 799

Sending: mac set ch freq 6 867700000

Sending: mac set ch drrange 6 0 5

Sending: mac set ch status 6 on

Sending: mac set ch dcycle 7 799

Sending: mac set ch freq 7 867900000

Sending: mac set ch drrange 7 0 5

Sending: mac set ch status 7 on

Sending: mac set pwridx 1

Sending: mac set retx 7

Sending: mac set dr 5

Sending: mac join otaa

Join not accepted: denied

Check your coverage, keys and backend status.

Sending: mac join otaa

Join not accepted: denied

Check your coverage, keys and backend status.

Sending: mac join otaa

Join not accepted: denied

Check your coverage, keys and backend status.

Sending: mac join otaa

Response is not OK: no_free_ch

Send join command failed

Sending: mac join otaa

Response is not OK: no_free_ch

Send join command failed

Sending: mac join otaa

Response is not OK: no_free_ch

Send join command failed

Sending: mac join otaa

Response is not OK: no_free_ch

Send join command failed

Sending: mac join otaa

Response is not OK: no_free_ch

Send join command failed

Sending: mac join otaa

Response is not OK: no_free_ch

Send join command failed

Sending: mac join otaa

Response is not OK: no_free_ch

Send join command failed

Sending: mac join otaa

Response is not OK: no_free_ch

Send join command failed

Sending: mac join otaa

Response is not OK: no_free_ch

Send join command failed

Sending: mac join otaa

Response is not OK: no_free_ch

Send join command failed

Sending: mac join otaa

Response is not OK: no_free_ch

Send join command failed

Sending: mac join otaa

Response is not OK: no_free_ch

Send join command failed

2

Can you follow a log on the gateway and see if the packet forwarder is running and if it is receiving packets?

I don’t know where your gateway would log this, on some it might be something like tail -f /var/log/syslog or sudo journalctl -f

3

Below the logs i have

[root@Wirnet_08060264 etc]# tail -f /mnt/fsuser-1/spf/var/log/spf.log
Dec 5 17:32:50 Wirnet local1.notice spf: # BEACON sent so far: 0
Dec 5 17:32:50 Wirnet local1.notice spf: # BEACON rejected: 0
Dec 5 17:32:50 Wirnet local1.notice spf: ### [JIT] ###
Dec 5 17:32:50 Wirnet local1.notice spf: /home/drd/jenkins/workspace/spf_release/lora_pkt_fwd/src/jitqueue.c:448:jit_print_queue(): INFO: [jit] queue is empty
Dec 5 17:32:50 Wirnet local1.notice spf: ### [GPS] ###
Dec 5 17:32:50 Wirnet local1.notice spf: # Invalid time reference (age: 1575567170 sec)
Dec 5 17:32:50 Wirnet local1.notice spf: # no valid GPS coordinates available yet
Dec 5 17:32:50 Wirnet local1.notice spf: ##### END #####
Dec 5 17:32:50 Wirnet local1.notice spf: JSON up: {“stat”:{“time”:“2019-12-05 17:32:50 GMT”,“rxnb”:0,“rxok”:0,“rxfw”:0,“ackr”:100.0,“dwnb”:0,“txnb”:0,“ping”:43}}
Dec 5 17:32:50 Wirnet local1.notice spf: INFO: [up] PUSH_ACK received in 32 ms
Dec 5 17:33:00 Wirnet local1.notice spf: INFO: [down] PULL_ACK received in 42.90 ms
Dec 5 17:33:10 Wirnet local1.notice spf: INFO: [down] PULL_ACK received in 42.27 ms
Dec 5 17:33:20 Wirnet local1.notice spf: INFO: [down] PULL_ACK received in 42.03 ms
Dec 5 17:33:20 Wirnet local1.notice spf: ##### 2019-12-05 17:33:20 GMT #####
Dec 5 17:33:20 Wirnet local1.notice spf: ### [UPSTREAM] ###
Dec 5 17:33:20 Wirnet local1.notice spf: # RF packets received by concentrator: 0
Dec 5 17:33:20 Wirnet local1.notice spf: # CRC_OK: 0.00%, CRC_FAIL: 0.00%, NO_CRC: 0.00%
Dec 5 17:33:20 Wirnet local1.notice spf: # RF packets forwarded: 0 (0 bytes)
Dec 5 17:33:20 Wirnet local1.notice spf: # PUSH_DATA datagrams sent: 1 (123 bytes)
Dec 5 17:33:20 Wirnet local1.notice spf: # PUSH_DATA acknowledged: 100.00%
Dec 5 17:33:20 Wirnet local1.notice spf: ### [DOWNSTREAM] ###
Dec 5 17:33:20 Wirnet local1.notice spf: # PULL_DATA sent: 3 (100.00% acknowledged, ping 42.03 ms)
Dec 5 17:33:20 Wirnet local1.notice spf: # PULL_RESP(onse) datagrams received: 0 (0 bytes)
Dec 5 17:33:20 Wirnet local1.notice spf: # RF packets sent to concentrator: 0 (0 bytes)
Dec 5 17:33:20 Wirnet local1.notice spf: # TX errors: 0
Dec 5 17:33:20 Wirnet local1.notice spf: # BEACON queued: 0
Dec 5 17:33:20 Wirnet local1.notice spf: # BEACON sent so far: 0
Dec 5 17:33:20 Wirnet local1.notice spf: # BEACON rejected: 0
Dec 5 17:33:20 Wirnet local1.notice spf: ### [JIT] ###
Dec 5 17:33:20 Wirnet local1.notice spf: /home/drd/jenkins/workspace/spf_release/lora_pkt_fwd/src/jitqueue.c:448:jit_print_queue(): INFO: [jit] queue is empty
Dec 5 17:33:20 Wirnet local1.notice spf: ### [GPS] ###
Dec 5 17:33:20 Wirnet local1.notice spf: # Invalid time reference (age: 1575567200 sec)
Dec 5 17:33:20 Wirnet local1.notice spf: # no valid GPS coordinates available yet
Dec 5 17:33:20 Wirnet local1.notice spf: ##### END #####
Dec 5 17:33:20 Wirnet local1.notice spf: JSON up: {“stat”:{“time”:“2019-12-05 17:33:20 GMT”,“rxnb”:0,“rxok”:0,“rxfw”:0,“ackr”:100.0,“dwnb”:0,“txnb”:0,“ping”:42}}
Dec 5 17:33:20 Wirnet local1.notice spf: INFO: [up] PUSH_ACK received in 31 ms
Dec 5 17:33:29 Wirnet local1.notice spf: INFO: [down] PULL_ACK received in 41.76 ms
Dec 5 17:33:40 Wirnet local1.notice spf: INFO: [down] PULL_ACK received in 41.45 ms
Dec 5 17:33:50 Wirnet local1.notice spf: INFO: [down] PULL_ACK received in 41.55 ms
Dec 5 17:33:50 Wirnet local1.notice spf: INFO: Disabling GPS mode for concentrator’s counter…
Dec 5 17:33:50 Wirnet local1.notice spf: INFO: host/sx1301 time offset=(1575566628s:276241µs) - drift=-155µs
Dec 5 17:33:50 Wirnet local1.notice spf: INFO: Enabling GPS mode for concentrator’s counter.
Dec 5 17:33:50 Wirnet local1.notice spf: ##### 2019-12-05 17:33:50 GMT #####
Dec 5 17:33:50 Wirnet local1.notice spf: ### [UPSTREAM] ###
Dec 5 17:33:50 Wirnet local1.notice spf: # RF packets received by concentrator: 0
Dec 5 17:33:50 Wirnet local1.notice spf: # CRC_OK: 0.00%, CRC_FAIL: 0.00%, NO_CRC: 0.00%
Dec 5 17:33:50 Wirnet local1.notice spf: # RF packets forwarded: 0 (0 bytes)
Dec 5 17:33:50 Wirnet local1.notice spf: # PUSH_DATA datagrams sent: 1 (123 bytes)
Dec 5 17:33:50 Wirnet local1.notice spf: # PUSH_DATA acknowledged: 100.00%
Dec 5 17:33:50 Wirnet local1.notice spf: ### [DOWNSTREAM] ###
Dec 5 17:33:50 Wirnet local1.notice spf: # PULL_DATA sent: 3 (100.00% acknowledged, ping 41.55 ms)
Dec 5 17:33:50 Wirnet local1.notice spf: # PULL_RESP(onse) datagrams received: 0 (0 bytes)
Dec 5 17:33:50 Wirnet local1.notice spf: # RF packets sent to concentrator: 0 (0 bytes)
Dec 5 17:33:50 Wirnet local1.notice spf: # TX errors: 0
Dec 5 17:33:50 Wirnet local1.notice spf: # BEACON queued: 0
Dec 5 17:33:50 Wirnet local1.notice spf: # BEACON sent so far: 0
Dec 5 17:33:50 Wirnet local1.notice spf: # BEACON rejected: 0
Dec 5 17:33:50 Wirnet local1.notice spf: ### [JIT] ###
Dec 5 17:33:50 Wirnet local1.notice spf: /home/drd/jenkins/workspace/spf_release/lora_pkt_fwd/src/jitqueue.c:448:jit_print_queue(): INFO: [jit] queue is empty
Dec 5 17:33:50 Wirnet local1.notice spf: ### [GPS] ###
Dec 5 17:33:50 Wirnet local1.notice spf: # Invalid time reference (age: 1575567230 sec)
Dec 5 17:33:50 Wirnet local1.notice spf: # no valid GPS coordinates available yet
Dec 5 17:33:50 Wirnet local1.notice spf: ##### END #####
Dec 5 17:33:50 Wirnet local1.notice spf: JSON up: {“stat”:{“time”:“2019-12-05 17:33:50 GMT”,“rxnb”:0,“rxok”:0,“rxfw”:0,“ackr”:100.0,“dwnb”:0,“txnb”:0,“ping”:42}}
Dec 5 17:33:50 Wirnet local1.notice spf: INFO: [up] PUSH_ACK received in 28 ms
Dec 5 17:33:56 Wirnet local1.notice spf: INFO: Received pkt from mote: D0025D52 (fcnt=46037)
Dec 5 17:33:56 Wirnet local1.notice spf: JSON up: {“rxpk”:[{“tmst”:608032267,“time”:“2019-12-05T17:33:56Z”,“chan”:1,“rfch”:1,“freq”:868.300000,“stat”:1,“modu”:“LORA”,“datr”:“SF7BW125”,“codr”:“4/5”,“lsnr”:8.8,“rssi”:nan,“size”:23,“data”:“AFJdAtB+1bNwTwweAAujBADxR5cmTmw=”
Dec 5 17:34:00 Wirnet local1.notice spf: INFO: [down] PULL_ACK received in 41.48 ms
Dec 5 17:34:03 Wirnet local1.notice spf: INFO: Received pkt from mote: D0025D52 (fcnt=46037)
Dec 5 17:34:03 Wirnet local1.notice spf: JSON up: {“rxpk”:[{“tmst”:615168619,“time”:“2019-12-05T17:34:03Z”,“chan”:2,“rfch”:1,“freq”:868.500000,“stat”:1,“modu”:“LORA”,“datr”:“SF7BW125”,“codr”:“4/5”,“lsnr”:7.0,“rssi”:nan,“size”:23,“data”:“AFJdAtB+1bNwTwweAAujBADxMJEh+6A=”
Dec 5 17:34:10 Wirnet local1.notice spf: INFO: [down] PULL_ACK received in 41.18 ms
Dec 5 17:34:10 Wirnet local1.notice spf: INFO: Received pkt from mote: D0025D52 (fcnt=46037)
Dec 5 17:34:10 Wirnet local1.notice spf: JSON up: {“rxpk”:[{“tmst”:622305179,“time”:“2019-12-05T17:34:10Z”,“chan”:0,“rfch”:1,“freq”:868.100000,“stat”:1,“modu”:“LORA”,“datr”:“SF7BW125”,“codr”:“4/5”,“lsnr”:8.8,“rssi”:nan,“size”:23,“data”:“AFJdAtB+1bNwTwweAAujBAAQLH3ln30=”
Dec 5 17:34:19 Wirnet local1.notice spf: INFO: [down] PULL_ACK received in 41.57 ms
Dec 5 17:34:20 Wirnet local1.notice spf: ##### 2019-12-05 17:34:20 GMT #####
Dec 5 17:34:20 Wirnet local1.notice spf: ### [UPSTREAM] ###
Dec 5 17:34:20 Wirnet local1.notice spf: # RF packets received by concentrator: 3
Dec 5 17:34:20 Wirnet local1.notice spf: # CRC_OK: 100.00%, CRC_FAIL: 0.00%, NO_CRC: 0.00%
Dec 5 17:34:20 Wirnet local1.notice spf: # RF packets forwarded: 3 (69 bytes)
Dec 5 17:34:20 Wirnet local1.notice spf: # PUSH_DATA datagrams sent: 4 (828 bytes)
Dec 5 17:34:20 Wirnet local1.notice spf: # PUSH_DATA acknowledged: 25.00%
Dec 5 17:34:20 Wirnet local1.notice spf: ### [DOWNSTREAM] ###
Dec 5 17:34:20 Wirnet local1.notice spf: # PULL_DATA sent: 3 (100.00% acknowledged, ping 41.57 ms)
Dec 5 17:34:20 Wirnet local1.notice spf: # PULL_RESP(onse) datagrams received: 0 (0 bytes)
Dec 5 17:34:20 Wirnet local1.notice spf: # RF packets sent to concentrator: 0 (0 bytes)
Dec 5 17:34:20 Wirnet local1.notice spf: # TX errors: 0
Dec 5 17:34:20 Wirnet local1.notice spf: # BEACON queued: 0
Dec 5 17:34:20 Wirnet local1.notice spf: # BEACON sent so far: 0
Dec 5 17:34:20 Wirnet local1.notice spf: # BEACON rejected: 0
Dec 5 17:34:20 Wirnet local1.notice spf: ### [JIT] ###
Dec 5 17:34:20 Wirnet local1.notice spf: /home/drd/jenkins/workspace/spf_release/lora_pkt_fwd/src/jitqueue.c:448:jit_print_queue(): INFO: [jit] queue is empty
Dec 5 17:34:20 Wirnet local1.notice spf: ### [GPS] ###
Dec 5 17:34:20 Wirnet local1.notice spf: # Invalid time reference (age: 1575567260 sec)
Dec 5 17:34:20 Wirnet local1.notice spf: # no valid GPS coordinates available yet
Dec 5 17:34:20 Wirnet local1.notice spf: ##### END #####
Dec 5 17:34:20 Wirnet local1.notice spf: JSON up: {“stat”:{“time”:“2019-12-05 17:34:20 GMT”,“rxnb”:3,“rxok”:3,“rxfw”:3,“ackr”:25.0,“dwnb”:0,“txnb”:0,“ping”:42}}
Dec 5 17:34:20 Wirnet local1.notice spf: INFO: [up] PUSH_ACK received in 28 ms
Dec 5 17:34:30 Wirnet local1.notice spf: INFO: [down] PULL_ACK received in 41.56 ms

4

That shows everything to be working.

Are you really seeing nothing in the TTN gateway traffic page?

One of your packets looks to be a join request, that it doesn’t seem to trigger a join accept suggests that the node details are not entered the same way in TTN, or else that the join nonce is being re-used, causing the packet to look like an attack that should be silently ignored, rather than a valid join.

(Of course it could trigger a join accept that is being routed by some other gateway)

Except, wait a second…

JSON up: {“rxpk”:[{“tmst”:608032267,“time”:“2019-12-05T17:33:56Z”,“chan”:1,“rfch”:1,“freq”:868.300000,“stat”:1,“modu”:“LORA”,“datr”:“SF7BW125”,“codr”:“4/5”,“lsnr”:8.8,“rssi”:nan,“size”:23,“data”:“AFJdAtB+1bNwTwweAAujBADxR5cmTmw=”

That is not right. RSSI should be a number. My guess is this would lead the TTN stack to conclude the signal report is corrupt and ignore it.

Perhaps someone more familiar with this gateway / packet forwarder can comment? I guess it’s possible this could actually be routine behavior, if the SNR is being used for routing decisions rather than the RSSI. But a valid RSSI really should be being reported.

Could there be something wrong in a radio-path / antenna compensation table leading to an invalid RSSI?

1 Like
5

i saw nothing in the console
Received Messages and Transmitted Messages remains to 0
Nothing is displayed in traffic console

6

Indeed, please make sure you have the gateway’s Traffic page in TTN Console open before making the node send its Join Request. It will not show traffic that was received before that page was opened in a browser.

Indeed; for future readers, this is one of those:

Above, the line saying “Received pkt from mote: D0025D52 (fcnt=46037)” is actually wrong, as the gateway assumes it’s a regular uplink and erroneously decodes the non-encrypted parts for its log. However, a Join Request is encoded differently (and includes neither a DevAddr nor a frame counter), so that first line can be ignored. The second indeed is a Join Request.

Even when the AppEUI, AppKey or DevEUI would not match whatever is registered in TTN Console, the gateway’s Traffic page would still show such Join Request, but no Join Accept. (The application’s or node’s Data page would not show it, if not matched.) The gateway’s Traffic page also shows packets that are for other providers, and are ignored. It should also show errors such as described in OTAA shows "Activation DevNonce not valid: already used".

As TTN does seem to accept the status messages, then if there’s really nothing in the gateway’s Traffic page, then I’d say that the gateway’s connection settings are fine. So, I’d say that indeed TTN is rejecting the gateway’s uplink messages for some other reason, like maybe the “nan”. (Nice find!)

7

I still block on this . I have try to delete recreate the gateway. But gateway is connected but i never see the traffic. Nobody has an idea to debug this ? is there traces to provide ?

E..(i.@.@..y....4.L..k.....,.l..rv.....d
19:39:44.212258 IP 52.169.76.203.1700 > 192.168.1.30.36715: UDP, length 4
E.. .x@./.r.4.L........k.....l..................t.
19:39:51.286062 IP 192.168.1.30.42867 > 52.169.76.203.1700: UDP, length 235
E...kx@.@..3....4.L..s....,.....rv.....d{"rxpk":[{"tmst":719405219,"time":"2019-12-09T19:39:51Z","chan":0,"rfch":1,"freq":868.100000,"stat":1,"modu":"LORA","datr":"SF7BW125","codr":"4/5","lsnr":8.8,"rssi":nan,"size":23,"data":"AFJdAtB+1bNwTwweAAujBAD5eQMwppg="}]}
19:39:54.211301 IP 192.168.1.30.36715 > 52.169.76.203.1700: UDP, length 12
E..(l.@.@..x....4.L..k....}w.!+.rv.....d
19:39:54.251252 IP 52.169.76.203.1700 > 192.168.1.30.36715: UDP, length 4
E.. .R@./.m@4.L........k...f.!+................Z.=
19:39:54.734935 IP 192.168.1.30.42867 > 52.169.76.203.1700: UDP, length 122
E...l:@.@.......4.L..s....-
....rv.....d{"stat":{"time":"2019-12-09 19:39:54 GMT","rxnb":2,"rxok":2,"rxfw":2,"ackr":33.3,"dwnb":0,"txnb":0,"ping":42}}
19:39:54.762166 IP 52.169.76.203.1700 > 192.168.1.30.42867: UDP, length 4
E.. .X@.0.l:4.L........s......................ou..
19:40:04.251293 IP 192.168.1.30.36715 > 52.169.76.203.1700: UDP, length 12
E..(m.@.@.......4.L..k.....C.U..rv.....d
19:40:04.295861 IP 52.169.76.203.1700 > 192.168.1.30.36715: UDP, length 4
E.. ..@./.i.4.L........k...2.U.................Ib;
19:40:07.434573 IP 192.168.1.30.42867 > 52.169.76.203.1700: UDP, length 235
E...o.@.@.......4.L..s........p.rv.....d{"rxpk":[{"tmst":735542259,"time":"2019-12-09T19:40:07Z","chan":1,"rfch":1,"freq":868.300000,"stat":1,"modu":"LORA","datr":"SF7BW125","codr":"4/5","lsnr":9.0,"rssi":nan,"size":23,"data":"AFJdAtB+1bNwTwweAAujBAAEfmb2ZNM="}]}
19:40:14.291443 IP 192.168.1.30.36715 > 52.169.76.203.1700: UDP, length 12
E..(o.@.@.......4.L..k....4...s.rv.....d
19:40:14.332562 IP 52.169.76.203.1700 > 192.168.1.30.36715: UDP, length 4
E.. ..@./.h.4.L........k......s................xT2
19:40:24.131871 IP 192.168.1.30.36715 > 52.169.76.203.1700: UDP, length 12
E..(p.@.@.......4.L..k.....].;..rv.....d
19:40:24.173826 IP 52.169.76.203.1700 > 192.168.1.30.36715: UDP, length 4
E.. ..@./.`.4.L........k.. M.;.................e..
19:40:24.738240 IP 192.168.1.30.42867 > 52.169.76.203.1700: UDP, length 122
E...p.@.@..;....4.L..s.....].\..rv.....d{"stat":{"time":"2019-12-09 19:40:24 GMT","rxnb":1,"rxok":1,"rxfw":1,"ackr":50.0,"dwnb":0,"txnb":0,"ping":43}}
19:40:24.774191 IP 52.169.76.203.1700 > 192.168.1.30.42867: UDP, length 4
E.. ..@.0._.4.L........s..9&.\................;H..
19:40:34.171277 IP 192.168.1.30.36715 > 52.169.76.203.1700: UDP, length 12
E..(s.@.@.......4.L..k.....b.6..rv.....d
19:40:34.212424 IP 52.169.76.203.1700 > 192.168.1.30.36715: UDP, length 4
E.. ..@./.`{4.L........k...Q.6....................
19:40:44.211458 IP 192.168.1.30.36715 > 52.169.76.203.1700: UDP, length 12
E..(v.@.@.......4.L..k..........rv.....d
19:40:44.251139 IP 52.169.76.203.1700 > 192.168.1.30.36715: UDP, length 4
E.. .?@./.`S4.L........k..t....................O..
19:40:54.251276 IP 192.168.1.30.36715 > 52.169.76.203.1700: UDP, length 12
E..(x.@.@.~.....4.L..k..........rv.....d
19:40:54.293794 IP 52.169.76.203.1700 > 192.168.1.30.36715: UDP, length 4
E.. ..@./.[.4.L........k..3..................."v..
19:40:54.748773 IP 192.168.1.30.42867 > 52.169.76.203.1700: UDP, length 123
E...x.@.@.~P....4.L..s....u.....rv.....d{"stat":{"time":"2019-12-09 19:40:54 GMT","rxnb":0,"rxok":0,"rxfw":0,"ackr":100.0,"dwnb":0,"txnb":0,"ping":43}}
19:40:54.779481 IP 52.169.76.203.1700 > 192.168.1.30.42867: UDP, length 4
E.. .*@.0.Zh4.L........s..m...................Wq4.
19:41:04.291486 IP 192.168.1.30.36715 > 52.169.76.203.1700: UDP, length 12
E..(||@.@.{.....4.L..k....vI.O2.rv.....d
19:41:04.332607 IP 52.169.76.203.1700 > 192.168.1.30.36715: UDP, length 4
E.. .r@./.U 4.L........k...8.O2...................
19:41:14.132004 IP 192.168.1.30.36715 > 52.169.76.203.1700: UDP, length 12
E..(})@.@.za....4.L..k...._...I.rv.....d
19:41:14.174073 IP 52.169.76.203.1700 > 192.168.1.30.36715: UDP, length 4
E.. .q@./.P!4.L........k...r..I.................+:
19:41:24.171859 IP 192.168.1.30.36715 > 52.169.76.203.1700: UDP, length 12
E..(}@@.@.zJ....4.L..k....%.....rv.....d
19:41:24.212789 IP 52.169.76.203.1700 > 192.168.1.30.36715: UDP, length 4
E.. ..@./.K.4.L........k..........................
19:41:24.754129 IP 192.168.1.30.42867 > 52.169.76.203.1700: UDP, length 123
E...}r@.@.y.....4.L..s....m{.N..rv.....d{"stat":{"time":"2019-12-09 19:41:24 GMT","rxnb":0,"rxok":0,"rxfw":0,"ackr":100.0,"dwnb":0,"txnb":0,"ping":43}}
19:41:24.784325 IP 52.169.76.203.1700 > 192.168.1.30.42867: UDP, length 4
E.. .%@.0.Jm4.L........s..c4.N................->P.
19:41:34.211442 IP 192.168.1.30.36715 > 52.169.76.203.1700: UDP, length 12
E..(..@.@.v.....4.L..k....8...p.rv.....d
19:41:34.251562 IP 52.169.76.203.1700 > 192.168.1.30.36715: UDP, length 4
E.. .6@./.G\4.L........k......p................JP.
19:41:44.251296 IP 192.168.1.30.36715 > 52.169.76.203.1700: UDP, length 12
E..(..@.@.s.....4.L..k..........rv.....d
19:41:44.290369 IP 52.169.76.203.1700 > 192.168.1.30.36715: UDP, length 4
E.. .6@./.?\4.L........k..q...................  ...
19:41:54.291572 IP 192.168.1.30.36715 > 52.169.76.203.1700: UDP, length 12
E..(..@.@.q.....4.L..k........).rv.....d
19:41:54.332736 IP 52.169.76.203.1700 > 192.168.1.30.36715: UDP, length 4
E.. ..@./.8.4.L........k......)...............^ke(
19:41:54.752997 IP 192.168.1.30.42867 > 52.169.76.203.1700: UDP, length 123
E.....@.@.pj....4.L..s.....u.TH.rv.....d{"stat":{"time":"2019-12-09 19:41:54 GMT","rxnb":0,"rxok":0,"rxfw":0,"ackr":100.0,"dwnb":0,"txnb":0,"ping":41}}
19:41:54.783759 IP 52.169.76.203.1700 > 192.168.1.30.42867: UDP, length 4
E.. .0@.0.7b4.L........s.....TH..................D
19:42:04.132105 IP 192.168.1.30.36715 > 52.169.76.203.1700: UDP, length 12
E..(..@.@.o.....4.L..k........
.rv.....d
19:42:04.174174 IP 52.169.76.203.1700 > 192.168.1.30.36715: UDP, length 4
E.. ..@./.5.4.L........k......
................4M.
19:42:14.171878 IP 192.168.1.30.36715 > 52.169.76.203.1700: UDP, length 12
E..(..@.@.m.....4.L..k..........rv.....d
19:42:14.213178 IP 52.169.76.203.1700 > 192.168.1.30.36715: UDP, length 4
E.. .L@./.2F4.L........k..N.....................[.
19:42:23.876021 IP 192.168.1.30.42867 > 52.169.76.203.1700: UDP, length 235
E....s@.@.j8....4.L..s.....d....rv.....d{"rxpk":[{"tmst":871987659,"time":"2019-12-09T19:42:23Z","chan":2,"rfch":1,"freq":868.500000,"stat":1,"modu":"LORA","datr":"SF7BW125","codr":"4/5","lsnr":7.0,"rssi":nan,"size":23,"data":"AFJdAtB+1bNwTwweAAujBACjOpuAxP0="}]}
19:42:24.211397 IP 192.168.1.30.36715 > 52.169.76.203.1700: UDP, length 12
E..(.x@.@.k.....4.L..k....c...D.rv.....d
19:42:24.252284 IP 52.169.76.203.1700 > 192.168.1.30.36715: UDP, length 4
E.. ..@./.,.4.L........k......D...............K.H.
19:42:24.753773 IP 192.168.1.30.42867 > 52.169.76.203.1700: UDP, length 122
E.....@.@.j.....4.L..s........[.rv.....d{"stat":{"time":"2019-12-09 19:42:24 GMT","rxnb":1,"rxok":1,"rxfw":1,"ackr":50.0,"dwnb":0,"txnb":0,"ping":43}}
19:42:24.788773 IP 52.169.76.203.1700 > 192.168.1.30.42867: UDP, length 4
E.. .E@.0.+M4.L........s......[...............Yu:g
19:42:34.251319 IP 192.168.1.30.36715 > 52.169.76.203.1700: UDP, length 12
E..(..@.@.h.....4.L..k..........rv.....d
19:42:34.291041 IP 52.169.76.203.1700 > 192.168.1.30.36715: UDP, length 4
E.. .9@./.*Y4.L........k......................^...
19:42:44.291346 IP 192.168.1.30.36715 > 52.169.76.203.1700: UDP, length 12
E..(.m@.@.e.....4.L..k.....K.L..rv.....d
19:42:44.335890 IP 52.169.76.203.1700 > 192.168.1.30.36715: UDP, length 4
E.. ..@./.'.4.L........k..M;.L....................
19:42:54.131668 IP 192.168.1.30.36715 > 52.169.76.203.1700: UDP, length 12
E..(.K@.@.b?....4.L..k.....k.-..rv.....d
19:42:54.171746 IP 52.169.76.203.1700 > 192.168.1.30.36715: UDP, length 4
E.. ..@./.$.4.L........k...Z.-................1.,.
19:42:54.757293 IP 192.168.1.30.42867 > 52.169.76.203.1700: UDP, length 123
E....v@.@.a.....4.L..s.......   B.rv.....d{"stat":{"time":"2019-12-09 19:42:54 GMT","rxnb":0,"rxok":0,"rxfw":0,"ackr":100.0,"dwnb":0,"txnb":0,"ping":43}}
19:42:54.789821 IP 52.169.76.203.1700 > 192.168.1.30.42867: UDP, length 4
E.. .C@.0.#O4.L........s...y.   B..................N
19:43:04.171297 IP 192.168.1.30.36715 > 52.169.76.203.1700: UDP, length 12
E..(..@.@.`.....4.L..k..........rv.....d
19:43:04.211003 IP 52.169.76.203.1700 > 192.168.1.30.36715: UDP, length 4
E.. ..@./...4.L........k......................iN..
19:43:10.090159 IP 192.168.1.30.42867 > 52.169.76.203.1700: UDP, length 235
E.....@.@.^.....4.L..s....{...3.rv.....d{"rxpk":[{"tmst":918201547,"time":"2019-12-09T19:43:10Z","chan":1,"rfch":1,"freq":868.300000,"stat":1,"modu":"LORA","datr":"SF7BW125","codr":"4/5","lsnr":9.2,"rssi":nan,"size":23,"data":"AFJdAtB+1bNwTwweAAujBACxczQc3+A="}]}
19:43:14.211291 IP 192.168.1.30.36715 > 52.169.76.203.1700: UDP, length 12
E..(..@.@.].....4.L..k..........rv.....d
19:43:14.251559 IP 52.169.76.203.1700 > 192.168.1.30.36715: UDP, length 4
E.. .4@./..^4.L........k..V...................6f^1
19:43:24.251303 IP 192.168.1.30.36715 > 52.169.76.203.1700: UDP, length 12
E..(.B@.@.]H....4.L..k....#.....rv.....d
19:43:24.290582 IP 52.169.76.203.1700 > 192.168.1.30.36715: UDP, length 4
E.. ..@./...4.L........k......................-..;
19:43:24.787351 IP 192.168.1.30.42867 > 52.169.76.203.1700: UDP, length 122
E....t@.@.\.....4.L..s...."=..-.rv.....d{"stat":{"time":"2019-12-09 19:43:24 GMT","rxnb":1,"rxok":1,"rxfw":1,"ackr":50.0,"dwnb":0,"txnb":0,"ping":41}}
19:43:24.828030 IP 52.169.76.203.1700 > 192.168.1.30.42867: UDP, length 4
E.. ..@.0...4.L........s......-.................6.
19:43:26.222724 IP 192.168.1.30.42867 > 52.169.76.203.1700: UDP, length 235
E.....@.@.[.....4.L..s..........rv.....d{"rxpk":[{"tmst":934339083,"time":"2019-12-09T19:43:26Z","chan":0,"rfch":1,"freq":868.100000,"stat":1,"modu":"LORA","datr":"SF7BW125","codr":"4/5","lsnr":9.5,"rssi":nan,"size":23,"data":"AFJdAtB+1bNwTwweAAujBAAcJcnKsXo="}]}
19:43:34.291270 IP 192.168.1.30.36715 > 52.169.76.203.1700: UDP, length 12
E..(..@.@.\     ....4.L..k....a".vG.rv.....d
19:43:34.332590 IP 52.169.76.203.1700 > 192.168.1.30.36715: UDP, length 4
E.. ..@./...4.L........k.....vG................;.p
19:43:44.131281 IP 192.168.1.30.36715 > 52.169.76.203.1700: UDP, length 12
E..(.A@.@.[I....4.L..k....u...2.rv.....d
19:43:44.170757 IP 52.169.76.203.1700 > 192.168.1.30.36715: UDP, length 4
E.. ..@./...4.L........k......2...............c/3.
19:43:54.171416 IP 192.168.1.30.36715 > 52.169.76.203.1700: UDP, length 12
E..(..@.@.X.....4.L..k.....{....rv.....d
19:43:54.213138 IP 52.169.76.203.1700 > 192.168.1.30.36715: UDP, length 4
E.. ..@./...4.L........k..8k....................}E
19:43:54.788367 IP 192.168.1.30.42867 > 52.169.76.203.1700: UDP, length 122
E....9@.@.W.....4.L..s.....p.J..rv.....d{"stat":{"time":"2019-12-09 19:43:54 GMT","rxnb":1,"rxok":1,"rxfw":1,"ackr":50.0,"dwnb":0,"txnb":0,"ping":42}}
19:43:54.824264 IP 52.169.76.203.1700 > 192.168.1.30.42867: UDP, length 4
E.. ..@.0...4.L........s..H8.J....................
19:44:04.211268 IP 192.168.1.30.36715 > 52.169.76.203.1700: UDP, length 12
E..(..@.@.V.....4.L..k.....g.0..rv.....d
19:44:04.252103 IP 52.169.76.203.1700 > 192.168.1.30.36715: UDP, length 4
E.. ..@./...4.L........k...W.0..................!.
19:44:14.251441 IP 192.168.1.30.36715 > 52.169.76.203.1700: UDP, length 12
E..(..@.@.S.....4.L..k.....x. #.rv.....d
19:44:14.290911 IP 52.169.76.203.1700 > 192.168.1.30.36715: UDP, length 4
E.. ..@./..e4.L........k...h. #...............*.).
19:44:24.291273 IP 192.168.1.30.36715 > 52.169.76.203.1700: UDP, length 12
E..(..@.@.P.....4.L..k....<...l.rv.....d
19:44:24.333357 IP 52.169.76.203.1700 > 192.168.1.30.36715: UDP, length 4
E..
d@./...4.L........k......l...............CW..
19:44:24.802492 IP 192.168.1.30.42867 > 52.169.76.203.1700: UDP, length 123
E.....@.@.P4....4.L..s....`.....rv.....d{"stat":{"time":"2019-12-09 19:44:24 GMT","rxnb":0,"rxok":0,"rxfw":0,"ackr":100.0,"dwnb":0,"txnb":0,"ping":43}}
19:44:24.837471 IP 52.169.76.203.1700 > 192.168.1.30.42867: UDP, length 4
E..
n@.0..$4.L........s..Y....................i.O
19:44:25.942387 IP 192.168.1.30.42867 > 52.169.76.203.1700: UDP, length 236
E.....@.@.O.....4.L..s..........rv.....d{"rxpk":[{"tmst":994031948,"time":"2019-12-09T19:44:25Z","chan":7,"rfch":0,"freq":867.900000,"stat":1,"modu":"LORA","datr":"SF12BW125","codr":"4/5","lsnr":9.2,"rssi":nan,"size":23,"data":"QJZTnQ+ALAIIffYQeo85SEfOoz6CMZY="}]}
19:44:34.131716 IP 192.168.1.30.36715 > 52.169.76.203.1700: UDP, length 12
E..(.C@.@.PG....4.L..k..........rv.....d
19:44:34.170936 IP 52.169.76.203.1700 > 192.168.1.30.36715: UDP, length 4
E.. .;@./..W4.L........k..7....................)r.
19:44:44.171713 IP 192.168.1.30.36715 > 52.169.76.203.1700: UDP, length 12
E..(..@.@.O.....4.L..k..........rv.....d
19:44:44.214396 IP 52.169.76.203.1700 > 192.168.1.30.36715: UDP, length 4
E.. ..@./...4.L........k..k|..................a..M
19:44:54.211277 IP 192.168.1.30.36715 > 52.169.76.203.1700: UDP, length 12
E..(..@.@.N}....4.L..k.....w. ..rv.....d
19:44:54.252298 IP 52.169.76.203.1700 > 192.168.1.30.36715: UDP, length 4
E.. .`@./..24.L........k..jg. ................t(.7
19:44:54.804064 IP 192.168.1.30.42867 > 52.169.76.203.1700: UDP, length 122
E.....@.@.N.....4.L..s.....3....rv.....d{"stat":{"time":"2019-12-09 19:44:54 GMT","rxnb":1,"rxok":1,"rxfw":1,"ackr":50.0,"dwnb":0,"txnb":0,"ping":43}}
19:44:54.840057 IP 52.169.76.203.1700 > 192.168.1.30.42867: UDP, length 4
E.. .i@.0..)4.L........s..H.....................i.
19:45:04.251403 IP 192.168.1.30.36715 > 52.169.76.203.1700: UDP, length 12
E..(..@.@.Lw....4.L..k.....Z.>..rv.....d
19:45:04.291329 IP 52.169.76.203.1700 > 192.168.1.30.36715: UDP, length 4
E.. ..@./...4.L........k...J.>................[..z
19:45:14.291281 IP 192.168.1.30.36715 > 52.169.76.203.1700: UDP, length 12
E..(.l@.@.J.....4.L..k..........rv.....d
19:45:14.333661 IP 52.169.76.203.1700 > 192.168.1.30.36715: UDP, length 4
E.. !.@./...4.L........k..7...................."=+
19:45:24.131726 IP 192.168.1.30.36715 > 52.169.76.203.1700: UDP, length 12
E..(.h@.@.H"....4.L..k....@...g.rv.....d
19:45:24.171380 IP 52.169.76.203.1700 > 192.168.1.30.36715: UDP, length 4
E.. (.@./...4.L........k......g...............m..1
19:45:24.802950 IP 192.168.1.30.42867 > 52.169.76.203.1700: UDP, length 123
E.....@.@.G{....4.L..s....\..3..rv.....d{"stat":{"time":"2019-12-09 19:45:24 GMT","rxnb":0,"rxok":0,"rxfw":0,"ackr":100.0,"dwnb":0,"txnb":0,"ping":42}}
19:45:24.836454 IP 52.169.76.203.1700 > 192.168.1.30.42867: UDP, length 4
E.. (.@.0...4.L........s..UO.3.................<..
19:45:32.644392 IP 192.168.1.30.42867 > 52.169.76.203.1700: UDP, length 236
E.....@.@.F.....4.L..s........P.rv.....d{"rxpk":[{"tmst":1060760531,"time":"2019-12-09T19:45:32Z","chan":2,"rfch":1,"freq":868.500000,"stat":1,"modu":"LORA","datr":"SF7BW125","codr":"4/5","lsnr":7.0,"rssi":nan,"size":23,"data":"AFJdAtB+1bNwTwweAAujBACKVFfkLv0="}]}
19:45:34.171425 IP 192.168.1.30.36715 > 52.169.76.203.1700: UDP, length 12
E..(..@.@.Gq....4.L..k..........rv.....d
19:45:34.210710 IP 52.169.76.203.1700 > 192.168.1.30.36715: UDP, length 4
E.. 0C@./..O4.L........k..@....................h..
19:45:44.211293 IP 192.168.1.30.36715 > 52.169.76.203.1700: UDP, length 12
E..(.=@.@.DM....4.L..k..........rv.....d
19:45:44.252806 IP 52.169.76.203.1700 > 192.168.1.30.36715: UDP, length 4
E.. 3.@./...4.L........k..Qs..................e..,
19:45:54.251423 IP 192.168.1.30.36715 > 52.169.76.203.1700: UDP, length 12
E..(..@.@.A.....4.L..k....s...4.rv.....d
19:45:54.291857 IP 52.169.76.203.1700 > 192.168.1.30.36715: UDP, length 4
E.. :8@./..Z4.L........k......4..................1
19:45:54.803354 IP 192.168.1.30.42867 > 52.169.76.203.1700: UDP, length 122
E.....@.@.A.....4.L..s........^.rv.....d{"stat":{"time":"2019-12-09 19:45:54 GMT","rxnb":1,"rxok":1,"rxfw":1,"ackr":50.0,"dwnb":0,"txnb":0,"ping":41}}
19:45:54.844870 IP 52.169.76.203.1700 > 192.168.1.30.42867: UDP, length 4
E.. :|@.0...4.L........s......^...................
19:46:04.291281 IP 192.168.1.30.36715 > 52.169.76.203.1700: UDP, length 12
E..(..@.@.@r....4.L..k..........rv.....d
19:46:04.330621 IP 52.169.76.203.1700 > 192.168.1.30.36715: UDP, length 4
E.. >.@./...4.L........k..1....................*..
19:46:14.131712 IP 192.168.1.30.36715 > 52.169.76.203.1700: UDP, length 12
E..(.&@.@.>d....4.L..k..........rv.....d
19:46:14.172305 IP 52.169.76.203.1700 > 192.168.1.30.36715: UDP, length 4
E.. A.@./...4.L........k..|w..................l..M
19:46:24.171351 IP 192.168.1.30.36715 > 52.169.76.203.1700: UDP, length 12
E..(..@.@.;.....4.L..k..........rv.....d
19:46:24.211012 IP 52.169.76.203.1700 > 192.168.1.30.36715: UDP, length 4
E.. F`@./..24.L........k.........................5
19:46:24.805868 IP 192.168.1.30.42867 > 52.169.76.203.1700: UDP, length 123
E....$@.@.:.....4.L..s.....6....rv.....d{"stat":{"time":"2019-12-09 19:46:24 GMT","rxnb":0,"rxok":0,"rxfw":0,"ackr":100.0,"dwnb":0,"txnb":0,"ping":41}}
19:46:24.848755 IP 52.169.76.203.1700 > 192.168.1.30.42867: UDP, length 4
E.. F.@.0...4.L........s..
.....................[.
19:46:28.885443 IP 192.168.1.30.42867 > 52.169.76.203.1700: UDP, length 236
E.....@.@.9.....4.L..s....Qz....rv.....d{"rxpk":[{"tmst":1117000811,"time":"2019-12-09T19:46:28Z","chan":0,"rfch":1,"freq":868.100000,"stat":1,"modu":"LORA","datr":"SF7BW125","codr":"4/5","lsnr":9.5,"rssi":nan,"size":23,"data":"AFJdAtB+1bNwTwweAAujBABTNMbEIyQ="}]}
19:46:34.211277 IP 192.168.1.30.36715 > 52.169.76.203.1700: UDP, length 12
E..(.G@.@.9C....4.L..k....c...D.rv.....d
19:46:34.253623 IP 52.169.76.203.1700 > 192.168.1.30.36715: UDP, length 4
E.. N.@./...4.L........k......D.................I.
19:46:44.251346 IP 192.168.1.30.36715 > 52.169.76.203.1700: UDP, length 12
E..(..@.@.5.....4.L..k.......x..rv.....d
19:46:44.293055 IP 52.169.76.203.1700 > 192.168.1.30.36715: UDP, length 4
E.. R.@./...4.L........k..*..x................:o..
19:46:45.026440 IP 192.168.1.30.42867 > 52.169.76.203.1700: UDP, length 236
E.....@.@.4.....4.L..s....r8.Ii.rv.....d{"rxpk":[{"tmst":1133137619,"time":"2019-12-09T19:46:45Z","chan":1,"rfch":1,"freq":868.300000,"stat":1,"modu":"LORA","datr":"SF7BW125","codr":"4/5","lsnr":9.8,"rssi":nan,"size":23,"data":"AFJdAtB+1bNwTwweAAujBABPD6t8nFM="}]}
19:46:54.291546 IP 192.168.1.30.36715 > 52.169.76.203.1700: UDP, length 12
E..(.c@.@.3'....4.L..k........#.rv.....d
19:46:54.331461 IP 52.169.76.203.1700 > 192.168.1.30.36715: UDP, length 4
E.. Xc@./../4.L........k......#.................}.
19:46:54.802197 IP 192.168.1.30.42867 > 52.169.76.203.1700: UDP, length 122
E.....@.@.2.....4.L..s..../.....rv.....d{"stat":{"time":"2019-12-09 19:46:54 GMT","rxnb":2,"rxok":2,"rxfw":2,"ackr":33.3,"dwnb":0,"txnb":0,"ping":42}}
19:46:54.843348 IP 52.169.76.203.1700 > 192.168.1.30.42867: UDP, length 4
E.. X.@.0...4.L........s......................SCth
19:47:04.131984 IP 192.168.1.30.36715 > 52.169.76.203.1700: UDP, length 12
E..(..@.@.1.....4.L..k....>...i.rv.....d
19:47:04.172724 IP 52.169.76.203.1700 > 192.168.1.30.36715: UDP, length 4
E.. a5@./..]4.L........k......i.................o.
19:47:14.171286 IP 192.168.1.30.36715 > 52.169.76.203.1700: UDP, length 12
E..(..@.@.0.....4.L..k....*..j~.rv.....d
19:47:14.211491 IP 52.169.76.203.1700 > 192.168.1.30.36715: UDP, length 4
E.. d.@./...4.L........k.....j~...............4.#>
19:47:24.211433 IP 192.168.1.30.36715 > 52.169.76.203.1700: UDP, length 12
E..(./@.@.-[....4.L..k....*L.L~.rv.....d
19:47:24.253940 IP 52.169.76.203.1700 > 192.168.1.30.36715: UDP, length 4
E.. k]@./..54.L........k...;.L~...............S.:.
19:47:24.821086 IP 192.168.1.30.42867 > 52.169.76.203.1700: UDP, length 123
E....d@.@.,.....4.L..s.....x.Q%.rv.....d{"stat":{"time":"2019-12-09 19:47:24 GMT","rxnb":0,"rxok":0,"rxfw":0,"ackr":100.0,"dwnb":0,"txnb":0,"ping":42}}
19:47:24.865225 IP 52.169.76.203.1700 > 192.168.1.30.42867: UDP, length 4
E.. k.@.0...4.L........s...1.Q%.................q.
19:47:34.251410 IP 192.168.1.30.36715 > 52.169.76.203.1700: UDP, length 12
E..(..@.@.).....4.L..k...._...H.rv.....d
19:47:34.292250 IP 52.169.76.203.1700 > 192.168.1.30.36715: UDP, length 4
E.. q.@./...4.L........k......H................./.
19:47:44.291411 IP 192.168.1.30.36715 > 52.169.76.203.1700: UDP, length 12
E..(..@.@.%.....4.L..k....U...S.rv.....d
19:47:44.331244 IP 52.169.76.203.1700 > 192.168.1.30.36715: UDP, length 4
E.. x.@./...4.L........k......S................m.w
19:47:54.131729 IP 192.168.1.30.36715 > 52.169.76.203.1700: UDP, length 12
E..(.S@.@.#7....4.L..k.....^.:..rv.....d
19:47:54.172913 IP 52.169.76.203.1700 > 192.168.1.30.36715: UDP, length 4
E.. z.@./...4.L........k...M.:..................c.
19:47:54.824303 IP 192.168.1.30.42867 > 52.169.76.203.1700: UDP, length 123
E....]@.@.".....4.L..s........1.rv.....d{"stat":{"time":"2019-12-09 19:47:54 GMT","rxnb":0,"rxok":0,"rxfw":0,"ackr":100.0,"dwnb":0,"txnb":0,"ping":42}}
19:47:54.865678 IP 52.169.76.203.1700 > 192.168.1.30.42867: UDP, length 4
E.. z.@.0...4.L........s......1...............v..z
19:48:04.171861 IP 192.168.1.30.36715 > 52.169.76.203.1700: UDP, length 12
E..(..@.@. t....4.L..k..........rv.....d
19:48:04.211456 IP 52.169.76.203.1700 > 192.168.1.30.36715: UDP, length 4
E.. ..@./...4.L........k.........................5
19:48:14.211421 IP 192.168.1.30.36715 > 52.169.76.203.1700: UDP, length 12
E..(..@.@.......4.L..k....Qf.2W.rv.....d
19:48:14.250509 IP 52.169.76.203.1700 > 192.168.1.30.36715: UDP, length 4
E.. ..@./.~.4.L........k...U.2W..................<
19:48:24.251290 IP 192.168.1.30.36715 > 52.169.76.203.1700: UDP, length 12
E..(..@.@.......4.L..k.....S.D..rv.....d
19:48:24.292822 IP 52.169.76.203.1700 > 192.168.1.30.36715: UDP, length 4
E.. ..@./.y.4.L........k..6C.D.................4.j
19:48:24.821682 IP 192.168.1.30.42867 > 52.169.76.203.1700: UDP, length 123
E.....@.@.......4.L..s....T.....rv.....d{"stat":{"time":"2019-12-09 19:48:24 GMT","rxnb":0,"rxok":0,"rxfw":0,"ackr":100.0,"dwnb":0,"txnb":0,"ping":42}}
19:48:24.864523 IP 52.169.76.203.1700 > 192.168.1.30.42867: UDP, length 4
E.. .(@.0.xj4.L........s..O....................v<G
19:48:34.291546 IP 192.168.1.30.36715 > 52.169.76.203.1700: UDP, length 12
E..(.x@.@.......4.L..k..........rv.....d
19:48:34.331314 IP 52.169.76.203.1700 > 192.168.1.30.36715: UDP, length 4
E.. ..@./.t.4.L........k..>......................m
19:48:44.132071 IP 192.168.1.30.36715 > 52.169.76.203.1700: UDP, length 12
E..(.5@.@..U....4.L..k.....r.%..rv.....d
19:48:44.172923 IP 52.169.76.203.1700 > 192.168.1.30.36715: UDP, length 4
E.. ..@./.p~4.L........k..Ub.%.................=..
19:48:51.447047 IP 192.168.1.30.42867 > 52.169.76.203.1700: UDP, length 236
E....G@.@..c....4.L..s..........rv.....d{"rxpk":[{"tmst":1259557483,"time":"2019-12-09T19:48:51Z","chan":2,"rfch":1,"freq":868.500000,"stat":1,"modu":"LORA","datr":"SF7BW125","codr":"4/5","lsnr":7.5,"rssi":nan,"size":23,"data":"AFJdAtB+1bNwTwweAAujBAArb2vw8g8="}]}
19:48:54.171314 IP 192.168.1.30.36715 > 52.169.76.203.1700: UDP, length 12
E..(.`@.@..*....4.L..k..........rv.....d
19:48:54.211965 IP 52.169.76.203.1700 > 192.168.1.30.36715: UDP, length 4
E.. ..@./.m.4.L........k..A...................QF.h
19:48:54.823164 IP 192.168.1.30.42867 > 52.169.76.203.1700: UDP, length 122
E....q@.@.......4.L..s.....\.^S.rv.....d{"stat":{"time":"2019-12-09 19:48:54 GMT","rxnb":1,"rxok":1,"rxfw":1,"ackr":50.0,"dwnb":0,"txnb":0,"ping":42}}
19:48:54.865630 IP 52.169.76.203.1700 > 192.168.1.30.42867: UDP, length 4
E.. .-@.0.le4.L........s...$.^S................_..
19:49:04.211427 IP 192.168.1.30.36715 > 52.169.76.203.1700: UDP, length 12
E..(..@.@.......4.L..k.....7.`..rv.....d
19:49:04.250696 IP 52.169.76.203.1700 > 192.168.1.30.36715: UDP, length 4
E.. ..@./.i.4.L........k..z'.`................w...
19:49:14.251294 IP 192.168.1.30.36715 > 52.169.76.203.1700: UDP, length 12
E..(.$@.@..f....4.L..k..........rv.....d
19:49:14.292935 IP 52.169.76.203.1700 > 192.168.1.30.36715: UDP, length 4
E.. ..@./.a.4.L........k..q.......................
19:49:24.291582 IP 192.168.1.30.36715 > 52.169.76.203.1700: UDP, length 12
E..(..@.@.......4.L..k....".....rv.....d
19:49:24.332470 IP 52.169.76.203.1700 > 192.168.1.30.36715: UDP, length 4
E.. ..@./.^.4.L........k........................+.
19:49:24.770029 IP 192.168.1.30.42867 > 52.169.76.203.1700: UDP, length 238
E..
..@.@.......4.L..s........T.rv.....d{"rxpk":[{"tmst":1292857668,"time":"2019-12-09T19:49:24Z","chan":3,"rfch":0,"freq":867.100000,"stat":1,"modu":"LORA","datr":"SF12BW125","codr":"4/5","lsnr":10.5,"rssi":nan,"size":23,"data":"QJZTnQ+ALQII6v5Xu0XEVRW5Vlnsra0="}]}
19:49:24.876019 IP 192.168.1.30.42867 > 52.169.76.203.1700: UDP, length 122
E.....@.@..R....4.L..s........5.rv.....d{"stat":{"time":"2019-12-09 19:49:24 GMT","rxnb":1,"rxok":1,"rxfw":1,"ackr":50.0,"dwnb":0,"txnb":0,"ping":42}}
19:49:24.917155 IP 52.169.76.203.1700 > 192.168.1.30.42867: UDP, length 4
E.. ..@.0.]v4.L........s......5...............B`..
8

[root@Wirnet_08060264 ~]# tail -f /mnt/fsuser-1/spf/var/log/spf.log

[code]
Dec 9 20:02:54 Wirnet local1.notice spf: # BEACON queued: 0
Dec 9 20:02:54 Wirnet local1.notice spf: # BEACON sent so far: 0
Dec 9 20:02:54 Wirnet local1.notice spf: # BEACON rejected: 0
Dec 9 20:02:54 Wirnet local1.notice spf: ### [JIT] ###
Dec 9 20:02:54 Wirnet local1.notice spf: /home/drd/jenkins/workspace/spf_release/lora_pkt_fwd/src/jitqueue.c:448:jit_print_queue(): INFO: [jit] queue is empty
Dec 9 20:02:54 Wirnet local1.notice spf: ### [GPS] ###
Dec 9 20:02:54 Wirnet local1.notice spf: # Invalid time reference (age: 1575921774 sec)
Dec 9 20:02:54 Wirnet local1.notice spf: # no valid GPS coordinates available yet
Dec 9 20:02:54 Wirnet local1.notice spf: ##### END #####
Dec 9 20:02:54 Wirnet local1.notice spf: JSON up: {“stat”:{“time”:“2019-12-09 20:02:54 GMT”,“rxnb”:2,“rxok”:2,“rxfw”:2,“ackr”:0.0,“dwnb”:0,“txnb”:0,“ping”:43}}
Dec 9 20:03:04 Wirnet local1.notice spf: INFO: [down] PULL_ACK received in 43.24 ms
Dec 9 20:03:14 Wirnet local1.notice spf: INFO: [down] PULL_ACK received in 41.08 ms
Dec 9 20:03:24 Wirnet local1.notice spf: INFO: [down] PULL_ACK received in 40.79 ms
Dec 9 20:03:24 Wirnet local1.notice spf: ##### 2019-12-09 20:03:24 GMT #####
Dec 9 20:03:24 Wirnet local1.notice spf: ### [UPSTREAM] ###
Dec 9 20:03:24 Wirnet local1.notice spf: # RF packets received by concentrator: 0
Dec 9 20:03:24 Wirnet local1.notice spf: # CRC_OK: 0.00%, CRC_FAIL: 0.00%, NO_CRC: 0.00%
Dec 9 20:03:24 Wirnet local1.notice spf: # RF packets forwarded: 0 (0 bytes)
Dec 9 20:03:24 Wirnet local1.notice spf: # PUSH_DATA datagrams sent: 1 (121 bytes)
Dec 9 20:03:24 Wirnet local1.notice spf: # PUSH_DATA acknowledged: 0.00%
Dec 9 20:03:24 Wirnet local1.notice spf: ### [DOWNSTREAM] ###
Dec 9 20:03:24 Wirnet local1.notice spf: # PULL_DATA sent: 3 (100.00% acknowledged, ping 40.79 ms)
Dec 9 20:03:24 Wirnet local1.notice spf: # PULL_RESP(onse) datagrams received: 0 (0 bytes)
Dec 9 20:03:24 Wirnet local1.notice spf: # RF packets sent to concentrator: 0 (0 bytes)
Dec 9 20:03:24 Wirnet local1.notice spf: # TX errors: 0
Dec 9 20:03:24 Wirnet local1.notice spf: # BEACON queued: 0
Dec 9 20:03:24 Wirnet local1.notice spf: # BEACON sent so far: 0
Dec 9 20:03:24 Wirnet local1.notice spf: # BEACON rejected: 0
Dec 9 20:03:24 Wirnet local1.notice spf: ### [JIT] ###

9

Well, you are still reporting the same

“rssi”:nan

So its unlikely that anything would have changed

Nobody has an idea to debug this ?

If it wasn’t clear the first time this erroneous value was highlighted, I suggest you take this up with Kerlink and try to correct that issue at the source, or else find confirmation that despite seeming odd it is appropriate behavior.

Perhaps you can try a different version of the gateway firmware.

Perhaps there’s an antenna compensation table that has a bad or missing entry.

Perhaps there is a different packet forwarder you can run on this gateway.

1 Like
10

Please learn how to format your forum posts. Dumping large amounts of log or trace into a message makes for difficult reading. (Which generally means I will just ignore the question)

Also, please read the replies you got, @cslorabox identified the probable cause already.

11

as far as i see my gateway is connected on the console !
how can we explain the gw is connected and we can’t see anything in the traffic window . at least i expect to see error or the frame which are received ?

12

You gateway is sending what appear to be broken messages to the network.

The RSSI field in an uplink needs to be a valid numeric value, instead it is “nan” which indicates a floating point error.

You need to figure out why that is happening and fix it. Again, that’s either an error you need to raise with Kerlink, or see if you have better luck with another gateway firmware version.

Here for example someone quotes a configuration file having “nan” as an entry for “rssi_offset” - it’s not clear if their problem is the same as yours but presumably the old computer saying “garbage in, garbage out” could also apply to “nan in, nan out”

13

i just follow the following link
https://www.thethingsnetwork.org/docs/gateways/kerlink/config.html

14

Please read the linked post from the other forum and then report back what the values of rssi_offset are in your your gateway’s various configuration files.

I don’t have a Kerlink gateway, but while the values in my gateway’s configurations may or may not be accurate, they are at least numbers. I don’t really feel like putting in “nan” as a value just to see if I can break them, but I strongly suspect I could.

15

[root@Wirnet_08060264 etc]# cat local_conf.json
{
“SX1301_conf”: {
“radio_0”: { “rssi_offset”: -nan },
“radio_1”: { “rssi_offset”: -nan },
“tx_lut_0”: {“dig_gain”: 3, “pa_gain”: 3, “mix_gain”: 15, “rf_power”: -1 ,
“tx_lut_1”: {“dig_gain”: 3, “pa_gain”: 3, “mix_gain”: 15, “rf_power”: -1 ,
“tx_lut_2”: {“dig_gain”: 3, “pa_gain”: 3, “mix_gain”: 15, “rf_power”: -1 ,
“tx_lut_3”: {“dig_gain”: 3, “pa_gain”: 3, “mix_gain”: 15, “rf_power”: -1 ,
“tx_lut_4”: {“dig_gain”: 3, “pa_gain”: 3, “mix_gain”: 15, “rf_power”: -1 ,
“tx_lut_5”: {“dig_gain”: 3, “pa_gain”: 3, “mix_gain”: 15, “rf_power”: -1 ,
“tx_lut_6”: {“dig_gain”: 3, “pa_gain”: 3, “mix_gain”: 15, “rf_power”: -1 ,
“tx_lut_7”: {“dig_gain”: 3, “pa_gain”: 3, “mix_gain”: 15, “rf_power”: -1 ,
“tx_lut_8”: {“dig_gain”: 3, “pa_gain”: 3, “mix_gain”: 15, “rf_power”: -1 ,
“tx_lut_9”: {“dig_gain”: 3, “pa_gain”: 3, “mix_gain”: 15, “rf_power”: -1 ,
“tx_lut_10”: {“dig_gain”: 3, “pa_gain”: 3, “mix_gain”: 15, “rf_power”: -1 },
“tx_lut_11”: {“dig_gain”: 3, “pa_gain”: 3, “mix_gain”: 15, “rf_power”: -1 },
“tx_lut_12”: {“dig_gain”: 3, “pa_gain”: 3, “mix_gain”: 15, “rf_power”: -1 },
“tx_lut_13”: {“dig_gain”: 3, “pa_gain”: 3, “mix_gain”: 15, “rf_power”: -1 },
“tx_lut_14”: {“dig_gain”: 3, “pa_gain”: 3, “mix_gain”: 15, “rf_power”: -1 },
“tx_lut_15”: {“dig_gain”: 3, “pa_gain”: 3, “mix_gain”: 15, “rf_power”: -1 }
},

    "gateway_conf": {
            "gateway_ID": "7276FF0008060264"
    }

}[root@Wirnet_08060264 etc]#

[root@Wirnet_08060264 etc]# cat global_conf.json
{
“SX1301_conf”: {
“lorawan_public”: true,
“antenna_gain”: 0,
“clksrc”: 1,
“radio_0”: {
“enable”: true,
“type”: “SX1257”,
“freq”: 867500000,
“tx_enable”: true,
“tx_notch_freq”: 129000,
“tx_freq_min”: 863000000,
“tx_freq_max”: 870000000
},
“radio_1”: {
“enable”: true,
“type”: “SX1257”,
“freq”: 868500000,
“tx_enable”: false
},
“chan_multiSF_0”: { “enable”: true, “radio”: 1, “if”: -400000 },
“chan_multiSF_1”: { “enable”: true, “radio”: 1, “if”: -200000 },
“chan_multiSF_2”: { “enable”: true, “radio”: 1, “if”: 0 },
“chan_multiSF_3”: { “enable”: true, “radio”: 0, “if”: -400000 },
“chan_multiSF_4”: { “enable”: true, “radio”: 0, “if”: -200000 },
“chan_multiSF_5”: { “enable”: true, “radio”: 0, “if”: 0 },
“chan_multiSF_6”: { “enable”: true, “radio”: 0, “if”: 200000 },
“chan_multiSF_7”: { “enable”: true, “radio”: 0, “if”: 400000 },
“chan_Lora_std”: {
“enable”: true,
“radio”: 1,
“if”: -200000,
“bandwidth”: 250000,
“spread_factor”: 7
},
“chan_FSK”: {
“enable”: true,
“radio”: 1,
“if”: 300000,
“bandwidth”: 125000,
“datarate”: 50000
},
“tx_lut_0”: {“dig_gain”: 0, “pa_gain”: 0, “mix_gain”: 8, “rf_power”: 0}
},
“gateway_conf”: {
“server_address”: “router.eu.thethings.network”,
“serv_port_up”: 1700,
“serv_port_down”: 1700,
“keepalive_interval”: 10,
“stat_interval”: 30,
“push_timeout_ms”: 100,
“forward_crc_valid”: true,
“forward_crc_error”: false,
“forward_crc_disabled”: false,
“autoquit_threshold”: 3,
“gps_tty_path”: “/dev/nmea”
}
}
[root@Wirnet_08060264 etc]#
[root@Wirnet_08060264 fsuser-1]# cat loraboard_conf.json
{
“SX1301_conf”: {
“radio_0”: { “rssi_offset”: -nan },
“radio_1”: { “rssi_offset”: -nan },
“tx_lut_0”: {“dig_gain”: 3, “pa_gain”: 3, “mix_gain”: 15, “rf_power”: -1 },
“tx_lut_1”: {“dig_gain”: 3, “pa_gain”: 3, “mix_gain”: 15, “rf_power”: -1 },
“tx_lut_2”: {“dig_gain”: 3, “pa_gain”: 3, “mix_gain”: 15, “rf_power”: -1 },
“tx_lut_3”: {“dig_gain”: 3, “pa_gain”: 3, “mix_gain”: 15, “rf_power”: -1 },
“tx_lut_4”: {“dig_gain”: 3, “pa_gain”: 3, “mix_gain”: 15, “rf_power”: -1 },
“tx_lut_5”: {“dig_gain”: 3, “pa_gain”: 3, “mix_gain”: 15, “rf_power”: -1 },
“tx_lut_6”: {“dig_gain”: 3, “pa_gain”: 3, “mix_gain”: 15, “rf_power”: -1 },
“tx_lut_7”: {“dig_gain”: 3, “pa_gain”: 3, “mix_gain”: 15, “rf_power”: -1 },
“tx_lut_8”: {“dig_gain”: 3, “pa_gain”: 3, “mix_gain”: 15, “rf_power”: -1 },
“tx_lut_9”: {“dig_gain”: 3, “pa_gain”: 3, “mix_gain”: 15, “rf_power”: -1 },
“tx_lut_10”: {“dig_gain”: 3, “pa_gain”: 3, “mix_gain”: 15, “rf_power”: -1 },
“tx_lut_11”: {“dig_gain”: 3, “pa_gain”: 3, “mix_gain”: 15, “rf_power”: -1 },
“tx_lut_12”: {“dig_gain”: 3, “pa_gain”: 3, “mix_gain”: 15, “rf_power”: -1 },
“tx_lut_13”: {“dig_gain”: 3, “pa_gain”: 3, “mix_gain”: 15, “rf_power”: -1 },
“tx_lut_14”: {“dig_gain”: 3, “pa_gain”: 3, “mix_gain”: 15, “rf_power”: -1 },
“tx_lut_15”: {“dig_gain”: 3, “pa_gain”: 3, “mix_gain”: 15, “rf_power”: -1 }
},

    "gateway_conf": {
            "gateway_ID": "7276FF0008060264"
    }

}[root@Wirnet_08060264 fsuser-1]#

16

Now we are getting somewhere!

Try replacing those “-nan” with legal, if perhaps not very correct values.

For example

seems to have

“rssi_offset”: -166.0,

Which is worth seeing if it gets you working when filled into the field of your files that have a field by that name.

Long term it would be getter to get a recommended value for file from Kerlink.