It just doesn't seem to be used to detect anything.
- B
Oh. Well I have a theory about that... it could be a failsafe for the R6700v3 which is identical to the R6400v2 (yay, NetGear !!!). It would make sense to include that router in this code since it would be able to run it without a problem. I don’t have the 6700v3 though so I can’t confirm this. Seems like a possibility though.
If anything, I agree that the procedure of identifying the model could use some TLC. Whether the board ID belongs to a 6400v2, 7000P, or both...
This post might seem kind of repetitive ... but nevertheless I want to add that there seem to be serious issues with builds on the R6400v2 because DD-WRT wrongly identifies it as a 7000P. And this is the case with all different builds that I have played with. It seems to be a problem with the “basic” code of DD-WRT itself (not sure what terminology would be correct here). My suspicion is that it seriously messes up the addressing of the memory and the chipset in the back ground. At this point I can’t see recommending ANY build for the 6400v2 because of that problem.
This post might seem kind of repetitive ... but nevertheless I want to add that there seem to be serious issues with builds on the R6400v2 because DD-WRT wrongly identifies it as a 7000P. And this is the case with all different builds that I have played with. It seems to be a problem with the “basic” code of DD-WRT itself (not sure what terminology would be correct here). My suspicion is that it seriously messes up the addressing of the memory and the chipset in the back ground. At this point I can’t see recommending ANY build for the 6400v2 because of that problem.
This post might seem kind of repetitive ... but nevertheless I want to add that there seem to be serious issues with builds on the R6400v2 because DD-WRT wrongly identifies it as a 7000P. And this is the case with all different builds that I have played with. It seems to be a problem with the “basic” code of DD-WRT itself (not sure what terminology would be correct here). My suspicion is that it seriously messes up the addressing of the memory and the chipset in the back ground. At this point I can’t see recommending ANY build for the 6400v2 because of that problem.
R6400v2 and R7000P have same CPU:CPU1: Broadcom BCM4708C0 (1 GHz, 2 cores) but different wl chip.
On 5ghz (R6400v2=BCM4360 and R7000P=Broadcom BCM4365E).
On 2.4ghz (R6400v2=BCM4331 and R7000P=Broadcom BCM4360).
that why 5ghz was disable because it think 2.4ghz wl.
R7000( BCM4709A0=1ghz) is a upgrade of R6400v1(Broadcom BCM4708A0=800mhz).
if FW is .chk then it contains boardID, if you open by Hx or iHex on mac, Hexedit on android then you can see 57byte or so , just delete until you see HDR0 in text, where FW start in router and rename trx. Netgear ussually has 17mtd which mtd5 contain boarid and serial number.
dd if=/dev/mtd5 | hexdump -C
then you can see it. modify for compatible which Fw you want to test.
Mod Fw suits to cfe of router or mod cfe to fit Fw.
Also most wl routers now have 3x3:3 MIMO but most devices like smart phone only has 2 spatial Tx,Rx. some hippcup on latency happen. for best and instantly transmit , router should set 2 spatial Tx and 3 spatial Rx, but i dont know how or there is no option on BroadCom Soc wl. any idea.
I have the 6700v3 if anyone needs me to verify anything. I hope that whatever firmware is ultimately available for 6400v2 is available for 6700v3 as well. I have stock firmware loaded now, and I can't find anywhere to enable telnet in order to check vram for board id (debug.htm does not have an option for telnet).
I have the 6700v3 if anyone needs me to verify anything. I hope that whatever firmware is ultimately available for 6400v2 is available for 6700v3 as well. I have stock firmware loaded now, and I can't find anywhere to enable telnet in order to check vram for board id (debug.htm does not have an option for telnet).
The routers are the same. So you should be able to flash the image on the 6700v3 once it becomes available. I just flashed my 6400v2 back to stock today and boy, was that a pain. More than usual.
Joined: 18 Mar 2014 Posts: 12917 Location: Netherlands
Posted: Wed Aug 08, 2018 9:47 Post subject:
How did you flash back and was it working when on stock?
I just received a new R6400 which i ordered to be placed with friends (I have already an R6400v1) there is no version information when you order, the order number is just R6400-100PES, but just openend the box and it is a V2.
I am running several routers all are using DDWRT, but I am hesitant to put it on th R6400V2 at the moment.
I also hope that @Kong will make a build for this router as the hardware seems pretty decent and it is really cheap here in Europe
How did you flash back and was it working when on stock?
I just received a new R6400 which i ordered to be placed with friends (I have already an R6400v1) there is no version information when you order, the order number is just R6400-100PES, but just openend the box and it is a V2.
I am running several routers all are using DDWRT, but I am hesitant to put it on th R6400V2 at the moment.
I also hope that @Kong will make a build for this router as the hardware seems pretty decent and it is really cheap here in Europe
If I can help let me know I have serial.
I would advise not to flash DD-WRT on a v2 at this point because of a bug in the model detection (there is a ticket filed but not sure when it will be addressed). I used a usb-serial cable... so I had to open up the router. And it doesn’t even have regular screws. But I heard from someone else that there is a tool out there that supposedly did it over an Ethernet cable. I have to check that out.
