Reply

R7000 1.0.9.26 Feedback Thread

R7000 1.0.9.26 Feedback Thread

Updated from 1.0.7_1.1.99 > 1.0.9.26_10.2.31 - R7000

 

Current bandwidth 300 / 12 (comcast)

 

Verdict: Immediately lost 50% of my downstream bandwidth

 

I went through every single page and menu option.  Having owned this router for years, I know every inch of its GUI.  I went into QoS and enabled it, downloaded the newest definitions file (dated 7/23/17) -For Christ sakes Netgear- saved and rebooted. Still at 50% of previous downstream bandwidth. Disabled QoS / WMM all together and rebooted, no change.

 

I then tried manually defining bandwidth, saving, rebooting and testing after each change. Rebooted the cable modem as well, multiple times with the same results. Best I could get was 165 down. The speed test in the router said 214 down, but I never saw that.

 

Then I reset the router to defaults... just tested wired bandwidth. SAME results, only 50% of previous downstream bandwidth.

 

ok... Let's be extra thorough.. reflash 1.0.9.26... which blows away the downloaded QoS configuration whether you have it enabled or disabled.... now its back to being blank - SAME results (50% of downstream).

 

***Connect directly to cable modem - get 300 / 12
 
Have about 43 minutes invested into this "upgrade" now. Have restarted at least 20 times.

 

Next step. flash back to 1.0.7... reapply config file. Retest downstream / upstream bandwidth.

 

301 Down / 12 Up

 

Your results may vary.  I never bothered checking wireless device performance as wired performance is paramount for my work.  Sticking with 1.0.7.. for the foreseeable future. Don't have the time to mess with this.

 

Observations:

I have seen QoS wreak havoc on previous versions of FW, but have always been able to overcome them by disabling it and WMM.  Not this time.  Disappointed, but only wasted 50 min of my time. Still waiting for something better to upgrade to.  Will try again the next release.  Am 100% stable where I'm at for now.

 

** Not looking for any assistance,  and please don't bother telling me about how great vortex or tomato FW is...  Just posting my experiencing with Netgear's latest release.  YMMV.

 

~Comcast 1 Gbps/50 Mbps SB8200 > R8000P
~R8000P FW:1.4.1.68 ~R7000 FW:1.0.9.42
~R6400 FW:1.0.1.52 ~Orbi-AC3000 FW:2.5.1.8
~EX3700 FW:1.0.0.84

Model: R7000|Nighthawk AC1900 Dual Band WiFi Router
Message 1 of 16
Donth
Aspirant

Re: R7000 1.0.9.26 Feedback Thread


@shadowsportswrote:

Updated from 1.0.7_1.1.99 > 1.0.9.26_10.2.31 - R7000

 

Current bandwidth 300 / 12 (comcast)

 

Verdict: Immediately lost 50% of my downstream bandwidth

 

I went through every single page and menu option.  Having owned this router for years, I know every inch of its GUI.  I went into QoS and enabled it, downloaded the newest definitions file (dated 7/23/17) -For Christ sakes Netgear- saved and rebooted. Still at 50% of previous downstream bandwidth. Disabled QoS / WMM all together and rebooted, no change.

 

I then tried manually defining bandwidth, saving, rebooting and testing after each change. Rebooted the cable modem as well, multiple times with the same results. Best I could get was 165 down. The speed test in the router said 214 down, but I never saw that.

 

Then I reset the router to defaults... just tested wired bandwidth. SAME results, only 50% of previous downstream bandwidth.

 

ok... Let's be extra thorough.. reflash 1.0.9.26... which blows away the downloaded QoS configuration whether you have it enabled or disabled.... now its back to being blank - SAME results (50% of downstream).

 

***Connect directly to cable modem - get 300 / 12
 
Have about 43 minutes invested into this "upgrade" now. Have restarted at least 20 times.

 

Next step. flash back to 1.0.7... reapply config file. Retest downstream / upstream bandwidth.

 

301 Down / 12 Up

 

Your results may vary.  I never bothered checking wireless device performance as wired performance is paramount for my work.  Sticking with 1.0.7.. for the foreseeable future. Don't have the time to mess with this.

 

Observations:

I have seen QoS wreak havoc on previous versions of FW, but have always been able to overcome them by disabling it and WMM.  Not this time.  Disappointed, but only wasted 50 min of my time. Still waiting for something better to upgrade to.  Will try again the next release.  Am 100% stable where I'm at for now.

 

** Not looking for any assistance,  and please don't bother telling me about how great vortex or tomato FW is...  Just posting my experiencing with Netgear's latest release.  YMMV.

 


Probably the stupidest question: Did you remember to set the computer to highest priority for QOS?  It's possible the chipset is having a problem keeping up with software updates.

Message 2 of 16

Re: R7000 1.0.9.26 Feedback Thread

QoS was disabled in the majority of my tests.  The same as it is now.

 

st.png 

 

 

~Comcast 1 Gbps/50 Mbps SB8200 > R8000P
~R8000P FW:1.4.1.68 ~R7000 FW:1.0.9.42
~R6400 FW:1.0.1.52 ~Orbi-AC3000 FW:2.5.1.8
~EX3700 FW:1.0.0.84

