Installed 9.13.1.2 - initial results (positive)

2 hours in, my iPad Pro 2024 has dropped IPv6. First bug.

Yeah this is a fail. I can’t get the iPad to reconnect on IPv6. I have tried stopping and starting Wi-Fi, hard reset of the iPad, and even a forget and rejoin at the network. In settings, it shows no router for IPv6.

I am disabling IPv6 on the router again. One of six tests is a fail.

 I just went in and tested my iPhone, which has just been sitting on my desk. It has no IPv6 connection now either. This is no better, it may even be worse than before. It didn’t usually fail this quickly.

It's early to declare victory, but in 3 days I have not had any memory creep situation on the 970s (which ends up in a crash/restart), or restarts independent of memory creep (which I have seen). I only had 1 flip to cellular 5G less than about 4 hours after upgrading to 9.13.1.2, but that was when I was testing IPv6, which is NOT ready for prime time (Netgear knows and is working on this) - so I disabled it. 

I did a power-cycle after disabling IPv6, and no flips to 5G cellular in 2 days. Memory creep can take up to 2-3 weeks to show up, but if I go 2 weeks with no flips to cellular/loss of WiFi in the house I would say they nailed it. This FW is solid otherwise for me - streaming, speed, latency, packet loss all perfect. Here is a mid-afternoon workday zoom call latency/pkt loss tracking result:
 
 
 

I am 9 days in. Things seem better with this version of firmware, but there is work to do on the four major issues I have suffered from. I have power cycled but have not done a full factory reset. 

Summary so far:

1. IPv6 - as noted above - had to disable, not working on Apple iPhone and iPad;
2. Flips to cellular when on WiFi - I have had 2 occurrences of this, the first was day two and the second was day 8, so the frequency is much less so far - plus I have been testing and looking for this.
3. Memory creep on Orbis - nothing obvious so far, but I am starting to get suspicious of one satellite 970 (which is the one that crashed, see below) - it has slowly moved from ~605MB used to 630MB. I only check it once a day and mem usage jumps around, but this will become obvious or not in the next 2 weeks.
4. Restarts due to crashes - one unfortunately. I sent the logs in. According to the logs the restart happened overnight about 4 days ago, a kernel panic crash.

Question: 

What method are you using to determine memory creep? also how do you determine whether a crash was caused by memory leak? thanks for the eductation...m 

BedfordHome​ I am just checking it on the router and satellite debug pages once a day to get a basic trend. We have a utility that signs in, scrapes the debug page, and outputs the result - but I didn't want to introduce anything external to the monitoring process with new firmware.

As for the restart - I ran a debug log from the router debug page - you get a zip file - expand it, there is a reason file in text along with a ton of other cryptic info. The reason file said "Kernel Panic crash" or something similar. While I do not know if that crash is due to memory creep, I have seen ones where, monitoring daily, the memory slowly grows from 600MB used to almost 800MB, and then I see a restart the next morning. It could be unrelated, it could just be some buffer being overwritten; that's why I report the memory creep and crashes separately for now.

I've had my 970 series (router + 2 satellites) up on 9.13.1.2 for 15 days now.

No sign of memory creep on the router nor either satellite.   No crashes/unexpected restarts.

Please note that I am running with both satellites connected wirelessly, IPv6 disabled, and I have no Apple devices.  

CPU Usage on router remains under 5%, with CPU usage on Sat 1 sits between 11.3 - 11.5%, while Sat 2 sits between 8.7% to 8.9%.  Both sats are connected using 5GHz+6GHz (WiFi7 MLO) bands.

Well apart from my google devices loosing internet a few times per day everything else seems ok so far my fingers are still cross