# MatchX no TX **URL:** \ **Category:** Gateways\ **Created:** [December 18, 2017, 6:58pm UTC](https://www.thethingsnetwork.org/forum/t/matchx-no-tx/11240 "2017-12-18T18:58:03Z")\ **Posts on this page:** 20\ **Page:** 1
**Author:** ![moeterbln](https://www.thethingsnetwork.org/forum/user_avatar/www.thethingsnetwork.org/moeterbln/32/20484_2.png) [@moeterbln](https://www.thethingsnetwork.org/forum/u/moeterbln)\ **Post date:** [December 18, 2017, 6:58pm UTC](https://www.thethingsnetwork.org/forum/t/matchx-no-tx/11240/1 "2017-12-18T18:58:03Z")
Suddenly my MatchX gateway stopped sending. I can’t join anymore. Nothing changed by me. With the same node I can join and get packets on all other gateways I’ve tried. It was all working for 2 Month without changes. Did anyone have similar problems? ---
**Author:** ![Verkehrsrot](https://www.thethingsnetwork.org/forum/user_avatar/www.thethingsnetwork.org/verkehrsrot/32/46588_2.png) [@Verkehrsrot](https://www.thethingsnetwork.org/forum/u/Verkehrsrot)\ **Post date:** [December 18, 2017, 7:53pm UTC](https://www.thethingsnetwork.org/forum/t/matchx-no-tx/11240/2 "2017-12-18T19:53:11Z")
Did you check if `txpk` packets arrive on port 1700 on the WAN-Port of the gateway? `sudo tcpdump -AUq port 1700` See [https://www.thethingsnetwork.org/wiki/Backend/Connect/Gateway](https://www.thethingsnetwork.org/wiki/Backend/Connect/Gateway) If your MatchX Gateway is from the first batch, you may try to derive the root password from the Gateway’s MAC-address, as described in the MatchX thread in this forum. Then you can take a look at the gateway’s log with `journalctl`. ---
**Author:** ![moeterbln](https://www.thethingsnetwork.org/forum/user_avatar/www.thethingsnetwork.org/moeterbln/32/20484_2.png) [@moeterbln](https://www.thethingsnetwork.org/forum/u/moeterbln)\ **Post date:** [December 18, 2017, 8:28pm UTC](https://www.thethingsnetwork.org/forum/t/matchx-no-tx/11240/3 "2017-12-18T20:28:46Z")
Unfortunally that root-password doesn’t work. And I see packets going to the matchx looking in my internet-connection. TTN console matches those packets. I see the json-data in my wireshark dump. Yesterday i was working ☹ ---
**Author:** ![Verkehrsrot](https://www.thethingsnetwork.org/forum/user_avatar/www.thethingsnetwork.org/verkehrsrot/32/46588_2.png) [@Verkehrsrot](https://www.thethingsnetwork.org/forum/u/Verkehrsrot)\ **Post date:** [December 18, 2017, 9:15pm UTC](https://www.thethingsnetwork.org/forum/t/matchx-no-tx/11240/4 "2017-12-18T21:15:41Z")
Did you try to send a packet to node with confirmation flag set (ACK)? Are those packets displayed as ACKed in the application? If yes this would proof that TX hardware is up and running. (As long as there is no other TTN gateway in range of node) ---
**Author:** ![moeterbln](https://www.thethingsnetwork.org/forum/user_avatar/www.thethingsnetwork.org/moeterbln/32/20484_2.png) [@moeterbln](https://www.thethingsnetwork.org/forum/u/moeterbln)\ **Post date:** [December 18, 2017, 9:40pm UTC](https://www.thethingsnetwork.org/forum/t/matchx-no-tx/11240/5 "2017-12-18T21:40:43Z")
Unfortunally the OTAA Join reply is not received by the node. In the UDP traffic I can clearly see the Join Ack that should be sent to the node. ---
**Author:** ![moeterbln](https://www.thethingsnetwork.org/forum/user_avatar/www.thethingsnetwork.org/moeterbln/32/20484_2.png) [@moeterbln](https://www.thethingsnetwork.org/forum/u/moeterbln)\ **Post date:** [December 18, 2017, 9:52pm UTC](https://www.thethingsnetwork.org/forum/t/matchx-no-tx/11240/6 "2017-12-18T21:52:09Z")
Ah now I see the problem. The gateway generates a error “TOO\_LATE” unfortunately that seems to be a problem with the TTN router/backend. My internet connection is fine. I don’t see any delays to various sites. Using router.eu.thethings.network should be the right one. At least for 2 month that was working. ---
**Author:** ![moeterbln](https://www.thethingsnetwork.org/forum/user_avatar/www.thethingsnetwork.org/moeterbln/32/20484_2.png) [@moeterbln](https://www.thethingsnetwork.org/forum/u/moeterbln)\ **Post date:** [December 18, 2017, 9:58pm UTC](https://www.thethingsnetwork.org/forum/t/matchx-no-tx/11240/7 "2017-12-18T21:58:48Z")
That is really annoying that I have to look at dumps for simple debugging things. Shouldn’t be there any other way where I can debug such things? It seems to be messaged to the backend so that could be displayed in the ttn console - That would have saved some hours searching every where. ---
**Author:** ![Verkehrsrot](https://www.thethingsnetwork.org/forum/user_avatar/www.thethingsnetwork.org/verkehrsrot/32/46588_2.png) [@Verkehrsrot](https://www.thethingsnetwork.org/forum/u/Verkehrsrot)\ **Post date:** [December 18, 2017, 10:25pm UTC](https://www.thethingsnetwork.org/forum/t/matchx-no-tx/11240/8 "2017-12-18T22:25:45Z")
I tried an OTAA join on my TTN connected MatchX Gateway. No problems. Node joins on first attempt. ---
**Author:** ![moeterbln](https://www.thethingsnetwork.org/forum/user_avatar/www.thethingsnetwork.org/moeterbln/32/20484_2.png) [@moeterbln](https://www.thethingsnetwork.org/forum/u/moeterbln)\ **Post date:** [December 19, 2017, 11:01am UTC](https://www.thethingsnetwork.org/forum/t/matchx-no-tx/11240/9 "2017-12-19T11:01:43Z")
Comparing to a Laired and a RAK831 Gateway looking at the dumps all looks the same but works. It is totally unclear why the gateway issues a TOO\_LATE-Error. ---
**Author:** ![Verkehrsrot](https://www.thethingsnetwork.org/forum/user_avatar/www.thethingsnetwork.org/verkehrsrot/32/46588_2.png) [@Verkehrsrot](https://www.thethingsnetwork.org/forum/u/Verkehrsrot)\ **Post date:** [December 20, 2017, 10:13am UTC](https://www.thethingsnetwork.org/forum/t/matchx-no-tx/11240/10 "2017-12-20T10:13:40Z")
New idea on this: maybe your gateway has no correct time. GPS up und running? ---
**Author:** ![moeterbln](https://www.thethingsnetwork.org/forum/user_avatar/www.thethingsnetwork.org/moeterbln/32/20484_2.png) [@moeterbln](https://www.thethingsnetwork.org/forum/u/moeterbln)\ **Post date:** [December 20, 2017, 10:38am UTC](https://www.thethingsnetwork.org/forum/t/matchx-no-tx/11240/11 "2017-12-20T10:38:44Z")
It all looks good. I changed to their could and will test in the evening. GPS is running fine to their console. What currently is not working is spectral scan. CPU load is at 17% without any traffic. Maybe that is normal. Looking at the network packets the timing is the same compared with the other gateways. Clearly I can see in the payload that the packets are totally in time. Currently I suppose a hardware defect. Maybe something that has to do with the part which is responsible for the spectral scan - That was working in the past. ---
**Author:** ![moeterbln](https://www.thethingsnetwork.org/forum/user_avatar/www.thethingsnetwork.org/moeterbln/32/20484_2.png) [@moeterbln](https://www.thethingsnetwork.org/forum/u/moeterbln)\ **Post date:** [December 20, 2017, 6:12pm UTC](https://www.thethingsnetwork.org/forum/t/matchx-no-tx/11240/12 "2017-12-20T18:12:17Z")
Ok I compared with the MatchX cloud. The Join Accept from the cloud to the gateway is sent with a delay of 0.26sec while the ttn cloud send that Join Accept after 4.6sec and the MatchX gateway drops the packet with error TOO\_LATE. Is there a reason why the packet is sent to the gateway that early? Maybe that can be reduced a bit to help here? I don’t know any setting to influence that delay. Other gateways seem to be fine with that behavior of ttn. ---
**Author:** ![moeterbln](https://www.thethingsnetwork.org/forum/user_avatar/www.thethingsnetwork.org/moeterbln/32/20484_2.png) [@moeterbln](https://www.thethingsnetwork.org/forum/u/moeterbln)\ **Post date:** [December 20, 2017, 6:17pm UTC](https://www.thethingsnetwork.org/forum/t/matchx-no-tx/11240/13 "2017-12-20T18:17:28Z")
I just see that I can confirm that the delay is the essential problem in my case. I just got a Join Accept that was sent out. The delay at the gateway for the Join Accept was 4.19sec and that was accepted by the MatchX. ---
**Author:** ![Verkehrsrot](https://www.thethingsnetwork.org/forum/user_avatar/www.thethingsnetwork.org/verkehrsrot/32/46588_2.png) [@Verkehrsrot](https://www.thethingsnetwork.org/forum/u/Verkehrsrot)\ **Post date:** [December 20, 2017, 7:23pm UTC](https://www.thethingsnetwork.org/forum/t/matchx-no-tx/11240/14 "2017-12-20T19:23:17Z")
Spectral scan via MatchX cloud ist not working on my MatchX gateway, too, so don’t worry about that. ---
**Author:** ![Verkehrsrot](https://www.thethingsnetwork.org/forum/user_avatar/www.thethingsnetwork.org/verkehrsrot/32/46588_2.png) [@Verkehrsrot](https://www.thethingsnetwork.org/forum/u/Verkehrsrot)\ **Post date:** [December 20, 2017, 7:26pm UTC](https://www.thethingsnetwork.org/forum/t/matchx-no-tx/11240/15 "2017-12-20T19:26:57Z")
Sure that this is not a network latency / routing problem? To check if RX/TX hardware of your MatchX gateway is properly working, you could connect a node by ABP instead OTAA and send some downlink data via the TTN console. If the node receives it, your gateway should be ok. ---
**Author:** ![moeterbln](https://www.thethingsnetwork.org/forum/user_avatar/www.thethingsnetwork.org/moeterbln/32/20484_2.png) [@moeterbln](https://www.thethingsnetwork.org/forum/u/moeterbln)\ **Post date:** [December 20, 2017, 8:26pm UTC](https://www.thethingsnetwork.org/forum/t/matchx-no-tx/11240/16 "2017-12-20T20:26:57Z")
Using the MatchX cloud works like ttn cloud used to work before. So hardware seems to be OK. There is nothing I can do. I don’t understand why the packets come that late with TTN to the gateway. Did you look at the traffic? What delays are at your GW for join accept messages? ---
**Author:** ![moeterbln](https://www.thethingsnetwork.org/forum/user_avatar/www.thethingsnetwork.org/moeterbln/32/20484_2.png) [@moeterbln](https://www.thethingsnetwork.org/forum/u/moeterbln)\ **Post date:** [December 21, 2017, 8:02pm UTC](https://www.thethingsnetwork.org/forum/t/matchx-no-tx/11240/17 "2017-12-21T20:02:19Z")
The Issue has been solved. For the communication regarding MatchX you can read here: [https://matchx.io/community/cloud-software](https://matchx.io/community/cloud-software) In short: They changed some constants that where obviously exactly the problem I observed. Now suddenly my ssh console closed and they updated my firmware and it is working again. Firmware versioning -\> Fail Parameter changes -\> Fail Accusing TTN of the behaviour -\> Fail No “Sorry for not listening to you” -\> Fail So that is an AWSOME company as they call themselves and keep making other products bad. Sorry I had to rant but I’m really upset. Just in case you have any problems with that gateway don’t trust what the MatchX people say. ---
**Author:** ![Verkehrsrot](https://www.thethingsnetwork.org/forum/user_avatar/www.thethingsnetwork.org/verkehrsrot/32/46588_2.png) [@Verkehrsrot](https://www.thethingsnetwork.org/forum/u/Verkehrsrot)\ **Post date:** [December 21, 2017, 8:19pm UTC](https://www.thethingsnetwork.org/forum/t/matchx-no-tx/11240/18 "2017-12-21T20:19:31Z")
Today i wanted to check the issue in my MatchX gateway and found, that i have the same problem suddenly. OTAA joining is not possible any longer. > ## TTN Console > > Join Accept > 21:06:35 > > { > “gw\_id”: “eui-40d63cfffe030e78”, > “payload”: “ILL7HyMWilV2GKJhWbx/Q+ketta7e810c0+8Qfw8s3aG”, > “lora”: { > “spreading\_factor”: 7, > “bandwidth”: 125, > “air\_time”: 71936000 > }, > “coding\_rate”: “4/5”, > “timestamp”: “2017-12-21T20:06:35.754Z”, > “frequency”: 868100000 > } > > Join Request > 21:06:31 > > { > “gw\_id”: “eui-40d63cfffe030e78”, > “payload”: “ACt0ANB+1bNwA+EbAAujBABYX00bwmg=”, > “dev\_eui”: “0004A30B001BE103”, > “lora”: { > “spreading\_factor”: 7, > “bandwidth”: 125, > “air\_time”: 61696000 > }, > “coding\_rate”: “4/5”, > “timestamp”: “2017-12-21T20:06:31.121Z”, > “rssi”: -59, > “snr”: 10, > “app\_eui”: “70B3D57ED000742B”, > “frequency”: 868100000 > } > > Assuming base64-encoded packet > ACt0ANB+1bNwA+EbAAujBABYX00bwmg= > > Message Type = Join Request > AppEUI = 70B3D57ED000742B > DevEUI = 0004A30B001BE103 > DevNonce = 5F58 > MIC = 4D1BC268 > > ==== > > ## MatchX Gateway Syslog: > > Thu Dec 21 20:06:31 2017 daemon.info syslog[5145]: > INFO: Received pkt from mote: D000742B (fcnt=46037) > > Thu Dec 21 20:06:31 2017 daemon.info syslog[5145]: > JSON up: {“rxpk”:[{“tmst”:137200611,“time”:“2017-12-21T20:06:30.078382Z”,“tmms”:1197922009078,“chan”:0,“rfch”:1,“freq”:868.100000,“stat”:1,“modu”:“LORA”,“datr”:“SF7BW125”,“codr”:“4/5”,“lsnr”:10.0,“rssi”:-59,“size”:23,“data”:“ACt0ANB+1bNwA+EbAAujBABYX00bwmg=”}]} > > Thu Dec 21 20:06:35 2017 daemon.info syslog[5145]: INFO: [down] PULL\_RESP received - token[121:8] : ) > > Thu Dec 21 20:06:35 2017 daemon.info syslog[5145]: > JSON down: {“txpk”:{“imme”:false,“tmst”:142200611,“freq”:868.1,“rfch”:0,“powe”:14,“modu”:“LORA”,“datr”:“SF7BW125”,“codr”:“4/5”,“ipol”:true,“size”:33,“ncrc”:true,“data”:“ILL7HyMWilV2GKJhWbx/Q+ketta7e810c0+8Qfw8s3aG”}} > > Thu Dec 21 20:06:35 2017 daemon.debug syslog[5145]: src/jitqueue.c:233:jit\_enqueue(): ERROR: Packet REJECTED, already too late to send it (current=141910935, packet=142200611, type=0) > > Thu Dec 21 20:06:35 2017 daemon.info syslog[5145]: ERROR: Packet REJECTED (jit error=1) ---
**Author:** ![moeterbln](https://www.thethingsnetwork.org/forum/user_avatar/www.thethingsnetwork.org/moeterbln/32/20484_2.png) [@moeterbln](https://www.thethingsnetwork.org/forum/u/moeterbln)\ **Post date:** [December 21, 2017, 8:21pm UTC](https://www.thethingsnetwork.org/forum/t/matchx-no-tx/11240/19 "2017-12-21T20:21:47Z")
If they are not already are updating your firmware just wait they have full access if you didn’t block the OpenVPN tunnel and trust them. ---
**Author:** ![Verkehrsrot](https://www.thethingsnetwork.org/forum/user_avatar/www.thethingsnetwork.org/verkehrsrot/32/46588_2.png) [@Verkehrsrot](https://www.thethingsnetwork.org/forum/u/Verkehrsrot)\ **Post date:** [December 21, 2017, 8:23pm UTC](https://www.thethingsnetwork.org/forum/t/matchx-no-tx/11240/20 "2017-12-21T20:23:51Z")
After i found that the gateway openes up a vpn tunnel to matchX cloud, it isolated it in the network, but left vpn tunnel open. How can i see that they upgraded my gateway, and when can i expect this to happen? Strange… [Next page](https://www.thethingsnetwork.org/forum/t/matchx-no-tx/11240.md?page=2)