Discussion: Arcadyan Firmware Update Notes

[Ryanthusar]

---

@Mkrtich wrote:

Thor GW entries

health check. detect case (ThorGW)

health check init or restart

I would not expect it to occur every 15 seconds which may indicate a connection issue that the program module is having with the Cloud service. If it had not settled down, you may wish to see if a Power Restart or Factory Reset pacifies it. 

---

My modem updated this morning at 130am to 0.12.09r and I can tell you now that neither the Power Restart, nor Factor Reset, will fix the health check issue. However is annoying that its filling the log up with such

[Sully5]

Hi,

Is it just me or does the reboot button no longer work on 0.12.09r? When you log into the modem and go to "Go To Advanced" -> "Management" -> "System Reset" -> "Restart" it no longer actually restarts the modem whereas it did on all prior firmwares. 

Thanks 

[cf4]

Just got the firmware update and it also noticed that the GUI reboot but no longer works. As well as breaking the GUI reboot button the only other function I can see that has changed is WiFi PMF is enabled by default.

[SammyY]

Have reset the modem less than a month ago, after problems with dropouts that have now been resolved and appear to have been unrelated.

I had not reset since early in the year, and noticed that the password complexity rules for the admin password had changed and my old password was no longer compliant. Other than that hadn't had issues until today.

Today I'm trying to add 2 port forwarding rules from different WAN ports to different destination IP addresses but the same LAN port.

Name Protocol WAN port LAN port Destination IP
machine1 BOTH 3389 3389 192.168.1.30

machine2 BOTH 3500 3389 192.168.1.35

I add machine1 just fine, but with that in the list, whether active or not if I try to add machine 2, I get an error:

192.168.1.1 says

This entry has been in list.

Given that 1) source port and 2) combination of the destination ip and port are different, this should be possible as far as I am aware.

I have found no workarounds. e.g. using a port range instead doesn't resolve it.

Product Vendor Arcadyan

Product Name LH1000
Boot Version 1.0.38-116.118
Firmware Version 0.12.09r
Hardware Version 01

[cf4]

When using port forwarding I don't use the same LAN port for two different IP address. Theoretically it should work but for simplicity I always change the port in the device or apps settings. It might be that the WAN port is already in use by another device using UPNP. Try turning of UPNP in the modem. Advanced > Local Network > UPNP. You might have to reboot the modem to clear the UPNP table. 

[SammyY]

Thanks for the suggestion cf4. Switching off UPNP made no difference, so I'm even more confident it's a bug.

Unfortunately it's a pain switching the port listening for remote desktop connections on Windows. It can be done in the registry but I really don't want to. The idea was to have different ports on the router redirecting to different machines. And yes I'm aware of the security risks. I was mostly just doing this to test if it's possible to use RDP without additional software like TeamViewer.

[SammyY]

I tried just TCP and that seemed to work momentarily but I can't replicate it.

EDIT:

Wow. It depends on the order you put them in.

If I put in the lower destination port first, and save in between, I can put them in as both without the error.
Validation on this page is messed up!

[cf4]

I checked it out on my modem and even when set to TCP it would not allow two devices to use same LAN port. I agree it looks like a bug in the firmware. It doesn't effect me because most of my apps or devices that need port forwarding have settings for changing the port.

[SammyY]

See my response above. The order that you add the rules affects whether they are accepted. Definitely a bug.

[Mkrtich]

Hi - my modem updated to V 0.12.09 r at 3:56 am this morning. I have noticed some peculiarities that other people have also posted. After log-in, I was presented with a bank screen which thankfully had only one choice - a [Refresh] offer, so I selected that and it allowed me in to the Basic Menu screen. 

1. In between VoIP Telephone Service re-registration to Telstra's SIP Server, which happens every 10 minutes, every 15 seconds records appear re health checks for ThorGW and SIP. Looks like an internal mechanism to ensure the SIP re-registration occurs which was not showing up on previous firmware. Unbeknown to me I lost my telephone service for three days recently, so maybe these health checks are there to wake up the re-registrations.   My logs go back to 02.08.2020 now so, as it fills up, older entries must be written over - previously I thought I had entries that went back further than 6 weeks, so all these 15 second checks are occupying space. 

2. When the modem updates its firmware, the time stamps are interrupted by entries that are dated 01.01.2018 indicating a Start syslog FW Version 0.12.09 r with modem serial number, then continue with current date and time. 

