Does chirpstack send PUSH_ACK to the gateway?

Hello!

I’m currently trying to troubleshoot some problems I have whit the dowlinks ( I talk about that here ), something that I have noticed is that when I looked up the statistics that my gateway is prompting:

##### 2024-06-18 15:04:32 GMT #####
### [UPSTREAM] ###
# RF packets received by concentrator: 61
# CRC_OK: 72.13%, CRC_FAIL: 27.87%, NO_CRC: 0.00%
# RF packets forwarded: 61 (2486 bytes)
# PUSH_DATA datagrams sent: 55 (14915 bytes)
# PUSH_DATA acknowledged: 0.00%
#
### [DOWNSTREAM] ###
# PULL_DATA sent: 3 (0.00% acknowledged)
# PULL_RESP(onse) datagrams received: 0 (0 bytes)
# RF packets sent to concentrator: 0 (0 bytes)
# TX errors: 0
# BEACON queued: 0
# BEACON sent: 0
# BEACON rejected: 0
#
### [JIT] ###
#
### [LINK TESTING MOTE: 00CC01AF] ###
# Packets received from link testing mote: 0
#
### [GATEWAY] ###
# Boot time: 2024-06-18 14:23:32 GMT
# Temperature: 43 C (code=101)
#
##### END #####

As you can see no PUSH_DATA nor PULL_DATA were acknowledged, is this normal on the chirpstack environment?, how could I keep trying to trace the problem?

If correctly configured, then the ACK rate should be 100%. This might be a firewall issue. See also for some troubleshooting steps:

https://www.chirpstack.io/docs/guides/connect-gateway.html

2 Likes