I can only speek for myself in flashing a wax206. You can clone into one of the following git repos:
Build the image with the OpenWrt build system. You have to choose the right architecture with menuconfig. After build you can very easyli flash the image to the router via netgear web interface. Also just be invited to scroll up in this conversation to find necessary additional information.
@patient0 mentioned: There will be a pull request soon (as far as I did understand) so there might be first "official" snapshots soon.
@kcvanderlinden, right now you have to build it yourself.
Regarding the branch I'm not sure who else is working on their own one, a (very) few people did give feedback on the branch I'm working on. But if you don't have TTL/serial access you may want to wait a bit longer.
I created a PR a few minutes agaon from my newly forked repo today, branch
wax206/flashable-1Gbit. I seem to have messed up the OpenWrt git repo fork the first time and had to fork openwrt again, that's why the repo for the PR is different.
Pretty much everything seems to works except 2.5G mode for the WAN interface. That is a software limitation right now and it's very likely that it will be solved.
There is one issue regarding the flash layout size which I don't understand:
If I flash from stock to OpenWrt using the
*-factory.img I get a ubi-0 which contains two volumes with
volume ID 0, size 68LEBs (8.2MiB), name
volume ID 1, size 143LEBs (17.3MiB), name
But if I flash from OpenWrt to OpenWrt using
*-sysupgrade.bin I end up with two volumes of different sizes:
volume ID 0, size 100LEBs (12.1MiB), name
volume ID 1, size 111LEBs (13.4MiB), name
The entries after flashing
*-factory.img seems reasonable to me. But the second not so much.
What is the output of
ubinfo -a for others and how did you flash?
Volumes count: 2
Logical eraseblock size: 126976 bytes, 124.0 KiB
Total amount of logical eraseblocks: 272 (34537472 bytes, 32.9 MiB)
Amount of available logical eraseblocks: 0 (0 bytes)
Maximum count of volumes 128
Count of bad physical eraseblocks: 0
Count of reserved physical eraseblocks: 39
Current maximum erase counter value: 2
Minimum input/output unit size: 2048 bytes
Character device major/minor: 250:0
Present volumes: 0, 1
Volume ID: 0 (on ubi0)
Size: 38 LEBs (4825088 bytes, 4.6 MiB)
Character device major/minor: 250:1
Volume ID: 1 (on ubi0)
Size: 189 LEBs (23998464 bytes, 22.8 MiB)
Character device major/minor: 250:2
Flashed with nmrpflash.
@MOST2K2 : Thanks for reporting back. Did you flash the
sysupgrade.bin or the
factory.img, from what branch and do you have an EU model?
I'll give nmrpflash a got and see if that shows a different result. Not sure why is would behave different.
And as an important sidenote: Along the way I did increase the kernel size from 4MB to 6MB as was recommended. AFAI understood just flashing the new firmware will not change the that and one has to first flash back the stock firmware and then the new firmware. But maybe nmrpflash will work too. Or someone got a better idea.
factory.img, i used the 1GB branch with EU model.
The 2.5g port is not working and software updates not working too for most packages.
care to share the .config, I don't think it's in the 2.5G repo, and make picks the defaults, which are obviously incorrect.
no surprise, you're using an inofficial build.
@frollic, this is the diffconfig.sh output which I use as basis for compilation.
# CONFIG_LUA_ECO_WOLFSSL is not set
# CONFIG_PACKAGE_kmod-ppp is not set
# CONFIG_PACKAGE_ppp is not set
I updated and install the feeds, then run
make defconfig && make oldconfig, then
make -j<cpus> toolchain/install; make -j<cpus>.
Addition: I do work with the wax206/flashable-1Gbit branch.
@patient0: I'm testing my EU-Model as router with wireguardserver and ddns for a while now. After stumbeling over the fact, that the wax can't do 160mhz on 5Ghz and 40mhz on 2.4Ghz wlans, my setup works stable.
first use wax206,so..any OpenWrt firmware support for WAX206
Tried reading this thread?
It’s in development. See
for officially available firmware support
not work for me
i use git bash os is windows 7
then use the alter CSS web code "hack", to enable telnet, or telnetenable2.
You do realize that you can't use the wax202 firmware on the wax206, right?
@patient0 as you did a good chunk of the work, thank you for the effort. I will not be installing it yet as I want to wait for the official release version.
I think it's fair to let you choose what I do with my 100 USD. Where do I send it? (You can DM me if you wish).
Okay, just wanted to make sure you didn't try flashing the 202 openwrt on the 206 as I thought the post with the link to the current 202 release is a bit confusing
Other then that, I think nobody will be able to help you with just a "it doesn't work!" message. They will need more information from your attempt before you get the help you need to make it work