[Ferenc Unghváry]

Last Friday there was a powerbreak for a short time.
On Monday I could not login to the conduit. The conduit responses for ping but it does not response for SSH.

The conduit is built on the roof of the building.
It gets power via PoE. I unplugged the Ethernet cable and reconnected after a while. But it did not help.

What can we do?
How can we do a factory reset?

[Ferenc Unghváry]

Do I have to upgrade mLinux, lora-network-server and lora-packet-forwarder on both multiConnect Conduit devices?

[Ferenc Unghváry]

The log level was already set to 100.
Here a longer log:

13:4:5:474|TRACE| GW:00:80:00:00:00:00:c1:ca|SEEN|PULL-DATA|192.168.63.103:46804
13:4:5:607|TRACE| GW:00:80:00:00:00:00:c1:ca|SEEN|PUSH-DATA|192.168.63.103:34877
13:4:5:608|INFO| GW:00:80:00:00:00:00:c1:ca|FRAME-RX|Parsing 1 packets
13:4:5:609|DEBUG| GW:00:80:00:00:00:00:c1:ca|FRAME-RX|DATA: 400500000000bff00333ed531db33dd5a2525762607404181c206432bf520201b41a0341d8980326d8b2
13:4:5:609|DEBUG| GW:00:80:00:00:00:00:c1:ca|FRAME-RX|FREQ: 868.500000 MHz DR5 RSSI: -46 dB SNR: 70 cB
13:4:5:610|DEBUG| GW:00:80:00:00:00:00:c1:ca|FRAME-RX|TYPE: Unconfirmed Up
13:4:5:610|DEBUG| GW:00:80:00:00:00:00:c1:ca|PACKET-RX|ADDR: 00:00:00:05 FCnt:f0bf
13:4:5:611|INFO| ED:00-01-02-03-04-05-06-0b|CHECK-PKT|FCNT: 0002f0bf LAST-FCNT: 0002f0be Duplicate: no
13:4:5:612|INFO| ED:00-01-02-03-04-05-06-0b|CHECK-MIC|ADDR: 00:00:00:05 passed
13:4:5:612|INFO| ED:00-01-02-03-04-05-06-0b|PER|0.247831%
13:4:5:613|DEBUG| ED:00-01-02-03-04-05-06-0b|PACKET-RX|GW:00:80:00:00:00:00:c1:ca Time_us:1058586931
13:4:5:613|DEBUG| ED:00-01-02-03-04-05-06-0b|PACKET-RX|Downlink Packets Queued: 0
13:4:5:613|INFO| ED:00-01-02-03-04-05-06-0b|FCTRL|ADR:0 ADRACK:0 ACK:0 CLASS:A OPTS:0
13:4:5:625|TRACE| Schedule DC band: 1 available: 36000 duration: 56 freq: 868500000
13:4:5:625|INFO| ED:00-01-02-03-04-05-06-0b|SCHED-TX|Use RX1 TOA:56 ms
13:4:5:626|DEBUG| GW:00:80:00:00:00:00:c1:ca|FRAME-RX|JSON: {"chan":2,"codr":"4/5","data":"QAUAAAAAv/ADM+1THbM91aJSV2JgdAQYHCBkMr9SAgG0GgNB2JgDJtiy","datr":"SF7BW125","freq":868.5,"lsnr":7,"modu":"LORA","rfch":1,"rssi":-46,"size":42,"stat":1,"time":"2018-04-13T13:03:50.608672Z","tmst":1058586931}
13:4:5:633|TRACE| GW:00:80:00:00:00:00:c1:ca|SEEN|PUSH-DATA|127.0.0.1:41926
13:4:5:635|INFO| GW:00:80:00:00:00:00:c1:ca|FRAME-RX|Parsing 1 packets
13:4:5:636|DEBUG| GW:00:80:00:00:00:00:c1:ca|FRAME-RX|DATA: 400500000000bff00333ed531db33dd5a2525762607404181c206432bf520201b41a0341d8980326d8b2
13:4:5:636|DEBUG| GW:00:80:00:00:00:00:c1:ca|FRAME-RX|FREQ: 868.500000 MHz DR5 RSSI: -83 dB SNR: 72 cB
13:4:5:636|DEBUG| GW:00:80:00:00:00:00:c1:ca|FRAME-RX|TYPE: Unconfirmed Up
13:4:5:637|DEBUG| GW:00:80:00:00:00:00:c1:ca|PACKET-RX|ADDR: 00:00:00:05 FCnt:f0bf
13:4:5:638|TRACE| Test authentication of duplicate frame
13:4:5:639|INFO| ED:00-01-02-03-04-05-06-0b|CHECK-PKT|FCNT: beea6094 LAST-FCNT: 0002f0bf Duplicate: yes
13:4:5:639|INFO| ED:00-01-02-03-04-05-06-0b|CHECK-MIC|ADDR: 00:00:00:05 passed
13:4:5:640|INFO| ED:00-01-02-03-04-05-06-0b|PER|0.247525%
13:4:5:640|DEBUG| ED:00-01-02-03-04-05-06-0b|PACKET-RX|GW:00:80:00:00:00:00:c1:ca Time_us:3671254707
13:4:5:640|DEBUG| ED:00-01-02-03-04-05-06-0b|PACKET-RX|Downlink Packets Queued: 0
13:4:5:641|INFO| ED:00-01-02-03-04-05-06-0b|FCTRL|ADR:0 ADRACK:0 ACK:0 CLASS:A OPTS:0
13:4:5:643|DEBUG| GW:00:80:00:00:00:00:c1:ca|FRAME-RX|JSON: {"chan":2,"codr":"4/5","data":"QAUAAAAAv/ADM+1THbM91aJSV2JgdAQYHCBkMr9SAgG0GgNB2JgDJtiy","datr":"SF7BW125","freq":868.5,"lsnr":7.2000000000000002,"modu":"LORA","rfch":0,"rssi":-83,"size":42,"stat":1,"time":"2018-04-13T13:04:05.632249Z","tmst":3671254707}
13:4:6:379|INFO| ED:00-01-02-03-04-05-06-0b|FRAME-TX|Nothing to transmit
13:4:15:234|TRACE| GW:00:80:00:00:00:00:c1:ca|SEEN|PULL-DATA|127.0.0.1:45199
13:4:15:674|TRACE| GW:00:80:00:00:00:00:c1:ca|SEEN|PULL-DATA|192.168.63.103:46804
13:4:19:865|TRACE| GW:00:80:00:00:00:00:c1:ca|SEEN|PUSH-DATA|127.0.0.1:41926
13:4:19:866|INFO| GW:00:80:00:00:00:00:c1:ca|FRAME-RX|Parsing 1 packets
terminate called after throwing an instance of 'std::out_of_range'
  what():  basic_string::substr
