I have a Mikrotik WAP LR8 (running 7.18.1) connecting to TTN using BS/CUPS
After a few hours (non-deterministic, but less than 12) it just stops forwarding with the log message:
[FWD] gateway-0 forwarder stopped
There’s typical messages in the log: RX packets, LNS signalling etc but nothing to suggest a problem. I know everyone needs a nap from time to time, but this thing can’t keep online.
Has anyone else seen this?
Thanks, Rob
Hi,
I’ve had this issue with firmware 7.17.x but now I’ve upgraded my gateways to 7.18 and 7.18.2 and I’ve not had the issue. Some gateways have been up for more than a week … I’ll keep monitoring.
Can you try 7.18.2 and see if this is still happening ?
Bad news I got the issue on 2 WAP LR8 running 7.18.1 and 7.18.2 today. One of them, in addition to being disconnected, had lost its link between device & Network Server definition.
I’ve opened a ticket at microtik support.
@robshep if you’re still experiencing the issue I suggest you do the same to put the pressure on them have this issue investigated & solved since this is really a showstopper for an otherwise quite nice gateway …
I’ve seen the same behaviour on my gateway (also running v7.18.2.)
Though I can’t reproduce it exactly, it seems to occur mostly when the router can’t reach the server on the first attempt or has abnormally high latency while doing so.
My internet connection is “reset” every night and comes back with a different public IP. The router appears to have difficulties re-establishing the connection to the TTN server in this case.
I solved it by automatically rebooting the WAP whenever the public IP changes. This information is available from my DSL router, which reports it to a MQTT broker, which the Mikrotik can subscribe to and execute a script when the relevant topic changes.
Mikrotik support finally responded to my bug report asking to test on 7.19RC I’ve not done it so far but looking at the changelog I don’t think they fixed it. I’ve built monitoring scripts using the mikrotik API to check the LoRa Status and reboot the gateway & reconfigure LoRa if needed after the reboot since I’ve experienced LoRa config loss when the issue occurs. This is a real pain …