|
#1
|
|||
|
|||
|
You can now download WNDR4000 firmware v1.0.0.90 from the Netgear Download Center here:
http://downloadcenter.netgear.com/en/product/WNDR4000 As always, it is highly recommended to perform the firmware update wired to the router and not over a wireless connection. Bug Fixes and Enhancements:
Known Issues:
|
|
#2
|
|||
|
|||
|
New firmware with the same bugs like in V1.0.0.88_9.1.77 I described earlier:
1. There is a "Gateway IP Address" setting available in "Enable AP mode" section. But anyway there is still no internet connection and access to the wireless-router over internet-router is also miss. 2. If we firstly disable one of the wireless frequencies (2.4GHz or 5 GHz) via web and after disable/enable WiFi with the help of "WiFi on/off button" all wireless frequencies become to active again regardless of previous settings. |
|
#3
|
|||
|
|||
|
I am not a fan of the WNDR4000. Even when it first came out it used an old chipset. I would never buy it. I was just posting to let ppl know where is a firmware update. I'm waiting for the new N750 model which should be out by the end of the year which is based on a Atheros better chip VS the WNDR4000 Broadcom chip.
In regards to your concern, #1 if you google Netgear AP Mode you will find how to get that type of setup working. It can be a head banger sometimes. It just takes trial and error. As for #2, that "issue" exists in all Netgear models (and other brand dual band routers) that have the physical on/off button. It really is not an "issue" as there is no way in the coding of the firmware to have it work like you want it too w/ dual band radio models. Last edited by Mars Mug; August 6th, 2012 at 11:10 PM. |
|
#4
|
|||
|
|||
|
After this new firmware the wireless turned rubish. Constant failing, but when using cable: No problems. It was stable until i loaded shitty 1.0.0.90 on my router. I did a master reset (30/30/30) before AND after update. I'm using WPA2 AES encryption, and none of my neighbours are using the same wireless channel as me. And the failing happens on both 2.4GHz and 5GHz.
|
|
#5
|
|||
|
|||
|
havent seen any wireless failing after upgrading here. Have copied GB's of data back and forth both wireless and wired......
|
|
#6
|
|||
|
|||
|
I am still at version V1.0.0.82_8.0.71
From what I have read here in these forums this is about the most stable version and I understand the new interface is awful. Any comments? |
|
#7
|
|||
|
|||
|
The new Interface for the configuration page requires familiarization. You will just need to get used to its more graphical presentation. I have tried the wireless scheduling, and it works fine. Make sure that you set the correct time zone on your area.
|
|
#8
|
|||
|
|||
|
Bug sighting:
If I disable the SSID broadcast Name for the 5G under the 'wireless settings', it shows as the 2.4G Broadcast Name disabled under the advanced home screen. The 5G Broadcast Name shows as 'On'.
|
|
#9
|
|||
|
|||
|
I'm of the mind that "if it isn't broken don't fix it". I'm just not sure what benefit there is to upgrading when with every upgrade there seems to be a new suite of bugs introduced.
I see you seem to be OK with the interface but I've read some not so nice comments about it here. |
|
#10
|
|||
|
|||
|
Ok, I've finally reverted back to 1.0.0.82 after struggling with wireless performance on .88 and .90 for 2.4GHz. I was actually getting better speeds over my 3G connection if the router was up for more than 1 day. Wired connections worked perfectly with all of the firmware versions above.
I wish it was possible to send diagnostic information back on demand, because I'm sure it is tough to try and debug these things without real-world data. -Dave |
![]() |
| Thread Tools | |
| Display Modes | |
|
|