Logger Level Changed to 100
9:39:41:806|INFO|Setting join delay according to public/private setting
9:39:41:807|INFO|Setting join 5 seconds

[Ferenc Unghváry]

mLinux 3.2.0 \n \l
MTS Network Server – Version 1.0.43

How can I increase the logging level?

[Ferenc Unghváry]

I disabled LoRa packet forwarder in file /etc/default/lora-packet-forwarder.
I also removed global_conf.json and local_conf.json files.
Then I tried to start lora_pkt_fwd from /var/run/1 directory but it failed because it is a symbolic link to /opt/lora/basic_pkt_fwd-usb but this file is missing. There is a packet forwarder executable file named lora_pkt_fwd in directory /opt/lora.
I started it from folder /var/run/lora/1 but it failed to connect board.

Output of lora_pkt_fwd:

ERROR: FAIL TO CONNECT BOARD
ERROR: [main] failed to start the concentrator


I guessed wrong version of packet forwarder is installed. I downloaded the latest version of packet forwarder from your website: Lora Packet Forwarder USB 1.4.1-r11
I tried to install it but I got the following error message:


opkg install lora-packet-forwarder-usb_1.4.1-r11.0_arm926ejste.ipk
Installing lora-packet-forwarder-usb (1.4.1-r11.0) to root...
Collected errors:
* satisfy_dependencies_for: Cannot satisfy the following dependencies for lora-packet-forwarder-usb:
* libmpsse (>= 1.3) *
* opkg_install_cmd: Cannot install package lora-packet-forwarder-usb.


The installed version of mLinux is 3.2.0.

How can I check which version of packet forwarder (SPI or USB) should be installed?

Regards,

Ferenc

[Ferenc Unghváry]

We are using mLinux: Linux mtcdt 3.12.27
Originally we had only one MT MC Conduit LoRa GW. We used the factory settings.
It worked properly.
We bought another LoRa GW, any my collague set it as a packet forwarder (Lora AP).
I am not sure whether both Lora GW were able to receive the LoRa packages.
I hope yes.
He had to update the network server and packet forwarder software.

I think the packet forwarder has not run on the LoRa Gateway only on LoRa AP.
When he did it he got the information from the forum the lora_pkt_fwd should not run if lora-network-server runs.

Now I checked the running processes. Only lora-network-server runs.
The property ENABLED was set to no in /etc/default/lora-packet-forwarder file.
I set it to true but the packet forwarder cannot start:


INFO: found local configuration file local_conf.json, parsing it
INFO: redefined parameters will overwrite global parameters
INFO: local_conf.json does not contain a JSON object named SX1301_conf
INFO: local_conf.json does contain a JSON object named gateway_conf, parsing gateway parameters
INFO: server hostname or IP address is configured to "localhost"
INFO: upstream port is configured to "1680"
INFO: downstream port is configured to "1680"
INFO: packets received with a valid CRC will be forwarded
INFO: packets received with a CRC error will NOT be forwarded
INFO: packets received with no CRC will NOT be forwarded
ERROR: FAIL TO CONNECT BOARD
ERROR: [main] failed to start the concentrator


What shall I do to make it workable?

[Author]

Posts