3. Wi-Fi Booster firmware updated from WE410443B-TA FW Ver 2.02.63.11 to 2.02.64.01 but still not showing two Wi-Fi Booster folios on Basic Home Screen - maybe they only appear when you connect a Booster to the modem.

4. I may have missed this in the previous version 0.11.11 r, but the Welcome screen no longer has a Telstra Air Icon in the right hand corner - it has been replaced by a Game Optimiser Icon which has a Red Dot - maybe in preparation for a future function. I couldn't see any hint in the Port Forwarding section as to how to Enable it. Technicolor 18.1.c 0514-950 RB still features a Telstra Air Icon. I haven't seen the new version 18.1.c 0543-950 RA yet. 

5. GUI Restart looks like its doing something, going from 1% to 100% in the 120 seconds indicated on the modem, but the modem doesn't turn OFF and then back ON bringing into question if anything actually happened. No sign of a Restart in the System Log entries. Looks like an external power OFF and ON is now required to effect a Restart.

6. Wi-Fi feature Protected Management Frames now Enabled on Default. 

[abcde3]

My Arcadyan LH1000 modem firmware was upgraded to 0.12.09r on Monday morning.

Then the entire guest wifi can't communication between the devices in the same guest wifi network.

My guest wifi network has Chromcast and printer connected. It caused the other devices can't use them.

Can the modem rollback to previous firmware or the bug can be fixed ASAP?

[RobWA]

Yep...same issue here. 

Tried power cycling before and after setting the 2.4GHz "Wi-Fi PMF" to "Off" as suggested without eliminating the log entries every ~15 seconds.

[AB210]

My Arcadyan LH1000 modem firmware was upgraded to 0.12.09r on Monday morning.

And since this my Chamberlain MYQ gateway device will not connect.

Does anyone know why this might be the case?

[cf4]

Firmware update turned Protected Management Frames (WiFi-PMF) on by default suggest you try turning WiFi-PMF  off in the modem.

[AB210]

I forgot to mention that the gateway is connected by Ethernet cable.

[Mkrtich]

Hi - are you using your mobile phone to control the garage gateway? If so, is the failure to connect to the MYQ Garage Gateway from your Phone App occurring when your Phone is connected to the modem's 2.4Ghz or 5Ghz Wi-Fi network when you are at home or when you are remote from the home on a 4G connection? 

Can you see the Gateway in the modem's admin screen - Devices tree as active. Do you have a Static IP address set for the Gateway within the Arcadyan's settings in case it has lost its dynamic one after the modem was upgraded to the current firmware. If applicable, a power reset of the gateway should grab a new address allowing you to assign a fixed address. 

[TwoS1]

re the funny time stamps - I have been noticing this for a while now and in fact thought I may have had a hardware issue. Thinking about it tho I do not believe it is a fault as such.

It seems that when the modem is restarted, the time & date get reset to default (in my case 1/1/2018 10:30am). Any entries in the log will have this timestamp, until the modem does a time sync with the NTP server, at which point the modem's date and time gets updated to current time.

In the past there were generally only a couple of entries in the log with the "funny" date stamp, but it is probably more noticeable now after the 0.12.09r update due to the 15 second Thor(GW) and SIP entries occurring (ie 3 every 15 seconds) meaning many more entries before a NTP time sync occurs.

I just get the feeling that this latest version was pushed out bugs and all, to meet the proposed release of the games optimiser feature

[Mkrtich]

Yes, inclined to agree with you re Event Log entries but I understood that Game Optimiser would be Beta trialed (first month free) for qualified customers in November for the Arcadyan modem. I am not a power user and haven't picked up any significant issues being reported on the forum with 0.12.0.9r.Time will tell. Cheers

[TwoS1]

As I am not a gamer, I have not really looked into Game Optimiser as such, and can only comment on what I have read by other posters here and on Whirlpool. As I read it the Beta test was initially only for Technicolor modems, with Arcadyans getting the option of a free month's trial later on. Having said that, there are some posters on Whirlpool with Arc modems that have "joined the Beta test", whereas for others it has failed . Whatever, the 0.12.09r update has been released for all Arc modems, with the result we are all experiencing the multiple log entries making the log file almost useless. On the plus side, it seems this latest release has fixed the connected ethernet devices display issues that have been problematic ever since the 0.07.05r update.

