Seems VAPs were broken around middle of 2018.
If you search the New Build threads from around that time you may find your answer.
Try something from April-May.
I know r35550M kongac (03/28/18 ) VAPs work as expected for my R6300v2's. Uses the same build as your R7000 would.
I don't know for sure if it was the last one or not.....maybe 2nd or 3rd last? Can only confirm the one mentioned. ¯\_(ツ)_/¯ _________________ Location 1
R7800- DD-WRT v3.0-r53562 (10/03/23) Gateway
WNDR3400v1 DD-WRT v3.0-r35531_mega-nv64k (03/26/18 ) Access Point
WRT160Nv3 DD-WRT ?v3?.0-r35531 mini (03/26/18 ) Access Point
WRT54GSv5 DD-WRT v24-r33555_micro_generic (10/20/17) Repeater
Location 2
R7800- DD-WRT v3.0-r51855 (02/25/23) Gateway
R6300v2- DD-WRT v3.0-r50671 (10-26-22) Access Point
WNDR3700v2 DD-WRT v3.0-r35531 std (03/26/18 ) Access Point
E1200 v2 DD-WRT v3.0-r35531 mega-nv64k (03/26/18 ) Gateway(for trivial reasons)
RBWAPG-5HACT2HND-BE RouterOS-v6.46.4 (2/21/20) Outdoor Access Point
2x RBSXTG-5HPACD RouterOS-v6.46.4 (2/21/20) PTP Bridge 866.6Mbps-1GbpsLAN
Location 3
2x R7000- DD-WRT v3.0-r50671 (10/26/22) Access Points
2x RBWAPG-60AD RouterOS-v6.45.9 (04/30/20) PTP Bridge 2.3Gbps-1GbpsLAN
2x RBSXTsqG-5acD RouterOS-v6.49.7 (10/14/22) PTP Bridge 866.6Mbps-1GbpsLAN Thank You BrainSlayer for ALL that you do & have done, also to "most" everyone here that shares their knowledge
Seems VAPs were broken around middle of 2018.
If you search the New Build threads from around that time you may find your answer.
Try something from April-May.
For those running ARM based Broadcom routers, if you don't mind, try the following and see if it solves your problem.
.
.
Do report back if the above works for you. It can then be used to report back to BS & Kong for further investigation.
HTH.
Router/Version: Asus RT-AC68U
File: dd-wrt.v24-K3_AC_ARM_STD.bin (TEST Build)
Firmware: DD-WRT v3.0-r39960M kongac (06/08/19)
Kernel: Linux 4.4.180 #666 SMP Sat Jun 8 11:15:19 CEST 2019 armv7l DD-WRT
Mode: AP, 2.4(Wide HT40)+5(VHT80). Both radio work simultaneously.
Setup>Networking GUI: works flawlessly
VLAN: GUI Mode works just by adding vlan.*hwname
VAP: Works on br0. But breaking out to other bridges with VLANs or independently does not connect. Even eth1 and eth2 breaking out of br0 stop connecting with authentication failure.. VAP worked on all these test builds with @quarkysg 's workaround mentioned in this post earlier in an earlier thread
Thank you @quarkysg, you rock!!
Somehow I keep posting in wrong places. Earlier I posted this message above in BS r40009 New Builds thread
TBH I have tried both (09-26-2018 and TEST) Kong AC builds from desipro.de and r40009, r40048, r40065 from BS' Beta builds... None of them had the VAP authentication working. Both in r40048 BS and
r39960M kongac builds after running the workaround it worked.
As I'm still setting things up I have the freedom to try and and retry.. but once I put it up my family won't let me touch the equipment
Now I have questions:
1. Several other forum posts suggest that VAP doesn't work but in order to let BS and Kong know what should I do
2. Is there any other way to persist `quarkysg's wlconf` w/o adding jffs on USB
For those running ARM based Broadcom routers, if you don't mind, try the following and see if it solves your problem.
.
.
Do report back if the above works for you. It can then be used to report back to BS & Kong for further investigation.
HTH.
Router/Version: Asus RT-AC68U
File: dd-wrt.v24-K3_AC_ARM_STD.bin (TEST Build)
Firmware: DD-WRT v3.0-r39960M kongac (06/08/19)
Kernel: Linux 4.4.180 #666 SMP Sat Jun 8 11:15:19 CEST 2019 armv7l DD-WRT
Mode: AP, 2.4(Wide HT40)+5(VHT80). Both radio work simultaneously.
Setup>Networking GUI: works flawlessly
VLAN: GUI Mode works just by adding vlan.*hwname
VAP: Works on br0. But breaking out to other bridges with VLANs or independently does not connect. Even eth1 and eth2 breaking out of br0 stop connecting with authentication failure.. VAP worked on all these test builds with @quarkysg 's workaround mentioned in this post earlier in an earlier thread
Thank you @quarkysg, you rock!!
Somehow I keep posting in wrong places. Earlier I posted this message above in BS r40009 New Builds thread
TBH I have tried both (09-26-2018 and TEST) Kong AC builds from desipro.de and r40009, r40048, r40065 from BS' Beta builds... None of them had the VAP authentication working. Both in r40048 BS and
r39960M kongac builds after running the workaround it worked.
As I'm still setting things up I have the freedom to try and and retry.. but once I put it up my family won't let me touch the equipment
Now I have questions:
1. Several other forum posts suggest that VAP doesn't work but in order to let BS and Kong know what should I do
2. Is there any other way to persist `quarkysg's wlconf` w/o adding jffs on USB
Thanks
-B
Hello,
I think I found a fix/workaround today when I was setting up my Asus RT-AC68U with Kong build; I had the same problem as you described.
Are you still experiencing the VAP issues with
File: dd-wrt.v24-K3_AC_ARM_STD.bin (TEST Build)
Firmware: DD-WRT v3.0-r39960M kongac (06/08/19)?
For those running ARM based Broadcom routers, if you don't mind, try the following and see if it solves your problem:
1. Download the attached wlconf.gz file and transfer to your router.
2. 'gunzip' the file with the following command:
Code:
gunzip wlconf.gz
chmod u+x wlconf
3. Issue the following commands in the same directory that you have uploaded the wlconf.gz file:
Code:
stopservice nas
stopservice wlconf
./wlconf eth1 up
./wlconf eth2 up
startservice nas
You can ignore all the errors shown when the 'wlconf <intf> up' commands is executed.
From the changes in the source codes for the 'wlconf' utility, it looks like the way that the MAC addresses are getting generated for the wireless interfaces have changed for newer drivers. I guess it only applies to newer Broadcom wireless chipsets, which broke older chipsets.
I changed the 'wlconf' utility behaviour back to what it was previously and it seems to work OK for the following routers which I'm using:
D-Link DIR-868L
D-Link DIR-880L
Asus RT-AC68U/W
Do report back if the above works for you. It can then be used to report back to BS & Kong for further investigation.
HTH.
Thanks for providing those! They worked great! I'm running DD-WRT on an ASUS AC68U.
There were a couple of posts in this thread mentioning making it persistant with startup commands. However, this would require that I store the binaries somewhere. Is that able to be done without attaching an external storage device? If not, is JFFS what I need to look into?
Joined: 18 Mar 2014 Posts: 12922 Location: Netherlands
Posted: Mon Aug 05, 2019 13:51 Post subject:
pianoquintet wrote:
The commands suggested by quarkysg on the first page fixed my problem on an RT-AC56U.
They are not permanent, however, so the issues arise again on reboot. Can anyone help me make them permanent?
Thank you.
It can only be done if you have permanent storage.
Copy the unzipped files to your permanent storage like jffs make them executable like the instructions already given
and put following in administration/commands Save startup:
Code:
sleep 30
stopservice nas
stopservice wlconf
/jffs/wlconf eth1 up
/jffs/wlconf eth2 up
startservice nas
Before putting anything in startup command test from command line first otherwise if the commands are wrong you might have to reset.
I think I found a fix/workaround today when I was setting up my Asus RT-AC68U with Kong build; I had the same problem as you described.
Are you still experiencing the VAP issues with
File: dd-wrt.v24-K3_AC_ARM_STD.bin (TEST Build)
Firmware: DD-WRT v3.0-r39960M kongac (06/08/19)?
Let me know and I'll post results.
Thank you
@NotAutistic, Sorry for the delayed reply. I still do have intermittent issues when I took the patched wlconf provided in this thread away. I was only using restarting cron, nas, wlconf services in LIFO as recommended in other posts.
In the latest build post I see folks reporting there is no issue of VAP restarting.. what's your workaround?
and Thanks for your reply earlier!
Just to report that no VAP connection problem with the v3.0-r41027 on TP-Link Archer C9v1., if using dhcp on dd-wrt.
The patched wlconf also solve the dd-wrt running as AP (router) mode, with wl0.1 bridging VLAN and br1 (tagged VLAN on VAP)and using dhcp on PfSense. Thanks a lot.
Last edited by bthoven on Fri Nov 08, 2019 6:09; edited 3 times in total
Posted: Tue Nov 12, 2019 4:35 Post subject: Slow Ethernet
Hello all,
Can anybody please let me know if this affects ethernet speeds? I'm getting 1/10th the bandwidth that I can on my upstream router using ethernet.
I didn't benchmark before. However, my upstream router/internet gateway (pfsense) is getting ~450/50 Mbps, while my AC68U dd-wrt is getting ~35/2 Mbps. It's not even NATting, it's just routing.
If this is probably not related to `wlconf`, then I'll make a separate post about it.