The beginning of septembre there was a change in identification codes (board_id) of the Netgear routers. Netgear released a R6400v2 but identical R6400v2 had different board_id's ( nvram show | grep board).
Netgear really made a mess of that.
It is possible then that either a bug has been introduced or that board_id's of recent R7000P have been changed by Netgear.
I do not have one so I can check, but you can always send one to me for further investigation (just kidding)
If there are any experts I think the code can be found at source/router/rc/mtd.c and source/router/libutils/libutils/detect.c
R7000P board_id should be: U12H270T20_NETGEAR
Edit: just took a peek at the source code, cannot find anything wrong with it (but I have very limited coding skills)
It checks the boardnum ==32, boardtype ==0x0646 and boardrev == 0x1601, then checks the board_id and if that is U12H270T20 then it should be recognised as a R7000P.
If it is not recognised then it defaults to R6400v1!
So I am interested in [code]nvram show | grep from R7000P users
That looks OK, we (@Kernel-Panic and I) have identified a possible source of the misidentificationas as a bug in the source code.
We have send a proposal to solve this bug to the developers (I have personally contacted Kong).
But they are really busy and it might take a while and some repeated but polite asking
In the mean time you might try a build a build prior to 36816. That is where things went wrong (at least IMHO)
I have not reviewed the source code for the consequencies of the misidentification, partition layout is connected to the router model and it could be that your boarddata partion is compromised, lets hope not. If you did not erase nvram i think it is wise not to do so but am not sure about that
Where can I find the older builds? I only see the 9/18 and 11/18 builds in Kong’s directories. I guess I can use bs builds. Can you point me to the older builds?
Joined: 08 May 2018 Posts: 3149 Location: Texas, USA
Posted: Wed Nov 14, 2018 14:45 Post subject:
I did also notice that the et2phyaddr was removed from the detection algorithm, but I think it may be of no consequence as it may be a shared variable amongst all the routers included in that part of the code.
"Busy"... "Polite".... that makes me chuckle, but yeah.
Fixed build is uploading, use the R7000P.bin to update and do not use ddup unless you change DD_BOARD otherwise ddup would pull in the 6400v1 build again.
I flashed this new version, and the router model is now correct.
However, I'm still having trouble with 5ghz (wl1). If I disable wl0, the 2.4ghz, I receive a message saying my password is incorrect even though I have it set to the same one as my 2.4ghz with the same ssid. So I created a new ssid and gave it a new simple password, but I still cannot connect.
I'm showing 0% errors: 0 OK, 69 errors
Any ideas? This is the first time I've had any problems since flashing this back in November 2017 with the router running as dumb AP with automatic updates.