[EladB1]

Concerning the System Log filters of the ARC LH1000, for the next firmware upgrade, can someone at Crowd Support please advise Arcadyan that the normal or logical way for the Log filters to work is if a user deselects ALL, then all filters should be automatically deselected, so the user can then manually select the filter(s) that he/she is interested in.

As it currently stands in 12.09r, if one wants to see only TR-069 for example, the user must first deselect ALL then manually deselect each of the other filters, leaving only TR-069 selected...it's messy and time consuming !

Cheers...

[Mkrtich]

Hi all - I spotted a comment on Whirlpool dated 16 October 2020 regarding Firmware Version 0.12.15r. Wondering if anyone has it in case it has stopped the unnecessary health check entries in the Log screen of the Arcadyan. Mine is still on 0.12.9r happily filling the Log with Thor checks.

[SteveW_52]

Mine is still on 0.12.09r, with the same useless log info..  but other than the log being chockablock, it doesn't seem to impact the modem performance (PMF issues have been the most common problems I have seen).

At my age I am well used to a surname starting with W means I am well towards the back off the line (which is handy sometimes).. 

I have seen mentions of 0.12.15r but no detail of change log, improvements etc. so far..

[TwoS1]

I would have expected more posts (both here and on Whirlpool) re getting the 0.12.15r update, but it has gone very quiet.

Perhaps this release has been put on hold as well.This Game Optimiser rollout seems to be a bit bumpy, especially when it comes to the Arcadyan variant of the SM2.

[Mkrtich]

Yes, I got the impression that the Game Optimiser option was going through a type of Beta trial with the Technicolor SM2 in October (dynamic changes made to the server from customer feedback in the Discussion Group) and the Arcadyan trial was scheduled to commence some time in November 2020.

I use to think that firmware updates rolled out in a formal structured manner on a quarterly basis, but recently I have seen a few instances in past forum posts where they appear to be happening sporadically with versions I have not seen before for both models. Perhaps a way of informally doing a Beta trial on new platforms as they are released and then correcting them if necessary which may explain why sometimes we get what a call a 'leapfrog' update, bypassing previous sequentially numbered versions.     

[TwoS1]

Ever since firmware 0.07.05r was rolled out in May 2019 (as part of the WiFi booster release), the displaying of active ethernet devices has been broken (incorrect and conflicting - even more frustrating was the changing and random nature of indicated active devices). Come 16 months and 5 firmware releases later, ver 0.12.09r is released, and fantastic this issue seems to have been fixed. Wired devices accurately and consistently showing correct status.

Then 0.12.15r gets released. While it has fixed some other issues (ie 15 second Thor(GW) log entries), it has unfortunately "unfixed" the active ethernet devices display - back to incorrect and changing status for wired devices.

Appreciated if this could be passed on to correct area in case they are not aware of the issue

Thanks

[SteveW_52]

0.12.15r also resets the PMF settings to Enabled by default..  

[TwoS1]

Still get the feeling Game optimiser for Arcadyan is not rolling out smoothly

There is one lonely post over on Whirlpool of someone getting firmware update to 0.13.01r about a fortnight ago, then silence.

cheers

[Mkrtich]

Hi - just some general observations that I found interesting from reading the Log in my Arcadyan 0.12.15r yesterday; it provides more information about what is going on inside than the Technicolor modems. I have not seen these before, but they may have always been resident since 0.12.15r was introduced.   

1. The modem checks into Telstra's Automatic Configuration Server (ACS) on a regular basis - in this snapshot, it does a 'Sending 6' command and sometimes a 'Sending 4' to get a different response from the ACS. To initiate a previous Firmware Update earlier in the year, the Log showed a 'Sending 3'. 

2. The Wi-Fi function has a Layer 2 Tunneling Protocol (L2TP) applied - perhaps for IPv6 initiated connection from 2.4Ghz Wi-Fi devices as two Profiles are shown?

3. A check is done on the Max number of Users on the 2.4Ghz band 

4. The modem enables its Device module for Telstra Location of Things (LOT) Server - Telstra Locator.

5. The modem is Enabled for NetDuma Game Optimiser and a Quality of Service (QoS) Shaping Rule 1 is applied for a possible priority for its application on the WAN. I have not activated Game Optimiser and that is OK as I know it is resident in background and available for activation for all users.   

