Received ‘dnmsg’ before ‘router_config’ - dropped

ChirpStack Gateway Bridge
1

Hi,
I cannot connect end devices to Chirpstack server using Basic Station. I see in log file of Basic station “Received ‘dnmsg’ before ‘router_config’ - dropped”, see below:

2024-08-05 16:19:45.119 [S2E:VERB] RX 869.1MHz DR0 SF12/BW125 snr=10.2 rssi=-38 xtime=0x8A000004D16D03 - jreq MHdr=00 JoinEui=7665:6761:7464:3131 DevEui=70b3:d50a:d000:9299 DevNonce=15996 MIC=-1504505488
2024-08-05 16:19:45.391 [S2E:WARN] Received ‘dnmsg’ before ‘router_config’ - dropped
2024-08-05 16:19:57.400 [SYN:VERB] Time sync rejected: quality=355 threshold=233
2024-08-05 16:20:01.600 [SYN:VERB] Time sync rejected: quality=284 threshold=233
2024-08-05 16:20:03.701 [SYN:VERB] Time sync rejected: quality=319 threshold=233
2024-08-05 16:20:07.400 [SYN:INFO] MCU/SX130X drift stats: min: +0.0ppm q50: +5.0ppm q80: +10.6ppm max: -11.7ppm - threshold q90: +11.6ppm
2024-08-05 16:20:07.400 [SYN:INFO] Mean MCU drift vs SX130X#0: 3.8ppm
2024-08-05 16:20:10.600 [SYN:INFO] PPS/SX130X drift stats: min: +0.0ppm q50: +0.0ppm q80: +0.0ppm max: -0.3ppm - threshold q80: +0.0ppm
2024-08-05 16:20:40.600 [SYN:VERB] Time sync rejected: quality=276 threshold=233
2024-08-05 16:20:42.701 [SYN:VERB] Time sync rejected: quality=374 threshold=233
2024-08-05 16:20:44.802 [SYN:VERB] Time sync rejected: quality=847 threshold=233
2024-08-05 16:20:46.903 [SYN:INFO] Time sync qualities: min=149 q90=355 max=847 (previous q90=233)
2024-08-05 16:20:54.989 [S2E:VERB] RX 868.9MHz DR0 SF12/BW125 snr=12.5 rssi=-41 xtime=0x8A000008FB80F2 - jreq MHdr=00 JoinEui=a840:4100:0:101 DevEui=a840:4158:e189:3882 DevNonce=38262 MIC=1907188019
2024-08-05 16:20:55.250 [S2E:WARN] Received ‘dnmsg’ before ‘router_config’ - dropped

Where need I look for the reason: in Basic Station or in Chirpstack server?

Can anyone give me the working example of the station.conf and chirpstack-gateway-bridge.toml as example for SX1302 HAT on Raspberry Pi?
Thank you!

2

Thia is due to region not being set as AS923 was not recognized. This was solved in another thread though.

Are you still seeing issues?

3

