|
|
|
If you log into your deco via the http interface (if your model has one)- what does the logs say at that time?
automatic updates are done around that time (early hours of the morning)
Morm:
automatic updates are done around that time (early hours of the morning)
Wait, I have automatic updates off, and I had already upgraded manually. So there should be no upgrade operation.
So Farmside do actually manage our modems and upgrade them? If so that implies they do in fact know what firmware was running on all the routers all along and which ones were affected, contrary to what they told me...
r0bbie:
If you log into your deco via the http interface (if your model has one)- what does the logs say at that time?
I use a log scraper because the web interface is pretty awful.
Basically nothing for a few minutes beginning 3:17am. This is consistent with the constant crashes I get. Fortunately the deco syslog is very noisy, full of all kinds of crazy "normal" errors, missing files, whatever is running on the Deco that simply stumbles around constantly in "normal" operation. So it's easy to spot an outage.
Tue Sep 15 03:17:53 2026 user.notice : util_get_online_status: 0
Tue Sep 15 03:17:53 2026 user.notice : Online status is normal and goto next round
Tue Sep 15 03:21:00 2026 user.notice mobilev6: MTUV6= 0
Tue Sep 15 03:21:00 2026 user.notice mobilev6: SITPREFIXV6=
Tue Sep 15 03:21:00 2026 daemon.emerg camera_security[2008]: 131072+0 records in
Tue Sep 15 03:21:00 2026 daemon.emerg camera_security[2008]: 131072+0 records out
Tue Sep 15 03:21:00 2026 user.notice : SLAAC address not valid!
Hi there, (joined GeekZone to reply to this).
I have been battling OneNZ and TPLink for months over this issue x58 4g. Ironically, I applied a beta firmware to resolve an issue where additional deco mesh units were connected (green light) but could not be seen in the app (so could not configure etc). The beta update resolved the app problem but then introduced the random crash problem you are encountering.
I have worked with both OneNZ and TPLink to try to resolve. OneNZ were hopeless - stating no known issues, claiming it was a problem with the less than perfect reception I have causing CPU spikes etc, etc. TPLink were better, but in the end wanted me to install logging software and allow technicians to remote in to monitor. The amount of work was too much and I was sceptical it would work. I had spent days on this and was reluctant to spend more time on it.
In the end I took the OneNZ sim from the X58 4g and placed it in a very old 4g Spark Modem I had lying around and reset the deco units (including the x58 4g) to act as a Mesh only to serve internet around my house.
The Spark 4G is slightly slower than the X58 - but for my basic needs is fine - and ROCK solid. No crashes at all since for months now.
The x58-4g firmware I have that is causing the issue is 1.2.1 Build 20260826 rel 13194. I have turned off auto update as I want to research any future update notes before I upgrade in the future. However, may keep the current configuration as it just works.
I used to be impressed with the Deco system, but lately the software quality seems to have slipped.
SteveXNZ:
I had multiple issues with my X58-4G back in May, and Farmside couldn't resolve them. They handed off to OneNZ who couldn't find any backend faults. Despite multiple modem swaps the issues remained, and Farmside recommended I switch providers. Am now a happy Starlink customer with faster and more reliable service at much the same price. Do the numbers and keep this as an option.
I agree with this, think whatever you want about Mr Musk, but for rural / remote internet connections this is in my opinion currently the 'best option'. I am only staying with my current 4G service as the cost is slightly lower and I don't want to go through the installation / contract hassle. For now...
anarkiwi:
RogerMellie:
I have just turned off beam forming, as well as mesh functionality on all currently connected wifi devices and am still seeing CPU usage frequently spiking to 100%, with memory usage usually at or hovering around 69%.
The Deco app only allows me to see CPU usage on the main Deco device (the router)
I wrote a python script to scrape this from the third party TPLInk library. I don't use the mesh capability. When my Deco crashes, I see its CPU go up to 100% for a few minutes and stay there, and its memory go to about 80% and stay there. Then the Deco stops responding to ping. A few minutes after than the Internet connection goes down - sometimes for up to 30 minutes. Then it reboots itself. I have bisected all the config options I can drive from the app (there are not too many due to the vendorlocking issues - again customers are not to be trusted, apparently). I can't find any option that makes a difference, even with most everything off I can get my hands on and still have a somewhat functioning router. I also (of course) tried not scraping it all and uninstalling the app to make sure it wasn't the scraping of the data itself causing an issue. It's not. At a complete guess, it's choking on some random Internet traffic or its NAT resources are overflowing and it dies and watchdogs. I think it's the former (random Internet data) as there really is no time correlation - it is just as likely to crash at 3am under no load, as it is in the middle of streaming NetFlix.
yes - I had the same symptoms, random crashes / lock up (30 mins etc), and then sometimes reboots. If I had to guess I believe there is a problem with the modem related firmware.
geeknerdgeek:
The x58-4g firmware I have that is causing the issue is 1.2.1 Build 20260826 rel 13194. I have turned off auto update as I want to research any future update notes before I upgrade in the future. However, may keep the current configuration as it just works.
That's the firmware I have and it still seems broken. I would be more disposed to help for sure if Farmside would have fronted up to begin with. In response to my complaint one of the excuses for not telling me in proactively was, "we had no fix for it so telling people about the problem would not have achieved anything." Pretty poor customer service IMHO.
anarkiwi:
geeknerdgeek:
The x58-4g firmware I have that is causing the issue is 1.2.1 Build 20260826 rel 13194. I have turned off auto update as I want to research any future update notes before I upgrade in the future. However, may keep the current configuration as it just works.
That's the firmware I have and it still seems broken. I would be more disposed to help for sure if Farmside would have fronted up to begin with. In response to my complaint one of the excuses for not telling me in proactively was, "we had no fix for it so telling people about the problem would not have achieved anything." Pretty poor customer service IMHO.
Apologies, my response was probably not clear. I am now running a 4g spark modem feeding into a deco mesh to send internet through the house. This is the 'configuration' i am using. Ie the X58 4g is not doing any 4g modem work - just now acting a wifi mesh node. This 'config' is stable for me.
You are correct that the current firmware listed above has problems. My understanding is that there is some business relationship between Farmside and One NZ where Farmside use the One NZ deco modems - so out of their control (but still their problem!). Further compounding the issue is that the X58 4g is specific to One NZ who used to run a different firmware than the equivalent X50 4g (which the x58 is based on). Further compounding the issue is that I believe One NZ used to gate / restrict the rollout of the firmware updates which used to cause problems if you mixed the One NZ x58 4g modem with other retail deco mesh units as the retail deco units sometimes used to get firmware ahead of the One NZ modem. This is what prompted me to work with TP Link to flash beta Firmware onto the One NZ x58 4g. While the Mesh problems resolved it introduced the modem bug / crashing. Yes, messy messy messy for me...
Frustrating to read of others battling with Farmside and OneNZ, only for me to be told by Farmside support over the phone earlier this week that they'd "not heard of this issue". They were quite happy to suggest sending a replacement modem though (another X58 4G), without me even asking for it.
Having said that, I can report that this crashing issue has only happened once in approximately the last week, even without applying the latest firmware update mentioned earlier in this thread.
Currently running 1.2.1 Build 20260826 rel. 13194
Interesting to see that the latest firmware update is no longer available/visible to me in the app.
Would this suggest that Farmside or OneNZ have withdrawn it ?
|
|
|