Message 3 of 16
FURRYe38
Guru

Re: R7000 1.0.9.26 Feedback Thread

It's recommended that you use 1.0.7_1.1.99. Seems to be an issue in recent FW versions. Hopefully will be corrected by NG.

 

You can leave feedback here as well:

https://community.netgear.com/t5/Nighthawk-WiFi-Routers/Feedback-for-R7000-New-firmware-1-0-9-18/td-...

 

My Setup (Cable 1Gbps/50Mbps)>CM1200 v2.02.03(LAG Disabled)>RBK853 v3.2.18.1/RBK50 v2.7.2.104(WW)
Additional NG HW: C7800/CM1100/CAX80/CM2000, Orbi CBK40, R7800, R7960P, EX7500/EX7700, XR450(v2.3.2.120) and WNHDE111
Message 4 of 16
tivoboy
Guide

Re: R7000 1.0.9.26 Feedback Thread

I couldn't get this working at all.  Had to roll back to a 1.07.12 I think.  It's definitely 1.07.xx.  

 

The crazy thing is, I cannot BELIEVE that the router can't adjust for DST last weekend? I mean, it knows the date and it's off by an hour now.  So, all scheduled programming is off.  Come ON!  We've had these DST change dates for several years now.

Message 5 of 16

Re: R7000 1.0.9.26 Feedback Thread


@FURRYe38wrote:

It's recommended that you use 1.0.7_1.1.99. Seems to be an issue in recent FW versions. Hopefully will be corrected by NG.

 

You can leave feedback here as well:

https://community.netgear.com/t5/Nighthawk-WiFi-Routers/Feedback-for-R7000-New-firmware-1-0-9-18/td-...

 

I left my feedback for 1.0.9.26 on the .18 release thread you referenced aboove for the benefit of others.  If you read that thread, however, you'll see that a mod asks that feedback for 1.0.9.26 should not be left on the 1.0.9.18 feedback thread and instead left in a new thread which is why I created this one.   

 

I'm running 1.0.7_1.1.99  (again) for years now actually because it's been the most stable for me.  I steered clear of 1.0.8 when released because all it did was introduce gatering telemetry data.  Although it could be disabled, I saw little value in upgrade.  It came and went, and 1.0.9.x was released.  Plagued from the start, I watched each iteration fail based on the feedback from others, but the release does include some valuable security fixes.  Unfortunately, the instability and issues which followed made spending any time upgrading a gamble.

 

A few weeks ago I took that gamble believing that netgear may have finally got it right in 1.0.9..26.  Well, they didn't.  Not for me anyway and I simply don't have the time.  I am not down on the brand.  I've been using Netgear products for years and have been a member on these forums since 2004.  They'll eventually get it right.  But for now, I'm sticking with whats tried and true.  1.0.7.x.  Hopefully the issues associated with 1.0.9.x will get resolved sooner rather than later, but this doesn't look promising based on this releases current history. 

 


 

~Comcast 1 Gbps/50 Mbps SB8200 > R8000P
~R8000P FW:1.4.1.68 ~R7000 FW:1.0.9.42
~R6400 FW:1.0.1.52 ~Orbi-AC3000 FW:2.5.1.8
~EX3700 FW:1.0.0.84

Message 6 of 16

Re: R7000 1.0.9.26 Feedback Thread


@tivoboywrote:

I couldn't get this working at all.  Had to roll back to a 1.07.12 I think.  It's definitely 1.07.xx.  

 

The crazy thing is, I cannot BELIEVE that the router can't adjust for DST last weekend? I mean, it knows the date and it's off by an hour now.  So, all scheduled programming is off.  Come ON!  We've had these DST change dates for several years now.


The clock works fine and adjusts for DST automatically.  I haven't touched mine for years.  Make sure you have your time zone set correctly.  Also check the device in front of your R7000 for correct settings if applicable. 

 

time.png

 

 

~Comcast 1 Gbps/50 Mbps SB8200 > R8000P
~R8000P FW:1.4.1.68 ~R7000 FW:1.0.9.42
~R6400 FW:1.0.1.52 ~Orbi-AC3000 FW:2.5.1.8
~EX3700 FW:1.0.0.84

Message 7 of 16
FURRYe38
Guru

Re: R7000 1.0.9.26 Feedback Thread

Good Luck.

 


@shadowsportswrote:

@FURRYe38wrote:

It's recommended that you use 1.0.7_1.1.99. Seems to be an issue in recent FW versions. Hopefully will be corrected by NG.

 

You can leave feedback here as well:

https://community.netgear.com/t5/Nighthawk-WiFi-Routers/Feedback-for-R7000-New-firmware-1-0-9-18/td-...

 

I left my feedback for 1.0.9.26 on the .18 release thread you referenced aboove for the benefit of others.  If you read that thread, however, you'll see that a mod asks that feedback for 1.0.9.26 should not be left on the 1.0.9.18 feedback thread and instead left in a new thread which is why I created this one.   

 