Yes, you are right. The reason is my region RU864 is not presented in source code of Semtech Basic Station. I have added that region as it was written in this comment: Received 'dnmsg' before 'router_config' - dropped · Issue #200 · lorabasics/basicstation · GitHub
But now I can work with TTN, but cannot with Chirpstack: it doesn’t send settings to Basic Station. Now I am looking for the reason.
Here is the log:
root@raspberrypi:~/basicstation/examples/corecell# ./start-station.sh -l ./lns-ttn
Using variant=debug, lns_config=‘./lns-ttn’
Starting Station …
2024-08-19 13:23:18.280 [SYS:INFO] Logging : stderr (maxsize=10000000, rotate=3)
2024-08-19 13:23:18.280 [SYS:INFO] Station Ver : 2.0.6(corecell/debug) 2024-08-19 06:26:59
2024-08-19 13:23:18.281 [SYS:INFO] Package Ver : 2.0.4
2024-08-19 13:23:18.281 [SYS:INFO] mbedTLS Ver : 2.28.0
2024-08-19 13:23:18.281 [SYS:INFO] proto EUI : b827:ebff:fef4:16d7 (station.conf)
2024-08-19 13:23:18.281 [SYS:INFO] prefix EUI : ::1 (builtin)
2024-08-19 13:23:18.281 [SYS:INFO] Station EUI : b827:ebff:fef4:16d7
2024-08-19 13:23:18.281 [SYS:INFO] Station home: ./lns-ttn/ (–home)
2024-08-19 13:23:18.281 [SYS:INFO] Station temp: /var/tmp/ (builtin)
2024-08-19 13:23:18.281 [SYS:WARN] Station in NO-CUPS mode
2024-08-19 13:23:18.482 [TCE:INFO] Starting TC engine
2024-08-19 13:23:18.482 [TCE:INFO] Connecting to INFOS: ws://192.168.0.79:3001
2024-08-19 13:23:18.483 [AIO:XDEB] [3] ws_connecting state=1
2024-08-19 13:23:18.484 [AIO:XDEB] [3] ws_connecting state=2
2024-08-19 13:23:18.484 [AIO:XDEB] [3] socket write bytes=167
2024-08-19 13:23:18.485 [AIO:XDEB] [3] ws_connecting state=3
2024-08-19 13:23:18.485 [AIO:XDEB] [3] socket read bytes=129
2024-08-19 13:23:18.485 [AIO:XDEB] [3|WS] > {“router”:“b827:ebff:fef4:16d7”}
2024-08-19 13:23:18.485 [AIO:XDEB] [3] socket write bytes=38
2024-08-19 13:23:18.486 [AIO:XDEB] [3] socket read bytes=119
2024-08-19 13:23:18.486 [AIO:XDEB] [3|WS] < {“router”:“b827:ebff:fef4:16d7”,“muxs”:“b827:ebff:fef4:16d7”,“uri”:“ws://192.168.0.79:3001/gateway/b827ebfffef416d7”}
2024-08-19 13:23:18.486 [TCE:INFO] Infos: b827:ebff:fef4:16d7 b827:ebff:fef4:16d7 ws://192.168.0.79:3001/gateway/b827ebfffef416d7
2024-08-19 13:23:18.486 [AIO:DEBU] [3] ws_close reason=1000
2024-08-19 13:23:18.486 [AIO:XDEB] [3] ws_closing_w state=5
2024-08-19 13:23:18.486 [AIO:DEBU] Echoing close - reason=1000
2024-08-19 13:23:18.486 [AIO:XDEB] [3] socket write bytes=8
2024-08-19 13:23:18.487 [AIO:DEBU] [3] Connection closed unexpectedly
2024-08-19 13:23:18.487 [AIO:DEBU] [3] WS connection shutdown…
2024-08-19 13:23:18.487 [TCE:VERB] Connecting to MUXS…
2024-08-19 13:23:18.488 [AIO:XDEB] [3] ws_connecting state=1
2024-08-19 13:23:18.488 [AIO:XDEB] [3] ws_connecting state=2
2024-08-19 13:23:18.488 [AIO:XDEB] [3] socket write bytes=180
2024-08-19 13:23:18.491 [AIO:XDEB] [3] ws_connecting state=3
2024-08-19 13:23:18.491 [AIO:XDEB] [3] socket read bytes=129
2024-08-19 13:23:18.491 [TCE:VERB] Connected to MUXS.
2024-08-19 13:23:18.491 [AIO:XDEB] [3|WS] > {“msgtype”:“version”,“station”:“2.0.6(corecell/debug)”,“firmware”:“2.0.4”,“package”:“2.0.4”,“model”:“corecell”,“protocol”:2,“features”:“rmtsh”}
2024-08-19 13:23:18.491 [AIO:XDEB] [3] socket write bytes=151
2024-08-19 13:24:18.493 [AIO:XDEB] [3] socket read bytes=2
2024-08-19 13:24:18.493 [AIO:XDEB] [3|WS] < PING ()
2024-08-19 13:24:18.493 [AIO:XDEB] [3|WS] > PONG
2024-08-19 13:24:18.493 [AIO:XDEB] [3] socket write bytes=6
2024-08-19 13:25:18.495 [AIO:XDEB] [3] socket read bytes=2
2024-08-19 13:25:18.495 [AIO:XDEB] [3|WS] < PING ()
2024-08-19 13:25:18.495 [AIO:XDEB] [3|WS] > PONG
2024-08-19 13:25:18.495 [AIO:XDEB] [3] socket write bytes=6
2024-08-19 13:26:18.496 [AIO:XDEB] [3] socket read bytes=2
2024-08-19 13:26:18.496 [AIO:XDEB] [3|WS] < PING ()
2024-08-19 13:26:18.496 [AIO:XDEB] [3|WS] > PONG

4

We found that the issue was an incorrect frequency in the ChirpStack Gateway Bridge. The ChirpStack Gateway Bridge was logging an error when generating the router_config response.