Posted: Fri Mar 28, 2014 7:38 Post subject: R6300v1 and br0:0
So I've Netgear R6300v1 and DD-WRT K3 for NETGEAR R6300 802.11ac Router - Kong build.
My provider does not give any DHCP for WAN network, so it defauls to 169.254.xx.xx. This is a problem, since br0:0 takes this subnet for IP-addresses, and PPPoE can't connect, since routing prevents its packets to go to the right interface. If I do "ifconfig br0:0 down", everything is just fine.
However, if I make any changes in the web interface, it is up again and everything breaks down.
Is there any way to disable this interface forever or change it's IP address? Would "ifconfig br0:0 10.0.0.1 255.255.255.0" on startup work, or it would break something else?
nvram backup is done with netgear installed, by running command:
nvram show > /tmp/nvram.txt
But if you already converted it to a R6300V2, then we won't be able to get original nvram params anymore. And getting back to netgear AC 1450 fw will be difficult now. Thus we probably have to wait for someone else to dump nvram.
Without the nvram params for the radio there is a chance, that the radios are not working as supposed to e.g. weak signals etc.
The nvram in my dump of my busted router seems to be intact. You can get the info in my dump at offset 0x1f0000
If anyone has a CFE backup for a R6300v1, or if anyone with that router could PLEASE go to http://192.168.1.1/backup/cfe.bin and attach it to a post in this forum, it would allow me to have a working router again. There is no passwords or anything in the CFE, so there is no privacy concerns in posting it. All routers with that board version should contain the exact same CFE binary. The dump I posted has everything but the CFE bootloader as far as I can tell.
4. CHECK and UNDERSTAND the proper build for your router. The ROUTER memory (flash memory...not RAM) determines what build you can put on it. It is simple math. If you have a 4mb flash chip, you can't put a build larger than 4mb on it because it won't fit, even if you wish to have advanced features. In other words, don't look at the features and decide which one you want and then install it. You will often brick your router. This is bad.
...
Read the rest of this note to understand builds to flash to your router, once dd-wrt is installed according to the wiki, and to make sure you are flashing a supported build for your router.
To pick a build, there are three things you need to know. The process for flashing, the build type (micro, mini, standard or mega) and whether you need newd, K26, or vint. Then you can pick the build svn (14929, 13491, 12548 etc.) that you want to flash.
You don't have to use the build VERSION that are recommended in the wiki but it is a good practice to do so unless you undestand how all this works. You should use the build TYPE. (See below in this note.)
You need to know whether you can put micro, mini, standard or mega on your router. You can determine what TYPE of build is supported on your router by going here:
http://www.dd-wrt.com/wiki/index.php/Supported_Devices
...
NEWD is the NEW Driver based on the kernel 2.4. Many routers use this. Vint is the old Vintage driver for really early Linksys router from about 10 years ago, also based on kernel 2.4. Newd-2 is a newer driver that is available both in a kernel 2.4 and a kernel 2.6. It offers no real benefit in the kernel 2.4. It will brick many routers. K26 is the new kernel that some very new routers MUST use and it has the newd-2 driver. Using K26 on a router that doesn't support it, or failing to use K26 on a router that requires it will both brick the router.
NEWD has only NEWD (NOT NEWD2) in the filename of the bin file...DON'T CONFUSE THIS WITH NEWD2. All Brainslayer builds without k26 in the filename are NEWD builds. NEWD-2 has NEWD2 in the filename. K26 has K26 in the filename of the .bin file. VINT has the word VINT in the filename.
Most routers should use NEWD rather than VINT when they can. VINT is for old routers that cannot support the new wireless drivers. Many new models can ONLY use k26 builds, as explained above - if your original flash from the wiki was a build with k26 in the filename, you must always flash with a k26 build.
You should use VINT builds if you have a corerev=4 or less. If your router is a v.1, REALLY check to ensure whether you need VINT or not.
Netgear fw doesn't set a specific txpwr but they tell the driver to output the maximum allowed power, which is 1000mW in 5G for US/EU. Some channels don't allow that high output, but this is no problems, as on new models the txpwr is only a suggestion to the driver, it will still decide based on internal tables what output it will send. So you can just set it to 999 and the radio will output the maximum allowed txpwr.
Registered just to share my stupidity. I've twice flashed my R6300v2, and twice reverted to stock because of signal problems. Notably, I was following a generic tutorial to tweak the advanced wifi settings—one that advised a txpwr value of 120-160.
Posted: Mon Mar 31, 2014 2:51 Post subject: A few questions to Kong
Hi, Kong
My router is R6300v2 and installed your build recently. It works great and thanks you for the effort. I have some questions about the firmware:
1. Is it compatible to install the package whose arch is "brcm47xx" ? How about "ar71xx" ? Why the arch in your firmware is "bmc53xx"? As I know, the router's chip is bmc4708.
2. Have you consider to import forked-daapd into your repository? It's really nice to setup a itunes server on the router.
Posted: Mon Mar 31, 2014 9:53 Post subject: Re: A few questions to Kong
streak wrote:
Hi, Kong
My router is R6300v2 and installed your build recently. It works great and thanks you for the effort. I have some questions about the firmware:
1. Is it compatible to install the package whose arch is "brcm47xx" ? How about "ar71xx" ? Why the arch in your firmware is "bmc53xx"? As I know, the router's chip is bmc4708.
BCM4707/BCM4708/BCM4709/BCM5301 are all of the same family
ar71xx is completely different arch. Basically the bcm53xx naming comes from openwrt as I use openwrt to build the packages.
Quote:
2. Have you consider to import forked-daapd into your repository? It's really nice to setup a itunes server on the router.
Hi, I've r23770 working on a Netgear R6300V2 and is wonderfull!!
all that in a 'simple' router, with an additional 128GB usb it's the only hardware I need to share media all around the house ....
Thanks a lot!!!
My only problem is with minidlna, it has a bug https://sourceforge.net/p/minidlna/bugs/180/ and I know how to fix it in code but I don't know / cannot cross compile it for dd-wrt ....
Kong ¿will it be possible to include the patch for minidlna in the next version?
I've followed http://wiki.openwrt.org/doc/devel/crosscompile but know I'm blocked in
./configure --host=arm-openwrt-linux-uclibcgnueabi
with
configure: error: libavutil headers not found or not usable
¿there is another way to compile it ? or should I compile all deps? is there a guide or a script or a .tar to do it?
Hi, I've r23770 working on a Netgear R6300V2 and is wonderfull!!
all that in a 'simple' router, with an additional 128GB usb it's the only hardware I need to share media all around the house ....
Thanks a lot!!!
My only problem is with minidlna, it has a bug https://sourceforge.net/p/minidlna/bugs/180/ and I know how to fix it in code but I don't know / cannot cross compile it for dd-wrt ....
Kong ¿will it be possible to include the patch for minidlna in the next version?
I've followed http://wiki.openwrt.org/doc/devel/crosscompile but know I'm blocked in
./configure --host=arm-openwrt-linux-uclibcgnueabi
with
configure: error: libavutil headers not found or not usable
¿there is another way to compile it ? or should I compile all deps? is there a guide or a script or a .tar to do it?
Thanks
Nico
I just added the fix to my source tree, so my upcoming build will include it, if no one complains I add the fix to dd-wrt repository. _________________ KONG PB's: http://www.desipro.de/ddwrt/
KONG Info: http://tips.desipro.de/