Shaping Rule 1 is interesting as it implies others may exist for the WAN connection. 

20.12.2020 13:14:48 TR069: Sending 6 CONNECTION REQUEST inform to ACS: 2001:8006:3100:2100::1.
20.12.2020 13:14:48 TR069: Received InformResponse
20.12.2020 13:14:48 TR069: Received GetParameterValues
20.12.2020 13:14:49 TR069: Sending GetParameterValuesResponse
20.12.2020 13:14:49 TR069: Received GetParameterValues
20.12.2020 13:14:49 TR069: Sending GetParameterValuesResponse
20.12.2020 13:14:49 TR069: Received SetParameterValues
20.12.2020 13:14:49 TR069: Set Device.Services.X_TELSTRA_IWIFI.1.Enable success.
20.12.2020 13:14:49 TR069: Set Device.Services.X_TELSTRA_IWIFI.1.L2TP.MaxAuthUsers success.
20.12.2020 13:14:49 TR069: Set Device.Services.X_TELSTRA_IWIFI.1.Profile.1.CaptivePortal.IntegritySecret success.
20.12.2020 13:14:49 TR069: Set Device.Services.X_TELSTRA_IWIFI.1.L2TP.Server success.
20.12.2020 13:14:49 TR069: Set Device.Services.X_TELSTRA_IWIFI.1.Profile.1.Radio2G.SSID success.
20.12.2020 13:14:49 TR069: Set Device.Services.X_TELSTRA_IWIFI.1.Profile.2.Radio2G.MaxAssocUsers success.
20.12.2020 13:14:49 TR069: Set Device.Services.X_TELSTRA_IWIFI.1.Profile.2.Radio2G.SSID success.
20.12.2020 13:14:49 TR069: Set Device.Services.X_TELSTRA_IWIFI.1.L2TP.MaxPreAuthUsers success.
20.12.2020 13:14:49 TR069: Set Device.Services.X_TELSTRA_IWIFI.1.Profile.1.CaptivePortal.URL success.
20.12.2020 13:14:49 TR069: Set Device.Services.X_TELSTRA_IWIFI.1.Profile.1.Radio2G.MaxAssocUsers success.
20.12.2020 13:14:49 TR069: Set Device.Services.X_TELSTRA_IWIFI.1.Profile.2.CaptivePortal.URL success.
20.12.2020 13:14:49 TR069: Set Device.Services.X_TELSTRA_IWIFI.1.Profile.2.CaptivePortal.IntegritySecret success.
20.12.2020 13:14:49 TR069: Sending SetParameterValuesResponse
20.12.2020 13:14:49 TR069: Received SetParameterAttributes
20.12.2020 13:14:49 TR069: Sending SetParameterAttributesResponse
20.12.2020 13:14:49 TR069: Received SetParameterValues
20.12.2020 13:14:49 TR069: Set Device.Services.X_TELSTRA_LOT.Enable success.
20.12.2020 13:14:49 TR069: Set Device.Services.X_TELSTRA_LOT.ServerURL success.
20.12.2020 13:14:49 TR069: Set Device.Services.X_TELSTRA_LOT.Interval success.
20.12.2020 13:14:52 TR069: Sending SetParameterValuesResponse
20.12.2020 13:14:52 TR069: Received GetParameterNames
20.12.2020 13:14:53 TR069: Sending GetParameterNamesResponse
20.12.2020 13:14:53 TR069: Received SetParameterValues
20.12.2020 13:14:53 TR069: Set Device.Time.LocalTimeZone success.
20.12.2020 13:14:53 TR069: Set Device.Services.X_TELSTRA_DumaOS.Enable success.
20.12.2020 13:14:53 TR069: Set Device.QoS.Shaper.1.ShapingRate success.
20.12.2020 13:14:53 TR069: Sending SetParameterValuesResponse
20.12.2020 13:14:53 TR069: Received GetParameterValues
20.12.2020 13:14:53 TR069: Sending GetParameterValuesResponse
20.12.2020 13:14:53 TR069: Received SetParameterAttributes
20.12.2020 13:14:53 TR069: Sending SetParameterAttributesResponse
20.12.2020 13:14:53 TR069: Received SetParameterValues

[Yastiandrie]

@Mkrtich QoS.Shaper.1 is the upstream/upload bandwidth throttle amount

