When I compare the files 2q2 posted with the ones which are available on the FTP (build 17201) I think that these are the files for the WNDR3700v1 only.
In addition, for upgrading your WNDR3700v1 you only need the wndr3700-webflash.bin and remember not to choose "rest to defaults" on the upgrade page. The upgrade file is suitable for both North America (NA) and rest of the world.
The "wndr3700-factory.img" file is for the initial flashing from stock firmware for the rest of the world. Users with NA units need the "wndr3700-factory_NA.img".
And now I'm gonna upgrade my WNDR3700v1, hopefully it will work and thanks to 2q2!
When I compare the files 2q2 posted with the ones which are available on the FTP (build 17201) I think that these are the files for the WNDR3700v1 only.
In addition, for upgrading your WNDR3700v1 you only need the wndr3700-webflash.bin and remember not to choose "rest to defaults" on the upgrade page. The upgrade file is suitable for both North America (NA) and rest of the world.
The "wndr3700-factory.img" file is for the initial flashing from stock firmware for the rest of the world. Users with NA units need the "wndr3700-factory_NA.img".
And now I'm gonna upgrade my WNDR3700v1, hopefully it will work and thanks to 2q2!
I was running the Buffalo branded dd-wrt on my WZR-HP-G300NH. With the stock, I was not getting consistent 300mbps connections (it would always drop to 130mbps) and I would notice quite a few outputs to /var/log/messages. I upgraded to 17461 last night and I'm holding strong at 300mbps and with the messages log showing pretty clean
Great! Is that North America or the rest of the world (I'm in EU)?
I assumed that it was for the WNDR3700v1 and for EU (since the filename didn't contain "NA") and I tried flashing it using TFTP and it wasn't any problem. I will comment my experience in another thread I already started, but this version looks VERY promising!
Joined: 03 Jan 2010 Posts: 7568 Location: YWG, Canada
Posted: Wed Aug 24, 2011 22:36 Post subject:
Apparently my max TX power for ath0 is now 17dBm instead of 22dBm and its stuck in HT20 mode.. ath1 is still capping at 24dBm and is staying in HT40 mode, ack timing appears stuck at 450m unless its auto adjusting (doesn't "0" do this already and POORLY at that?). Dynamic HT20/40 mode is still broken and not letting anything connect when used.
Memory use is improved, more constant 67% free, though im going back to 17201, I expect HT40 when I damn select it, and "it forces HT20 when it detects other APs around" is rubbish, stock firmware does not do that neither does 17201 so that better not be an intentional change. I've ran 4 APs beside each other all on HT40 with no interference.... Other than that the channel listing is finally proper and it overall is stable. Fix the TX power and HT40 and i'll use it constantly (no I should not have to SSH to the router etc to manually change things to force it, fix it).
When I compare the files 2q2 posted with the ones which are available on the FTP (build 17201) I think that these are the files for the WNDR3700v1 only.
In addition, for upgrading your WNDR3700v1 you only need the wndr3700-webflash.bin and remember not to choose "rest to defaults" on the upgrade page. The upgrade file is suitable for both North America (NA) and rest of the world.
The "wndr3700-factory.img" file is for the initial flashing from stock firmware for the rest of the world. Users with NA units need the "wndr3700-factory_NA.img".
And now I'm gonna upgrade my WNDR3700v1, hopefully it will work and thanks to 2q2!
nFamous
Exactly. These files are for version 1. Sorry, I forgot to mention this in my post.
Posted: Fri Aug 26, 2011 3:41 Post subject: Wifi device cannot re-connect after "ifconfig ath0 down
My experience -
r17461
Buffalo wzr-hp-g300nh
cron jobs to turn off and on wifi, ath0 down and ath0 up.
When the wifi be back up, all my wifi devices will not be able to re-establish a connection.
Found that if I login into dd-wrt web mgmt, select "wireless" and "apply settings" (without changing anything) that would "correct" device connection problems.
Tests included resetting to factory default, re-installing r17461 and 30/30/30 reset.
Currently, cron jobs disabled and possibly reverting back to r16785.
