But when I flashed my Asus RT-AC86P, everything went fine, but there is no /etc/config/wireless file. And even if I put a line to enable the wireless in the LUCI, there's nothing there for me to configure.
I do have a bit of experience with Linux, but mainly with Ubuntu, Debian and the like, which usually auto-detect and configure such things for you...
Soooooo... how does one create a basic wireless configuration file? Is there a auto-config script or command that I've missed?
Again, I apologize if I'm missing the obvious, but I've searched through things and just can't seem to find anything beyond the fact that I'll need to create the file from scratch.
Woah, easy there fella... you're assuming a few things here!
First off, I didn't buy this solely to use with LEDE/OpenWRT. I'm a network admin and I'm coming back to LEDE/OpenWRT after a few years using other tools on about 5 different ASUS router models. Yes, I've stuck with ASUS because of the easy re-flash capability built in.
So, while I may be new to the boards, I'm not a total NOOB!
Let's clear up the confusion first. It's not a typo, RT-AC68P is the actual model number, it's simply an updated version of RT-AC68U (was mainly available from Best Buy a little over a year ago). It has a faster cpu model, but otherwise uses the same SOC as the RT-AC68U. Actually, this router works just fine with DD-WRT, Tomato, AdvancedTomato, etc for the ASUS RT-AC68U firmware.
Now, with that out of the way, this question is not related to the wireless not working, it's an issue with the wireless configuration file not being created. With that in mind, can you provide a template /etc/config/wireless?
dd-wrt and Tomato have licenses with Broadcom to use closed source drivers. Fully open-source support for Broadcom wifi chips is very limited. Thus LEDE developers and users avoid buying Broadcom based routers.
You can check if a WiFi driver is installed and working by running iw list on the command line.
I had been reading source code and come to the conclusion that there are two scripts that run on startup that check for and create the needed configuration based on specific hardware. So thank you for clarifying that!
Also, thank you for clarifying what you mean by "not supported". There is support out there, but it's not fully open-sourced, and this project stays away from that. I get it now.
I'm aware that dd-wrt has dabbled with certain licensing and commercial offerings, however Tomato has not. Tomato has no license to use any closed source drivers and, as far as I can tell, they use the open source broadcom driver... I'm assuming with modifications.
I'm going to be investigating sources from Shibby's code he's been using which enables use of all the devices I've documented so far: MIPSEL ARM
I'll report back if/when I find anything... but of course, anyone is welcome to join me on the journey...