We checked the logs, but they are similar to the previous ones—only showing DDNS and GoodCloud connection failures. So unfortunately, there isn’t much useful information there.
As mentioned earlier, if the issue occurs again, would it be possible to avoid changing the Repeater settings, then provide internet access via Ethernet or USB tethering and allow us remote access through GoodCloud so we can investigate further?
We have set up a test environment to try to reproduce the issue and let it run for quite a while, but unfortunately we were unable to reproduce it.
Our technicians have mobile cell routers - but they aren’t out onsite for hours at a time and don’t leave them plugged in. These are homes where the router provides internet to other equipment outside the home.
Any eta on this release? I’d love to start rolling it out to the fleet.
or is there anything we can do locally on existing systems (settings change/File change) in the mean time?
The next firmware for the AR300M will be v4.5, which includes minor version upgrades, so it may not be released very soon.
Would you be open to testing a beta firmware? If so, we can ask the development team to merge the fix into the current stable v4.3.25 firmware and provide it to you for validation to confirm whether the issue is fully resolved.
This is not good news. The last update for this router was a year ago. The router is not EOL, yet it still has several security and functional problems that I have already raised in other posts.
@butterfry has identified an issue that affects hundreds of units, which your engineering team has confirmed, and it likely affects many other users as well
yeah not good. I need a solution to this, it’s costing us thousands of dollars to send technicians out to reconnect these. I would take a beta firmware, but I don’t really like that idea.
So far, we’ve only been able to reproduce the issue once locally. Based on that, our development team has implemented a fix. However, we are still testing and verifying whether this fix fully resolves the issue. As mentioned earlier, the problem is difficult to reproduce in our environment.
If you’re willing, we can provide a version with the fix included so we can further validate it together in your environment and help move this forward.
This version is built on the current stable release v4.3.25, with no changes other than the Wi-Fi fix. We expect overall stability and functionality to remain largely unchanged.
Additionally, could you let us know your purchase channel? Was it through our consumer sales channels, such as the official website, Amazon, or Shopee, or are you an enterprise customer who purchased through one of our sales representatives via email?
If it’s the latter, we recommend contacting your sales representative so that we can provide further assistance with this matter.
I’m happy to try the test for sure. The issue seems to be more prevalent in certain Wi-Fi environments than others. Some work just fine and the issue never appears, others it seems to happen on a weekly basis. I can update the firmware on several troublesome sites and watch them.
I tried several times to contact your volume sales team but gave up. We purchase all of our routers at full retail price either through your website or Amazon.