On NBN it is set to the upload speed for your speed tier so you don't go over your speed and end up with dropped packets due to the NBN policer

[Mkrtich]

Hello Yastiandrie - Greetings for the New Year and thanks for the information. There is a lot happening inside these humble looking modems. I don't think a lot of people realise or appreciate how advanced they are with AI. 

On my behalf, may I ask if it is possible for you to pass on to the Product Managers, a contribution to a wish list of additional functionality and enhancement considerations for future releases for both modems.

1. Firmware Upgrade Notification Icon Available in GUI and manual selection by user for a download to commence. If this is not feasible due to security reasons, can that action reserve a request for the Telstra ACS to do a 'push upgrade' it in its next cycle.  A roll back feature would also assist if new version has issues. 

2. Allow existing Gen 1.1 and Gen 2 modems be able to act as remote fully integrated EasyMesh Wi-Fi Boosters - they currently have Controller and Agent software however are limited to act as the Controller only. It is not unusual for people to have acquired multiple modem units for various reasons. This would provide more functionality than the current Wi-Fi Booster Gen 2 i.e additional LAN ports and better 5 Ghz connectivity speeds with simplified user asset management and allow people to re-use spare or used equipment rather than dispose it. This will also benefit customers in the future whenever Telstra release a Gen 3 model allowing users to extend the life of their existing investments rather than replacing them with non Telstra product. 

I think the Wi-Fi Booster Gen 2 is an excellent and competent solution for many users. I am not suggesting it is to be replaced by a Gen 2 modem but having the modem used as an alternative would provide a practical and effective choice for other customers. EasyMesh was created for open interconnectivity, so one would expect it to work between modems made by the same company. I note Netgear has recently released support for EasyMesh in their product line up.   

3. Next hardware update to existing Gen 2 modems - provide LEDs on LAN and WAN ports. The Arcadyan AW:1000 has them - I assume they were left out of Gen 2 modems for cost reasons. 

[Yastiandrie]

Point 1 would be a no-go for many, many reasons

[Mkrtich]

Another suggestion for future firmware releases and an observation query -

1. Could the Help menus be updated to show current firmware features. Example - SAMBA page shows no SMBv2 configuration user guide. The screen in the modem has a hidden feature which is not logical - once credentials are assigned, they are hidden to the owner for no advantage. You have to turn the SMBv2 OFF first then ON again to edit the fields for a new USB drive entry - someone must have written code for that. 

2. Since 0.11.11r, the Arcadyan appears to be unable to be used as an Access Point - LAN to LAN same subnet configuration. With DHCP Server OFF, on 0.12.15r , I couldn't allocate a different IP address to the Arcadyan for it to fit into the Primary modem's IP address range. Is this a Bug or by Design?   

[cf4]

When trying to set up the new IP address for the modem did you change the DHCP IP address range to match the new address range. The start DHCP IP address or end DHCP IP address must also be change so the modem's new IP address is not within the address range of modem.

[Mkrtich]

Yes, it's a strange phenomena worthy of an X-Files episode It is as if the Arcadyan DHCP Server is locked down and can not be Disabled - hence the question to Yastiandrie. I can change the modem's IP address and its DHCP addressing range but if I attempt to Disable DHCP it, doesn't allow it. Yesterday thinking DHCPv6 may semi lock it down the function, I disabled that as well but no success with DHCPv4.

Thinking I may had have testing fatigue yesterday, I factory reset the modem again this morning after your email and got the same results. I seem to recall a post on some modem from last year that it matters in which order you do the changes - I did the modem's IP address then Disabled the DHCP server and I also did Disable DHCP Server first and then change addressing - both with same result. I am not good on detail as you know, so I may have missed something. 

Test-TCH modem is 192.168.10.1 with range 192.168.10.2 to 192.168.10.254

Test-ARC modem is 192.168.20.1 with range 192.168.20.2 to 192.168.20.254

Maybe I have chosen hidden ranges that modem uses for other functions

Changing Test-ARC from 192.168.20.1 to 192.168.10.50 to fit into 192.168.10.2-192.168.10.254 Error

This makes me think a LAN to LAN same subnet Access Point is not possible - have you successfully configured one?

Changing Test-ARC from 192.168.20.1 to 192.168.10.50 with no range specified Error

Changing Test-ARC from 192.168.20.1 to no IP address specified in case Test-TCH auto allocates address later on connection Error