I'm running 1.0.7_1.1.99  (again) for years now actually because it's been the most stable for me.  I steered clear of 1.0.8 when released because all it did was introduce gatering telemetry data.  Although it could be disabled, I saw little value in upgrade.  It came and went, and 1.0.9.x was released.  Plagued from the start, I watched each iteration fail based on the feedback from others, but the release does include some valuable security fixes.  Unfortunately, the instability and issues which followed made spending any time upgrading a gamble.

 

A few weeks ago I took that gamble believing that netgear may have finally got it right in 1.0.9..26.  Well, they didn't.  Not for me anyway and I simply don't have the time.  I am not down on the brand.  I've been using Netgear products for years and have been a member on these forums since 2004.  They'll eventually get it right.  But for now, I'm sticking with whats tried and true.  1.0.7.x.  Hopefully the issues associated with 1.0.9.x will get resolved sooner rather than later, but this doesn't look promising based on this releases current history. 

 


 


 

My Setup (Cable 1Gbps/50Mbps)>CM1200 v2.02.03(LAG Disabled)>RBK853 v3.2.18.1/RBK50 v2.7.2.104(WW)
Additional NG HW: C7800/CM1100/CAX80/CM2000, Orbi CBK40, R7800, R7960P, EX7500/EX7700, XR450(v2.3.2.120) and WNHDE111
Message 8 of 16
rjenk
Initiate

Re: R7000 1.0.9.26 Feedback Thread

Continue to have issues with Wi-Fi and management console locking up.  Router will still respond to pings and wired connections will pass through.  Wi-Fi connected devices show they are connected, but they cannot communicate.  Neither wired or wireless devices can connect to the managment web interface.  The only way to correct is to power cycle the router.  Only had it for three months and I routinely have to reboot it every couple of weeks.

Model: R7000|Nighthawk AC1900 Dual Band WiFi Router
Message 9 of 16
HiSpeed
Guide

Re: R7000 1.0.9.26 Feedback Thread

I still use v1.0.7.6_1.1.99 and everything works fine !

 

Man Happy

 

● Netgear R7000 (Root Router)
● TP-Link Archer C7 v2 (WDS Bridge)


Message 10 of 16

Re: R7000 1.0.9.26 Feedback Thread


@HiSpeedwrote:

I still use v1.0.7.6_1.1.99 and everything works fine !

Man Happy

 

***********

 

Agree.  Has truly been one of the best FW's availble for this router. 

 

 

 


 

~Comcast 1 Gbps/50 Mbps SB8200 > R8000P
~R8000P FW:1.4.1.68 ~R7000 FW:1.0.9.42
~R6400 FW:1.0.1.52 ~Orbi-AC3000 FW:2.5.1.8
~EX3700 FW:1.0.0.84

Message 11 of 16
pkaytes
Guide

Re: R7000 1.0.9.26 Feedback Thread

Since installing 1.0.9.26, after about 7 days router no longer responds to DNS requests from any client (wired or wireless) and one gets no response from the routers web interface either. Devices can ping each other and the router itself but any request that results in a DNS lookup (web browsing, email, etc, presuming automatic DNS configuration via DHCP) fails. The only resolution is to power cycle the router.

 

I would like to see this fixed but know better than to hold my breath!

Message 12 of 16
samman
Tutor

Re: R7000 1.0.9.26 Feedback Thread

1.0.9.26_10.2.31 Firmware breaks connection to my 5G clients that use 

IttimTec ITTIM Technologies chips

I downgraded back down to 1.0.9.14 and it works again.

 

Message 13 of 16
shamarin
Virtuoso

Re: R7000 1.0.9.26 Feedback Thread

Did you try a newer version 1.0.9.28?

Message 14 of 16
samman
Tutor

Re: R7000 1.0.9.26 Feedback Thread

The Netgear Genie app pointed to 1.0.9.26 but just tried 10.9.28 manually and same problem.

Model: R7000|Nighthawk AC1900 Dual Band WiFi Router
Message 15 of 16

Re: R7000 1.0.9.26 Feedback Thread

Thanks for the feedback. 

Also noted that x.028 introduces > Auto Firmware upgrade

This is a horrible feature unless it can be disabled.  There is nothing worse than being stable, and having your FW upgraded for you without your knowledge or consent.    

 

The Orbi's do this as well, until you manually flash which I've read arrests the "feature".  But you have to watch for it and catch it before it happens.  Its the surprise (headache) no one wants or needs.

 

Still waiting for a solid release.

 

 

 

~Comcast 1 Gbps/50 Mbps SB8200 > R8000P
~R8000P FW:1.4.1.68 ~R7000 FW:1.0.9.42
~R6400 FW:1.0.1.52 ~Orbi-AC3000 FW:2.5.1.8
~EX3700 FW:1.0.0.84

Model: R7000|Nighthawk AC1900 Dual Band WiFi Router
Message 16 of 16
Top Contributors
Discussion stats
  • 15 replies
  • 6040 views
  • 2 kudos
  • 9 in conversation
Announcements