I'd be happy if there will be a official version too. At the moment, I'm really disapointed from this router, as it useless for me at the moment I have a V1 here since a year or so which I like, but the 2 V2s are just collecting dust..
Here is a direct link to all the files provided on this device at fcc.gov. I take it you wanted the file with the internal photos, since it shows what chipset is in this router. I attached this PDF to this forum post.
(the case the router resides in, in these photos, is different from the one I have though, as can be seen here. I guess the photos are from before the router was put on the market, and the router exterior was redesigned in the meantime)
To try to install dd-wrt on the NETGEAR WNR3500L v2, I followed the wiki page for NETGEAR WNR3500L. Both on a Linux client (browser: Chromium and Firefox) and on a Windows client (browser: Internet Explorer 9), I
performed the 30-30-30 reset,
disabled the wireless adapter on my client,
configured my ethernet adapter to have IP 192.168.1.8, subnet mask 255.255.255.0, gateway 192.168.1.1,
connected my client to an ethernet port on the router,
double-checked the network configuration on my client before proceeding,
browsed to 192.168.1.1, logging in with the default username and password (before which I am asked if I want to use some setup wizard, to which I say no) (NETGEAR router firmware is V188.8.131.52_30.0.43),
skipped cancelling the automatic update, since the option was nonexistent,
tried uploading the provided trailed .chk file under "Router Upgrade",
with no success.
In the last step, if I provide this .chk file to the web interface, an error occurs when I press "upload" after about 1 second of file transfer. The error message given is "Firmware upgrade failed. Please check your file. This screen will automatically return to the previous screen in a few seconds...".
If I instead provide this .bin file to the web interface, an error occurs when I press "upload" before a file transfer commences (tested by disconnecting my client from the router before picking the file). The error message given is "Please assign the correct file. The file format is *.chk".
So it seems to me that a client-side script checks the file extension to ensure that it is ".chk". If it is, "update" starts a transfer. The router will immediately check the file header to see if the image is intended for this router. The router then sees that the image is not intended for this router (supposedly since it is intended for the NETGEAR WNR3500L v1), kills the transfer, and reports an error to the client.
Update: I got impatient, and flashed my NETGEAR WNR3500Lv2 with the trailed build provided in the myopenrouter.com forum post I linked to earlier (download link for the archive therein containing the .chk file I used), instead of the .chk file recommended in the wiki post for NETGEAR WNR3500L.
I then tried following the rest of the wiki entry for the NETGEAR WNR3500L, that is, to install this .bin file, to install type "big" DD-WRT on the router.
It failed; the DD-WRT web interface reported "Upgrade Failed".
I did a 30-30-30 reset, just in case, and now I have a working DD-WRT firmware on my NETGEAR WNR3500Lv2.
I do not know which features it supports, though; did the "big" firmware get installed despite the failure notification? If not, how do I see which features the current firmware supports? How do I see which firmware is currently running?
On the top of the web interface, it says Firmware: DD-WRT v24-sp2 (12/01/11). How do I read the date? YY-MM-DD, MM-DD-YY or DD-MM-YY?
Posted: Fri Mar 23, 2012 19:57 Post subject: Yes. Me too
Yes. I would like a version for the v2 too. I just bought one yesterday from Staples having read all the reviews saying how good it worked - and then I run into the problem that it will not load the .chk file because it needs a v2 header. I am new to dd-wrt so would like to use a tested build rather than make one myself.
I did get a version running on it, but none of the dd-wrt.com based brainslayer or eko builds will load over the top.
Just get rejected. bad magic number on a telnet flash
I was looking at compiling my own with the options I need, OpenVPN and Milkfish, but if someone else is working on it, I'm happy to dedicate my resources elsewhere, like testing it in production or helping on the forums or IRC