[cf4]

The error in the first image is due the Start DHCP address being lower than the local Device IP address. Change DHCP start to 192.168.10.51 and it should work.

Error in second image is due to DHCP start address and DHCP end address being blank.

Error in third image is due to Local Device IP address being left as blank.

[Mkrtich]

Thanks cf4 - will try it out and see what happens with further testing of possible LAN and Wi-Fi restrictions or access conflicts in Access Point mode.

I didn't realise the nuance about it having to set the Test-ARC A/P to be outside the allottable IP pool range of the primary Test-TCH modem. For separate subnets I usually start the pool range of the primary modem to be from 192.168.0.10 to allow some static IP addresses for some connections on 192.168.0.02 to 192.168.0.08 - didn't think to apply the same principle to a same subnet configuration as I thought all would be comfortable within the allottable pool range. 

[RobWA]

Hi,

Arcadyan LH1000 running 0.12.15r firmware. 

Log filling with junk about re-scanning 2.4 and 5GHz wifi (photo). Had a similar issue (not wifi) with an earlier firmware version.

However both 2.4 and 5 not enabled / turned off. Only ethernet enabled.

Questions: First: why is this happening? and

                  Second:  what is the memory device type (eg NAND flash?) in these modems and is this unnecessary writing of junk wearing out the write counts to the extent that if this is a widespread issue is there a risk of an 'avalanche' of requests for modem replacements?

Cheers.

[Mkrtich]

Hi - not sure, maybe when memory fills, it knocks off oldest records. Wi-Fi Doctor usually visits my modem daily , has a look around and then disappears - my Arcadyan Wi-Fi is ON and I don't have may Wi-Fi devices connected at the same time - maybe 6 or so. VoIP registrations occur every 10 minutes. 

17.01.2021 23:36:40 WiFi Dr.: ACS period timer trigger 2.4GHz rescan immediately.
17.01.2021 23:36:40 WiFi Dr.: ACS period timer trigger 5GHz rescan in 5 seconds.
17.01.2021 23:36:59 WLAN: stop AirIQ
17.01.2021 23:37:04 WLAN: 2.4GHz radio on
17.01.2021 23:37:04 WLAN: 5GHz radio on

[cf4]

This might be happening if modem can't communicate with maintenance server. Are there any TR-069 errors (ACS connection failed with error code 401).

With WiFi turned off on my LH1000 I only see these two events and then modem contacts maintenance server.

21.01.2021 14:47:04 WiFi Dr.: System boot trigger 2.4GHz rescan immediately.
21.01.2021 14:47:06 WiFi Dr.: System boot trigger 5GHz rescan in 5 seconds.
21.01.2021 14:47:22 WiFi Dr.: System boot trigger 2.4GHz rescan immediately.
21.01.2021 14:47:22 WiFi Dr.: System boot trigger 5GHz rescan in 5 seconds.

[RobWA]

Hi,
Thank you the quick response and the wifi off experiment.

No, there are no TR-069 errors (ACS connection failed with error code 401). (The log is from 3 January to now.)

The WiFi Dr occurs around 0208 hours daily as shown in the last two log extracts below.

Do the following extracts from the last two WiFi Dr have any significance?

1. 20.01.2021 02:08:54 health check [arc_wifidr_agent] disable or not exist
20.01.2021 02:08:54 health check detect case (ThorGW)

2. 21.01.2021 02:09:15 health check [arc_wifidr_agent] init or restart

20.01.2021 02:08:04 WiFi Dr.: System boot trigger 2.4GHz rescan immediately.
20.01.2021 02:08:04 WiFi Dr.: System boot trigger 5GHz rescan in 5 seconds.
20.01.2021 02:08:54 health check [ThorGW] init or restart
20.01.2021 02:08:54 health check [arc_wifidr_agent] disable or not exist
20.01.2021 02:08:54 health check detect case (ThorGW)
20.01.2021 02:08:57 WiFi Dr.: System boot trigger 2.4GHz rescan immediately.
20.01.2021 02:08:57 WiFi Dr.: System boot trigger 5GHz rescan in 5 seconds.
20.01.2021 02:09:00 health check case (SIP LOG)
20.01.2021 02:09:50 WiFi Dr.: System boot trigger 2.4GHz rescan immediately.
20.01.2021 02:09:50 WiFi Dr.: System boot trigger 5GHz rescan in 5 seconds.

