Packet forwarder not seen
Home › Forums › Lora Network Server › Packet forwarder not seen
- This topic has 9 replies, 3 voices, and was last updated 5 years, 8 months ago by
a.dolera1bc@gmail.com.
-
AuthorPosts
-
January 16, 2018 at 4:23 am #22344
Ferenc Unghváry
ParticipantHello,
we have 2 MultiConnect Conduit devices with LoRa chip.
One of them is used as a LoRa Network Server and the other is used as a LoRa Access Point.
The packer forwarder runs on LoRa AP.
The LoRa-network-server runs on LoRa GW.
Because of network problen the LoRa AP is stopped.
Since then the LoRa GW cannot receive any packages from LoRa devices, the the following error message appears in every 30 seconds in the log file:Packet forwarder not seen in … s
Why the LoRa gateway cannot receive any packages from LoRa devices?
Do I have to start packet forwarder with the network server?
How can I configure the network server not to use other LoRa AP?Best regards,
Ferenc
January 16, 2018 at 7:26 am #22345Jason Reiss
KeymasterAre you using mLinux or AEP? What version?
Is this a setup you had working at one point and now it is not working?Can you elaborate on the network problem causing the LoRa AP to stop?
The network server requires a packet forwarder to send packets from the radio hardware. A packet forwarder process should be started by the network server init script.
Can you check the packet forwarder process on the LoRa GW?
# ps -A | grep lora
Or try to start manually to see if there are error?
# cd /var/run/lora/1 # ./lora_pkt_fwd
For the network server to receive from the remote gateway the firewall must be opened and the network server configured to listen on the public ethernet interface. The “udp” > “allowPublic” setting must be set true.
January 16, 2018 at 8:32 am #22347Ferenc Unghváry
ParticipantWe 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?
January 16, 2018 at 8:42 am #22348Jason Reiss
KeymasterThis init script is used only if the Conduit is to be configured for packet forwarder only mode. On a network server Conduit is should be disabled.
/etc/default/lora-packet-forwarderOn the Network Server Conduit:
Remove any global_conf.json and local_conf.json files.
The network server will create a global_conf.json file for the packet forwarder.Is the packet forwarder output from the Network Server Conduit?
Did you run from /var/run/lora/1/ or from /opt/lora/ directory?mLinux 3.3.13 is our latest release version
To see your installed version check this file
# cat /etc/issuemLinux should not have a firewall enabled by default.
January 17, 2018 at 8:20 am #22356Ferenc Unghváry
ParticipantI 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
January 17, 2018 at 8:30 am #22357Jason Reiss
KeymasterI suggest upgrading to mLinux 3.3.13
# mts-io-sysfs show lora/*
MTAC-LORA-915
MTAC-LORA-1.01.0 cards should use USB packet forwarder
If conduit has internet try
# opkg update
# opkg install lora-packet-forwarder-usbJuly 6, 2019 at 12:17 pm #28147a.dolera1bc@gmail.com
ParticipantPlease, help!
For several days/nights I have been checking and making changes to the configuration of the package lora-packet-forwarder_usb without getting any progress, my problem is that I can not boot the packer-forwarder and therefore there is no communication with the gateway-bridge, I followed the configuration guidelines.Next I enclose my global_conf.json in case they detect any error that makes the output that I show later happen.
mtcdt:/var/config/lora-packet-forwarder-usb$ cat global_conf.json
{
“SX1301_conf”: {
“antenna_gain”: 0,
“chan_FSK”: {
“bandwidth”: 125000,
“datarate”: 50000,
“enable”: true,
“if”: 300000,
“radio”: 1
},
“chan_Lora_std”: {
“bandwidth”: 250000,
“enable”: true,
“if”: -200000,
“radio”: 1,
“spread_factor”: 7
},
“chan_multiSF_0”: {
“enable”: true,
“if”: -400000,
“radio”: 1
},
“chan_multiSF_1”: {
“enable”: true,
“if”: -200000,
“radio”: 1
},
“chan_multiSF_2”: {
“enable”: true,
“if”: 0,
“radio”: 1
},
“chan_multiSF_3”: {
“enable”: true,
“if”: -400000,
“radio”: 0
},
“chan_multiSF_4”: {
“enable”: true,
“if”: -200000,
“radio”: 0
},
“chan_multiSF_5”: {
“enable”: true,
“if”: 0,
“radio”: 0
},
“chan_multiSF_6”: {
“enable”: true,
“if”: 200000,
“radio”: 0
},
“chan_multiSF_7”: {
“enable”: true,
“if”: 400000,
“radio”: 0
},
“clksrc”: 0,
“lbt_cfg”: {
“enable”: false,
“rssi_target”: 160
},
“lorawan_public”: true,
“radio_0”: {
“enable”: true,
“freq”: 867500000,
“rssi_offset”: -162,
“tx_enable”: true,
“tx_freq_max”: 870000000,
“tx_freq_min”: 863000000,
“type”: “SX1257”
},
“radio_1”: {
“enable”: true,
“freq”: 868500000,
“rssi_offset”: -162,
“tx_enable”: false,
“type”: “SX1257”
},
“tx_lut_0”: {
“dig_gain”: 0,
“mix_gain”: 11,
“pa_gain”: 0,
“rf_power”: -6
},
“tx_lut_1”: {
“dig_gain”: 0,
“mix_gain”: 13,
“pa_gain”: 0,
“rf_power”: -3
},
“tx_lut_10”: {
“dig_gain”: 0,
“mix_gain”: 15,
“pa_gain”: 2,
“rf_power”: 16
},
“tx_lut_11”: {
“dig_gain”: 0,
“mix_gain”: 10,
“pa_gain”: 3,
“rf_power”: 20
},
“tx_lut_12”: {
“dig_gain”: 0,
“mix_gain”: 12,
“pa_gain”: 3,
“rf_power”: 23
},
“tx_lut_13”: {
“dig_gain”: 0,
“mix_gain”: 13,
“pa_gain”: 3,
“rf_power”: 25
},
“tx_lut_14”: {
“dig_gain”: 0,
“mix_gain”: 15,
“pa_gain”: 3,
“rf_power”: 26
},
“tx_lut_15”: {
“dig_gain”: 0,
“mix_gain”: 15,
“pa_gain”: 3,
“rf_power”: 27
},
“tx_lut_2”: {
“dig_gain”: 0,
“mix_gain”: 9,
“pa_gain”: 1,
“rf_power”: 0
},
“tx_lut_3”: {
“dig_gain”: 0,
“mix_gain”: 10,
“pa_gain”: 1,
“rf_power”: 3
},
“tx_lut_4”: {
“dig_gain”: 0,
“mix_gain”: 12,
“pa_gain”: 1,
“rf_power”: 6
},
“tx_lut_5”: {
“dig_gain”: 0,
“mix_gain”: 10,
“pa_gain”: 2,
“rf_power”: 10
},
“tx_lut_6”: {
“dig_gain”: 0,
“mix_gain”: 11,
“pa_gain”: 2,
“rf_power”: 11
},
“tx_lut_7”: {
“dig_gain”: 0,
“mix_gain”: 11,
“pa_gain”: 2,
“rf_power”: 12
},
“tx_lut_8”: {
“dig_gain”: 2,
“mix_gain”: 12,
“pa_gain”: 2,
“rf_power”: 13
},
“tx_lut_9”: {
“dig_gain”: 0,
“mix_gain”: 13,
“pa_gain”: 2,
“rf_power”: 14
}
},
“gateway_conf”: {
“gateway_ID”: “00800000A0003972”,
“server_address”: “localhost”,
“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,
“link_mote”: “00CC01AF”,
“beacon_conf”:{
“period”: 128,
“freq_hz”: 869525000,
“datarate”: 9,
“bw_hz”: 125000,
“power”: 14,
“infodesc”: 0
}
},
“gps_conf”: {
“gw_latitude”: 0,
“gw_longitude”: 0,
“gw_altitude”: 0,
“fixed_altitude”: false
}}
mtcdt:/var/config/lora-packet-forwarder-usb$ sudo /etc/init.d/lora-packet-forwarder-usb start
Found MTAC-LORA-G16-868 with MTAC-LORA-2.1 hardware
Starting lora-packet-forwarder-usb: *** GPS Packet Forwarder for Lora Gateway ***
Version: 1.4.1
*** Lora concentrator HAL library version info ***
Version: 1.7.0; Options: ftdi sx1301 sx1257 full mtac-lora private;INFO: Little endian host
INFO: found global configuration file global_conf.json, parsing it
INFO: global_conf.json does contain a JSON object named SX1301_conf, parsing SX1301 parameters
INFO: radio 0 enabled, center frequency 867500000
lgw_rxrf_setconf:894: Note: rf_chain 0 configuration; en:1 freq:867500000
INFO: radio 1 enabled, center frequency 868500000
lgw_rxrf_setconf:894: Note: rf_chain 1 configuration; en:1 freq:868500000
INFO: Lora multi-SF channel 0> radio 1, IF -400000 Hz, 125 kHz bw, SF 7 to 12
lgw_rxif_setconf:998: Note: LoRa ‘multi’ if_chain 0 configuration; en:1 freq:-400000 SF_mask:0x7e
INFO: Lora multi-SF channel 1> radio 1, IF -200000 Hz, 125 kHz bw, SF 7 to 12
lgw_rxif_setconf:998: Note: LoRa ‘multi’ if_chain 1 configuration; en:1 freq:-200000 SF_mask:0x7e
INFO: Lora multi-SF channel 2> radio 1, IF 0 Hz, 125 kHz bw, SF 7 to 12
lgw_rxif_setconf:998: Note: LoRa ‘multi’ if_chain 2 configuration; en:1 freq:0 SF_mask:0x7e
INFO: Lora multi-SF channel 3> radio 0, IF -400000 Hz, 125 kHz bw, SF 7 to 12
lgw_rxif_setconf:998: Note: LoRa ‘multi’ if_chain 3 configuration; en:1 freq:-400000 SF_mask:0x7e
INFO: Lora multi-SF channel 4> radio 0, IF -200000 Hz, 125 kHz bw, SF 7 to 12
lgw_rxif_setconf:998: Note: LoRa ‘multi’ if_chain 4 configuration; en:1 freq:-200000 SF_mask:0x7e
INFO: Lora multi-SF channel 5> radio 0, IF 0 Hz, 125 kHz bw, SF 7 to 12
lgw_rxif_setconf:998: Note: LoRa ‘multi’ if_chain 5 configuration; en:1 freq:0 SF_mask:0x7e
INFO: Lora multi-SF channel 6> radio 0, IF 200000 Hz, 125 kHz bw, SF 7 to 12
lgw_rxif_setconf:998: Note: LoRa ‘multi’ if_chain 6 configuration; en:1 freq:200000 SF_mask:0x7e
INFO: Lora multi-SF channel 7> radio 0, IF 400000 Hz, 125 kHz bw, SF 7 to 12
lgw_rxif_setconf:998: Note: LoRa ‘multi’ if_chain 7 configuration; en:1 freq:400000 SF_mask:0x7e
INFO: Lora std channel> radio 1, IF -200000 Hz, 250000 Hz bw, SF 7
lgw_rxif_setconf:972: Note: LoRa ‘std’ if_chain 8 configuration; en:1 freq:-200000 bw:2 dr:2
INFO: FSK channel> radio 1, IF 300000 Hz, 125000 Hz bw, 50000 bps datarate
lgw_rxif_setconf:1028: Note: FSK if_chain 9 configuration; en:1 freq:300000 bw:3 dr:50000 (50000 real dr) sync:0xC194C1
INFO: global_conf.json does contain a JSON object named gateway_conf, parsing gateway parameters
INFO: gateway MAC address is configured to 00800000A0003972
INFO: server hostname or IP address is configured to “localhost”
INFO: upstream port is configured to “1700”
INFO: downstream port is configured to “1700”
INFO: downstream keep-alive interval is configured to 10 seconds
INFO: statistics display interval is configured to 30 seconds
INFO: upstream PUSH_DATA time-out is configured to 100 ms
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
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 “1700”
INFO: downstream port is configured to “1700”
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
WARNING: [main] impossible to open for GPS sync (check permissions)
ERROR: FAIL TO CONNECT BOARD
ERROR: [main] failed to start the concentrator
OKCould someone give me some guidance?
July 8, 2019 at 7:57 am #28150Jason Reiss
KeymasterFound MTAC-LORA-G16-868 with MTAC-LORA-2.1 hardware
Looks like the hardware is not a USB lora card.
The 2.1 geo-location hardware should use this forwarder binary./opt/lora/pkt_forwarder
Also use the 2.1 configuration files in /opt/lora/
global_conf.json.MTAC_LORA_2_1*July 8, 2019 at 11:41 am #28157a.dolera1bc@gmail.com
ParticipantJuly 15, 2019 at 3:03 pm #28220a.dolera1bc@gmail.com
ParticipantHello Jason, I’ve already managed to start lora_pkt_fw my question is now the following, how do I get this to communicate with the lora_gateway_bridge, which should I install? And how to configure it?
Thanks!
-
AuthorPosts
- You must be logged in to reply to this topic.