I am a total newb (first post). I am running 19342 on WDNR3700v1 having upgraded from Netgear firmware four days ago. So far so good and all seems to be working well. No problems on installation. I didn't need to do a 30/30/30 , as it was working properly, hope this is not storing up any problems.
Rev 19342, WNDR3700v2. Noticed problems with external HDD. The device is properly mounted but I can't get access to any file. Console halts when I'm trying to do LS operation. Resources are not available via samba protocol.
Switched back to 17210 and NAS works fine. Sometimes built in dd-wrt HTTP server colapses. It accepts new connections and HTTP requests but returns nothing :/
I'm also using the latest version (DD-WRT v24-sp2 (06/08/12) std - build 19342) on a WNDR3700v1 and has been doing so for a couple of weeks, no problems here.
Good luck!
pptp and open vpn not working! dunno why.
i now want to "downgrade" to earlier firmware.
currently i have v24-sp2 build 19342. (Atheros AR7161 rev 2)
what is the best method to downgrade to V24-preSP2/2012/03-08-12-r18767 ?
try webflash or better restore to stock firmware and then install the factory.img ?
I'm also using the latest version (DD-WRT v24-sp2 (06/08/12) std - build 19342) on a WNDR3700v1 and has been doing so for a couple of weeks, no problems here.
Good luck!
pptp and open vpn not working! dunno why.
i now want to "downgrade" to earlier firmware.
currently i have v24-sp2 build 19342. (Atheros AR7161 rev 2)
what is the best method to downgrade to V24-preSP2/2012/03-08-12-r18767 ?
try webflash or better restore to stock firmware and then install the factory.img ?
Do a 30/30/30 reset before downgrading and you are safe
Joined: 03 Jan 2010 Posts: 7568 Location: YWG, Canada
Posted: Thu Feb 07, 2013 9:29 Post subject:
Updated WNDR3700 wiki for v3 support, v4 work in progress & changed/removed old info thats not longer in effect, broken links etc. _________________ LATEST FIRMWARE(S)
BrainSlayer wrote:
we just do it since we do not like any restrictions enforced by stupid cocaine snorting managers
My WNDR started some kind of channel-flipping. In the picture you can see it's jumping between channel 8 and channel 12. This is a little strange, because it is set to channel 8. I'm having a broken wifi for some time now, could this be related? Or is it a feature I'm not aware of?
Your WiFi isn't broken, the router is just channel bonding at 40 MHz.
The way WiFi at 2.4 GHz works is that each channel really bleeds into 3 neighboring channels. Each channel is roughly 5 MHz in each direction, and a standard WiFi signal is 20 MHz (actually 22 MHz, technically, but no need to add more confusion). That's what inSSIDer is showing you.
The above is also the reason why 2.4 GHz is so congested: there are really only 3 non-overlapping channels. So, if you aren't using channels 1, 6, or 11, then you are actually getting worse performance, and are f*cking up your neighbor's signals too. 5 GHz is better since there are more available channels, but even it will eventually get very congested (particularly with the new AC standard which can use up to 160 MHz for one WiFi signal versus the 40 MHz maximum in 802.11n). Worse, 5 GHz doesn't have the range that 2.4 GHz has (higher frequencies require more power), and has a harder time going through objects.
Anyways, if you don't want/need channel bonding, then don't set your AP's channel width to Turbo. The reason why your WiFi might appear to be broken is that you are probably running it out of your country's specifications, and your devices won't connect to it as a result. Change your regulatory domain. Many countries only allow channels 1-11, and based upon the graph you posted, your country is one of those (all the other routers are using channels 1-11). Some devices simply won't connect to wireless networks out of the originating country's spectrum unless you modify the code in the drivers. Also, they might not even be capable of doing so (hardware-wise).
Long story short: READ THE WIKI! If you don't know what you are doing, don't randomly change settings and then whine that something is broken.
Joined: 03 Jan 2010 Posts: 7568 Location: YWG, Canada
Posted: Wed Mar 20, 2013 19:19 Post subject:
ciper wrote:
Can someone suggest a fast/stable firmware version that doesn't have the 17dbm 2.4ghz cap? So far the latest one I have seen mentioned is 18007.
I like the stability of 18777 but the wireless power bug is crap.
The latest.. back when gui said 22dBm was incorrect reportings.. or my range wouldnt be the exact same as those firmwares with 22dBm & the current one with 17dBm.. not to mention the next released build will have codel/fq_codel finally & does it ever work well. _________________ LATEST FIRMWARE(S)
BrainSlayer wrote:
we just do it since we do not like any restrictions enforced by stupid cocaine snorting managers
Can someone suggest a fast/stable firmware version that doesn't have the 17dbm 2.4ghz cap? So far the latest one I have seen mentioned is 18007.
I like the stability of 18777 but the wireless power bug is crap.
The latest.. back when gui said 22dBm was incorrect reportings.. or my range wouldnt be the exact same as those firmwares with 22dBm & the current one with 17dBm.. not to mention the next released build will have codel/fq_codel finally & does it ever work well.
Joined: 03 Jan 2010 Posts: 7568 Location: YWG, Canada
Posted: Thu Mar 21, 2013 3:24 Post subject:
StiKemUp wrote:
tatsuya46 wrote:
ciper wrote:
Can someone suggest a fast/stable firmware version that doesn't have the 17dbm 2.4ghz cap? So far the latest one I have seen mentioned is 18007.
I like the stability of 18777 but the wireless power bug is crap.
The latest.. back when gui said 22dBm was incorrect reportings.. or my range wouldnt be the exact same as those firmwares with 22dBm & the current one with 17dBm.. not to mention the next released build will have codel/fq_codel finally & does it ever work well.
Posted: Tue Mar 26, 2013 4:26 Post subject: SSH problems in build 21061 (03-25-2013)?
I'm getting any SSH connection dropped almost immediately after connecting after upgrading to this firmware build. Running dropbear from telnet shows:
dropbear -b /tmp/loginprompt -r /tmp/root/.ssh/ssh_host_rsa_key -d /tmp/root/.ssh/ssh_host_dss_key -p 22 -E
[2024] Mar 26 00:08:59 Running in background
[2035] Mar 26 00:09:26 Child connection from 192.168.0.2:51000
Aiee, segfault! You should probably report this as a bug to the developer
On the client side (using Putty) it craps out here:
Event Log: Using Diffie-Hellman with standard group "group14"
Event Log: Doing Diffie-Hellman key exchange with hash SHA-1
Outgoing packet #0x1, type 30 / 0x1e (SSH2_MSG_KEXDH_INIT)
[snip some binary data]
Event Log: Server unexpectedly closed network connection
Anyone else with this issue? I have disabled SSH (apply-save-reboot) and reenable SSH (apply-save-reboot) which should have deleted and regenerated everything in nvram. This build contains dropbear v2013.56 from 2/21/2013 so the paint is still wet there (as are my suspicions).
