Hello everyone, I try to describe the problem and setup the best as I can. And also I am very new in linux and IoT stuffs.
I have AP MTCAP-915-041A con mLinux v6.0.1 and I have installed chirpstack-gateway-bridge_4.0.8-r1_arm926ejste.ipk through ssh and following this link.
The server is made with Ubuntu 20.04.2 LTS “focal” and it has ChirpStack V4. I can see the ShirpStack web inteface trhoug IP http://192.168.2.141:8080 (direct ethernet connection to Acces Point- AP or Gateway -GW Conduit). This connetion is made with a Ethernet-toUSB connection (the GW has a DHCP server) and in the motherboard o my PC I have Internet IP 10.73.97.xxx.
The problem: I can’t see the GW online; I mean, I never see LoRaWAN frames. This is in LoRa mode NERWORK SERVER. In LoRa mode PACKET FORWARDER, y saw some data comming out from the GW and comming out from the server with the command sudo tcpdump -AUq -i eth0 port 1700 -v
I have modified a bit the *.toml files but without success.
Thanks.
Hi @datnus. Yes, it is opened because in LoRa mode PACKET FORWARDER I could see the packets or some of them. I attach a capture. And I have installed all via docker, so, I undestand it is installed the chirpstack-gateway-bridge.
I am trying configure the region AU915.
In the GW, with the command tail -f /var/log/lora-pkt-fwd-1.log I get this:
admin@mtcap:/var/log$ tail -f lora-pkt-fwd-1.log
# RF packets sent to concentrator: 0 (0 bytes)
# TX errors: 0
# BEACON queued: 0
# BEACON sent so far: 0
# BEACON rejected: 0
### [JIT] ###
# SX1301 time (PPS): 1262467616 2
src/jitqueue.c:449:jit_print_queue(): INFO: [jit] queue is empty
### [GPS] ###
# GP^C
In the GW, with the command tail -f var/logs/messages, I get this
2023-05-22T18:15:47.250401-03:00 mtcap chirpstack-gateway-bridge[2283]: time="2023-05-22T18:15:47.249371232-03:00" level=error msg="[client] dial tcp 10.73.91.151:1883: connect: network is unreachable" module=mqtt
2023-05-22T18:15:47.272948-03:00 mtcap chirpstack-gateway-bridge[2283]: time="2023-05-22T18:15:47.271347073-03:00" level=warning msg="[client] failed to connect to broker, trying next" module=mqtt
2023-05-22T18:15:47.276862-03:00 mtcap chirpstack-gateway-bridge[2283]: time="2023-05-22T18:15:47.276109933-03:00" level=error msg="[client] Failed to connect to a broker" module=mqtt
2023-05-22T18:15:47.285896-03:00 mtcap chirpstack-gateway-bridge[2283]: time="2023-05-22T18:15:47.284283494-03:00" level=error msg="integration/mqtt: connection error" error="network Error : dial tcp 10.73.91.151:1883: connect: network is unreachable"
I add IP 192.168.2.141 in the redis location (chirpsatack *.toml file) and I could execute the web interface of the ChirpStack in this IP 192.168.2.141:8080
Hi,
Let’s come back to the basis.
If you installed gateway bridge on the gateway, you need to set up your gateway in packet forwarder mode, and send data to 127.0.0.1, uplink / downlink port = 1700.
In the toml file, you must specify the url of your server in the mqtt parameters. Try unsecure MQTT first (port 1883).
On server side, you must open port 1883, because your gateway will communicate through MQTT.
Another solution is to install gateway bridge on server side, and then, configure your packet forwarder with the ip of your server.
Do not use the “network server” setting of the gateway, this will use the local internal NS of the gateway.
For your information, Multitech integrated Chirpstack in version 6.3.0 of the firmware.
Hope this helps.
Thanks @Jerome73 .
I have installed the gateway-bridge in mi Gateway Mutitech and I have leaved this configuration on MQTT authentication: server=“tcp://127.0.0.1:1883”
Hi everyone. After several atempts we reinstall all from zero. We changed the redis for the IP that AP Conduit gives us 192.168.2.141 and we set the AP Conduit with this IP in the server address (port 1700 both); and packer forwarder also. With this, and no touchin any toml or config file, we could see the gateway Mutitech online. So, the IP must be in the same network.
[redis]
# Server address or addresses.
#
# Set multiple addresses when connecting to a cluster.
servers=[
"redis://$REDIS_HOST/",
"redis://192.168.2.141",
]
