Kong 24500M Problem

5 posts / 0 new
Last post
GAHelm
GAHelm's picture
Kong 24500M Problem

Tried the new 24500M on my R6300v2 today.  No luck, I found two things wrong with it.

1st - I cant get IPv6 to work on it, period.  My network locks up and I have to reboot the router to get back in and disable the IPv6 option.  On a couple of occasions I could keep the connection to the router but could not reach the internet beyond.

 

2nd - When trying to roll back to the Netgear firmware the router kept saying "Upgrade Failed" and would not accept the Netgear .CHK file.  I tried several times all the while rebooting, clearing my cache etc...  Was about to give up when I decided to roll back to a previous Kong version 24345M, I was able to roll back to the previous 24345M and THEN roll back to the latest Netgear .CHK file.  It appears that there is something not quite right with the 24500M firmware in that it will not let you roll back to the Netgear .CHK file.

As an aside I have been unable to get IPv6 working with the 24345M file as well.  If anyone can tell me how to get ATT Uverse IPv6 running on DD-WRT I would appreciate it.  With the latest Netgear firmware all I have to do is turn on Autodetect and it puts the router in "Pass through" mode for IPv6 and all the IPv6 test sites work.

Venturis
Venturis's picture
I also tried the 24500 build

I also tried the 24500 build today on my R7000 and had some issues that forced me to roll back to 24200M.

 

1. Could not access wifi through the 5GHz radio after the update.  Using the same wifi settings as had been working on 24200M build I could not even see the AP from my PC.  Tried using SSIDider to see what was happening and nothing showed up under the 5Ghz range.

Tried rebooting the router a couple times and changing the channel which allowed me to at least see the AP but I would get an error when trying to connect.

2. I tried rolling back to 24200M using the firware update page a got a "failed" update at least twice.  Tried to clear the nvram and still no success.  One hard reset later (power down/up) and finally able to roll back to 24200M

3. On the status page the WL0 CPU temperature reading was corrupted.  Showing temperature of 80897999.00 or something like that.

I'm using a Netgear A6200 on my laptop client.  I've had lots of trouble with being unable to connect or even see the 5GHz radio with some combinations of channel and sideband and in some cases had to power down/up the router to have the new channel setting take effect.  This is still the case with 24200M firmware.  Almost seemed like there are some combinations of channel/sideband that can be set however are unable to be used.

Kong
Kong's picture
 

 

Venturis said: I also tried the 24500 build today on my R7000 and had some issues that forced me to roll back to 24200M. 1. Could not access wifi through the 5GHz radio after the update.  Using the same wifi settings as had been working on 24200M build I could not even see the AP from my PC.  Tried using SSIDider to see what was happening and nothing showed up under the 5Ghz range. Tried rebooting the router a couple times and changing the channel which allowed me to at least see the AP but I would get an error when trying to connect. 2. I tried rolling back to 24200M using the firware update page a got a "failed" update at least twice.  Tried to clear the nvram and still no success.  One hard reset later (power down/up) and finally able to roll back to 24200M 3. On the status page the WL0 CPU temperature reading was corrupted.  Showing temperature of 80897999.00 or something like that. I'm using a Netgear A6200 on my laptop client.  I've had lots of trouble with being unable to connect or even see the 5GHz radio with some combinations of channel and sideband and in some cases had to power down/up the router to have the new channel setting take effect.  This is still the case with 24200M firmware.  Almost seemed like there are some combinations of channel/sideband that can be set however are unable to be used.

The issue with the A6200 is, that the driver does not allow you to use higher channels, since it doesn't support dfs. As far as I know netgear has already released a beta driver that allows to use upper channels.

 

If it tells you that the upgrade failed, then your browser did not completely send the firmware, I have seen this before, I just clear my browser cache close the browser and start it, after that it works fine.

 

The temperature bug is a broadcom bug and has been there also with old builds.

 

Regarding IPV6, you should wait to see if the guys over at the dd-wrt forum fix it with the new build or until I roll the first test builds which come with improved ipv6 support.

 

Venturis
Venturis's picture
 

 

Kong said:

Venturis said: I also tried the 24500 build today on my R7000 and had some issues that forced me to roll back to 24200M. 1. Could not access wifi through the 5GHz radio after the update.  Using the same wifi settings as had been working on 24200M build I could not even see the AP from my PC.  Tried using SSIDider to see what was happening and nothing showed up under the 5Ghz range. Tried rebooting the router a couple times and changing the channel which allowed me to at least see the AP but I would get an error when trying to connect. 2. I tried rolling back to 24200M using the firware update page a got a "failed" update at least twice.  Tried to clear the nvram and still no success.  One hard reset later (power down/up) and finally able to roll back to 24200M 3. On the status page the WL0 CPU temperature reading was corrupted.  Showing temperature of 80897999.00 or something like that. I'm using a Netgear A6200 on my laptop client.  I've had lots of trouble with being unable to connect or even see the 5GHz radio with some combinations of channel and sideband and in some cases had to power down/up the router to have the new channel setting take effect.  This is still the case with 24200M firmware.  Almost seemed like there are some combinations of channel/sideband that can be set however are unable to be used.

The issue with the A6200 is, that the driver does not allow you to use higher channels, since it doesn't support dfs. As far as I know netgear has already released a beta driver that allows to use upper channels. If it tells you that the upgrade failed, then your browser did not completely send the firmware, I have seen this before, I just clear my browser cache close the browser and start it, after that it works fine. The temperature bug is a broadcom bug and has been there also with old builds. Regarding IPV6, you should wait to see if the guys over at the dd-wrt forum fix it with the new build or until I roll the first test builds which come with improved ipv6 support.

 

Ok....I have to eat my words again...

With Kong's reassurance that the problem was mine I wiped the R7000 nvram and proceeded to install the 24500-UDHCPC6 build.

I also grabbed the beta A6200 drivers from Netgear's Ftp site as suggested by Kong.

This time the firmware installed smoothly and even the WL0 temperature is now reporting correctly.

No problems setting channel 157 for the 5GHz radio as I had previously with build 24200M.

Loaded all the settings again from scatch rather that using a previously saved config just to be sure.

All up and running now.  Will report back if I have any issues.

Before I forget...it looks like the NEWD and OLDD versions are no longer available so from now on can we expect only the new broadcom driver is used?

Thanks Kong.

zhrtc
zhrtc's picture
 

 

Kong said:

Venturis said: I also tried the 24500 build today on my R7000 and had some issues that forced me to roll back to 24200M. 1. Could not access wifi through the 5GHz radio after the update.  Using the same wifi settings as had been working on 24200M build I could not even see the AP from my PC.  Tried using SSIDider to see what was happening and nothing showed up under the 5Ghz range. Tried rebooting the router a couple times and changing the channel which allowed me to at least see the AP but I would get an error when trying to connect. 2. I tried rolling back to 24200M using the firware update page a got a "failed" update at least twice.  Tried to clear the nvram and still no success.  One hard reset later (power down/up) and finally able to roll back to 24200M 3. On the status page the WL0 CPU temperature reading was corrupted.  Showing temperature of 80897999.00 or something like that. I'm using a Netgear A6200 on my laptop client.  I've had lots of trouble with being unable to connect or even see the 5GHz radio with some combinations of channel and sideband and in some cases had to power down/up the router to have the new channel setting take effect.  This is still the case with 24200M firmware.  Almost seemed like there are some combinations of channel/sideband that can be set however are unable to be used.

The issue with the A6200 is, that the driver does not allow you to use higher channels, since it doesn't support dfs. As far as I know netgear has already released a beta driver that allows to use upper channels. If it tells you that the upgrade failed, then your browser did not completely send the firmware, I have seen this before, I just clear my browser cache close the browser and start it, after that it works fine. The temperature bug is a broadcom bug and has been there also with old builds. Regarding IPV6, you should wait to see if the guys over at the dd-wrt forum fix it with the new build or until I roll the first test builds which come with improved ipv6 support.

 

I also tried to upgrade my router's firmware from 24200M to build 24710 and 24500 today and encontered the same problem which is "Could not access wifi through the 5GHz radio after the update". My router model is Netgear R6300v2.

In addition, the "OpenVPN" service does't work either. I have already tried 30-30-30 reset procedure and set the 5G channel to be 149 or 157, nothing helped.

At last when I want to roll back to the official firmware from build 24710 the upgrade page continue to show "upgrade failed". I have to degrade to 24200M first then roll back to the official firmware.

I would appreciate it if anyone can tell me what happened to my router and help me solve this problem.