single channel gateway on US 902.3 MHz frequency using SF7 about lorawan-server HOT 12 CLOSED

Hi. Are you able to see the log file written by the lorawan-server? The best way to start is to check the log for errors and warnings. The gateway and/or device registration may be wrong. If there is no error nor warning, the connectivity between your gateway and the server is the issue.

from lorawan-server.

I've not found any logs but an empty crash.log file. Starting lorawan-server on the commandline provides lots of debug output on that console and nothing indicates errors. How might I enable logging?

INTERESTING: I realized I was looking at the admin screen from the machine running docker and the docker IP address is local( 172.x.x.x ) and is not accessable from outside the computer. I'm working on routing to my LAN so external devices( browser, gateway, etc ) can communicate with it.

Looking at my gateway console output it looks like the UDP connection to the server is ok:
Connecting to UDP port 1680
Connection successful

These are the active settings in the gateway(ESP-sc-gway.h) which I believe are important and were changed to point to the local lorawan-server:
#define _LOCUDPPORT 1680 // Often 1700 or 1701 is used for upstream comms
// MQTT definitions
#define _TTNPORT 1680
//#define _TTNSERVER "router.us.thethings.network"
#define _TTNSERVER "172.17.0.2"

And because I see and use the admin screens on 172.17.0.2:8080/admin I know it's accessable... I disabled the firewall( ufw ) also.
I was hoping to see some debug when the gateway connects to the lorawan-server but I see nothing.

from lorawan-server.

correct, nothing shows up in the console/startup log but startup messages. I'm sure now that I have a routing issue with IP traffic since the lorawan-server is running in a docker container. I will fix that and see what happens after that. But it will be a few hours before I can get back on this. I will post updates tonight. Thanks.

from lorawan-server.

Thanks. I just made a little update (commit 5ae2ce7), so you can see a log message when a gateway successfully connects to the lorawan-server. It's a useful information and it may help you debugging your connectivity issue.

from lorawan-server.

It was my LAN routing issue. I used socat to redirect TCP/IP 8080 and TCP/UDP 1680 and saw this on the lorawan-server log:

21:38:03.807 [warning] Unknown DevAddr 26011668
21:38:03.807 [error] ERROR: {unknown_devaddr,<<38,1,22,104>>}

Now to figure out how to define ADB devices. Thanks.

from lorawan-server.

To add this device, just add a new "Link", copy-paste the DevAddr "26011668" and enter the keys.

from lorawan-server.

Fantastic, seeing data now:

21:49:30.965 [error] ERROR: bad_mic
21:49:55.054 [debug] LinkADRReq {1,5,1}
21:49:55.054 [error] ERROR: {unexpected_data,{rxdata,1,<<3,3,3,28,220,148,65,139,114,203,66>>,false,true}}

It's a LMIC based ProMini node so I will probably have to figure out how to create a application filter. Using the default Semtech handler so probably why the error.

from lorawan-server.

The unexpected_data error is because you use some other (not yet supported) application. Some description of how to build the app handlers is here.

I am more worried about the bad_mic error. It shouldn't happen if everything is well configured and it's not related to app handlers.

from lorawan-server.

Hello, does the problem persist?

from lorawan-server.

Support for US 902.3 MHz was introduced in the release 0.3.0.

from lorawan-server.

I've not had time to get back to this. I build this into a bootable LiveCD for workshops I've been doing but out of 10 people nobody has shown interest in the Docker side so I've just got been back there. Soon though as I will be helping a school do some long range balloon tests and we'll be running local servers with a gateway in the chase vehicles. I'll open any issues I run into.

from lorawan-server.

OK. If the problem persists, feel free to raise a new issue.

from lorawan-server.