21.01.2021 02:09:13 WiFi Dr.: System boot trigger 2.4GHz rescan immediately.
21.01.2021 02:09:13 WiFi Dr.: System boot trigger 5GHz rescan in 5 seconds.
21.01.2021 02:09:15 health check [ThorGW] init or restart
21.01.2021 02:09:15 health check [arc_wifidr_agent] init or restart
21.01.2021 02:09:15 health check detect case (ThorGW)
21.01.2021 02:09:20 health check case (SIP LOG)
21.01.2021 02:10:06 WiFi Dr.: System boot trigger 2.4GHz rescan immediately.
21.01.2021 02:10:06 WiFi Dr.: System boot trigger 5GHz rescan in 5 seconds.

Cheers.

[RobWA]

Hi,

Thank you for the reply.

Re RAM type. Yastiandrie (March 2019) indicated the modem has 512MB RAM. 

My best guess is that this is eMCC type with maybe 3000 P/E cycles before failure(?)).

Cheers

[cf4]

I don't have any "20.01.2021 02:08:54 health check [arc_wifidr_agent] disable or not exist" in my log file so it could be significant. As to what it means I have no idea.

Did you turn WIfi off using WiFi button on back of the modem or the Wi-Fi Radio Tab in the modem's WiFi settings?

Did the .events below start as soon as you turned WiFi off or did they take several hours to start filling the log?

21.01.2021 02:10:06 WiFi Dr.: System boot trigger 2.4GHz rescan immediately.
21.01.2021 02:10:06 WiFi Dr.: System boot trigger 5GHz rescan in 5 seconds.

[RobWA]

Hi,

Wifi turned off using GUI and this was done on installation years ago.

Current log starts 3 January (16 days at ~ 0.3Mb per day) and we do not know when this started.  Our best guess is possibly when the firmware was last updated. 

[Mkrtich]

Hi - are you concerned about the modem's Log filling up with those System boot triggers on 2.4Ghz and 5Ghz radios - I take it the modem is not resetting itself when they happen. If feasible in your situation, have you considered doing a factory reset to see if things settle and then turn OFF Wi-Fi to see if these log entries continue.

There are two types of memory inside the Arcadyan - the System RAM and then the Flash Memory which holds the modem's firmware and Log information which survives a system reset and factory reset. Various figures are quoted for memory size, so I am not sure of the actual sizing of both modules as some posts mix up the memory types. This is what was inside an Acradyan modem that I looked into last year.

1. RAM - SEC7y6 - the 'y' is in Ukrainian Cyrillic, followed by two codes words in the same language followed by E712980EC

2. Toshiba Flash Memory - LJ2902 Taiwan 18199AE TC58BVG20HT-ADD. 

I have not been able to identify specifications for both chip modules with web searches, so the type of NAND used in the Flash Memory is unknown.

[RobWA]

Hi,

Thank you for the detailed reply and suggestion.

A power cycle of the modem seems to have cleared the log of the wifi rescans.  Will check again later to see if this has been maintained. 

[cf4]

Any one know which firmware added the "Mobile Only mode" option in the Modem's LTE settings?

[Mkrtich]

Hi - I don't recall seeing it in 0.12.15r but may have overlooked it. An unconfirmed Whirlpool post refers to it as a new selection for the DJA0230 in late October 2020 when 18.1c.0549-MR17-RB was released. DJA0231 18.1c 0585-MR7.1-RA also features Mobile Only mode and not sure if it was there in previous Technicolor versions, so perhaps a catch up for the Arcadyan to make all modems the same. 

[cf4]

It is a recent edition to the Technicolor modems. I have not noticed it before. Perhaps Telstra has added the option to make it easier to test 4G backup or to enable customers to switch to 4G backup when there is an intermittent fault on the main link.

[Mkrtich]

Yes, in addition to some testing advantages, it also provides greater flexibility for those customers who just want to have a reliable Mobile Broadband Home service using 4G LTE without an ADSL or NBN landline and given the modem is not locked, it's a reasonable solution for some customers albeit at CAT4 and CAT 6  LTE speeds. 

[Mkrtich]

@cf4  just confirming - I forgot that my test ARC modem is still on 0.12.15r and it doesn't have 'Mobile Mode Only', so it has been introduced in 0.13.01r.