has some examples. The device, a WNDR4000 with K3X 37582 Mega (NV64K) is functional. Clicking the field displays the invalid input prompt (sometimes repeatedly) then corrects the field for the appropriate value.
This bug was present at least as far back as 35531.
Troubleshooting or logs on request. Thank you for this great project.
Posted: Tue Mar 19, 2019 6:12 Post subject: DD-WRT v3.0-r38580M kongac (02/05/19) on RT-AC5300 working
Hi,
First of all, I would like to start with Thanking all the Senior members along with BS and Kong for your support, continuous efforts and dedication that you have bestowed over the years. Please let me know if I should post my question in the Advanced Networking section instead of here. Since I am trying out the basic functionality for DD-WRT v3.0-r38580M kongac build on ASUS RT-AC5300, I thought this would be more appropriate forum.
I plan to put a UTM with pfSense between Spectrum modem and this router. But this was my first attempt to run DDWRT on an ASUS. I've used DD-WRT on WRT54Gv2 with SD_Mod back in the days but got swayed between ISP boxes as 'life happens' and ASUS RT-AC series. I got tired after the GFBR network box and started looking for options last year. when I got hold of the RT-AC5300 that I'm working on.
When I tried the very first time flashing this build, I already had Merlin RT-AC5300_384.9 installed. So I reflashed back to ASUS official 3.0.0.4_384_45149-g467037b. On first attempt, the admin UI didn't load after the FW upload and reboot. It took about 3 tries. On the 3rd hard-reset I got the CFE mini browser. Then, I was able to get DD-WRT v3.0-r38580M kongac via the ASUS CFE minibrowser. I ran this build plain vanilla (it's anything but plain!) without any issues for a month. For a default household with couple of computers, smart and streaming devices on one subnet it just works!!
So Thank you :hug:
Now it was time to take a step ahead and really start using DD-WRT as it's meant for. But my first attempt on creating VLANs and bridging them to VAPs failed. That's why I decided to post this issue here instead of Advanced Networking section.
I've read all the posted stickys (and a few other posts) of this section.
My issue is - breaking out each WiFi and its VAPs separately is not working. All radios work fine when on br0 but when I break them out individually in separate bridges (even before adding/applying FW rules) the routing doesn't work. I can't get to WAN. I didn't see getting an IP assigned from the subnet SSID to which I connected.
I've followed the wiki https://wiki.dd-wrt.com/wiki/index.php/Multiple_WLANs and before that thoroughly read https://wiki.dd-wrt.com/wiki/index.php/Switched_Ports as I was planning to bridge VLANs to these bridges next.. but got stuck at the very first step itself. There is /jffs on USB and optware initialized. Other than that, there are no changes in any other tab.
If I'm doing something wrong, a trained eye would catch it in a wink. So please suggest if it is broken or there is something I am missing?
Thank you so much for your time.
-bk
Last edited by bkaskar on Mon Jul 01, 2019 22:37; edited 2 times in total
Posted: Tue Mar 26, 2019 5:35 Post subject: Solced
Hi Again, I found my issue(s) STP was set to ON in the assignment sections. Please let me know if that was not the issue..
Then the vlan*hwnames were also not setup for each of the VLANs.
Now I have 2 questions:
1. I have my basic setup working and as mentioned in the previous post, I plan to do the routing using utm. Then this device will just be an AP. So I would like to know if I define VLANs in the utm, how do I bridge them with the radios/VAPs I defined in my AP? I would like to know how DNSMasq/DHCP setup will change?
2. While creating VAPs and VLANs over UI, I noticed, at times an extra set of VAP and VLAN gets created e.g. wl0.1.3 and vlan3.3 etc. Is that a known bug (if it is a bug), I noticed those additional set appearing right after I added tagging. Did anyone else notice that?
Posted: Tue May 14, 2019 21:08 Post subject: E1200 ver2 no repeater, virtual interface unreliable
E1200 router flashed with latest dd-wrt.v24-37305_NEWD-2_K3.x_mega-nv64k build. When I try to connect to virtual interface which is the AP it is unreliable with no security and useless with WPA2.
I have tried other builds with the same problems. I have tried with windows 10 clients, Iphone clients, other clients no luck.
If I configure in AP mode regular router all clients connect perfectly.
I would like clients to connect to virtual interface as reliably as physical interface.
I tried the mini build same version and the virtual SSID is broadcast when the security is disabled, but the virtual SSID is not broadcast if security is enabled.
On the mega build the virtual SSID is broadcast whether security is enabled or not. but the clients cannot associate with security enabled
I tried the mini build same version and the virtual SSID is broadcast when the security is disabled, but the virtual SSID is not broadcast if security is enabled.
On the mega build the virtual SSID is broadcast whether security is enabled or not. but the clients cannot associate with security enabled
Post in the corresponding new build thread.
This is old. _________________ I am far from a guru, I'm barely a novice.
Hi, all! So I've been using the WNDR3400 router with DD-WRT v3.0-r36079 big (06/01/1 for over a year and it's the most stable router I've ever owned! So good! Literally had been on for over 200 days before. Kind of unbelievable with no hiccups!
However, and I'm not sure if this is setting I can change on the router or a possibly a bug on the build I'm using but I'm only getting 60Mbps download when I'm supposed to be getting 100Mbps. I confirmed it is definitely the router by plugging my modem directly into the PC, however with the router in the mix, I get throttled at 60Mbps.
Any ideas?
I might try flashing the newest build but don't want to if I don't need to!
Hi, all! So I've been using the WNDR3400 router with DD-WRT v3.0-r36079 big (06/01/1 for over a year and it's the most stable router I've ever owned! So good! Literally had been on for over 200 days before. Kind of unbelievable with no hiccups!
However, and I'm not sure if this is setting I can change on the router or a possibly a bug on the build I'm using but I'm only getting 60Mbps download when I'm supposed to be getting 100Mbps. I confirmed it is definitely the router by plugging my modem directly into the PC, however with the router in the mix, I get throttled at 60Mbps.
Any ideas?
I might try flashing the newest build but don't want to if I don't need to!
Thanks!
Best if you ask questions about that router directly in main Broadcom forum, NOT in this thread.
AND
most likely 60Mbps running DD-WRT is all that (480MHz CPU) unit will do across its WAN
AFAIK it only has a 10/100 switch.
A newer build with SFE enabled should give you 'bout 90Mbps
So I've been using the WNDR3400 router with DD-WRT v3.0-r36079 big (06/01/1 for over a year
A newer build with SFE enabled should give you 'bout 90Mbps
36079 should be able to enable SFE on the Basic WAN setup page. But ya there have been a lot of changes in recent builds for it. I'd suggest trying to enable it in your current build, test it for a week, save an nvram backup, then try a latest build (after reading its build thread, per mrjcd) and compare. If you have any issues, reset and manually setup (no backup restore) to retest before posting. If it still has issues, you can revert to 36079 and restore your backup. _________________ #NAT/SFE/CTF: limited speed w/ DD#Repeater issues#DD-WRT info: FAQ, Builds, Types, Modes, Changes, Demo#
OPNsense x64 5050e ITX|DD: DIR-810L, 2*EA6900@1GHz, R6300v1, RT-N66U@663, WNDR4000@533, E1500@353,
WRT54G{Lv1.1,Sv6}@250|FreshTomato: F7D8302@532|OpenWRT: F9K1119v1, RT-ACRH13, R6220, WNDR3700v4
So I've been using the WNDR3400 router with DD-WRT v3.0-r36079 big (06/01/1 for over a year
A newer build with SFE enabled should give you 'bout 90Mbps
36079 should be able to enable SFE on the Basic WAN setup page. But ya there have been a lot of changes in recent builds for it. I'd suggest trying to enable it in your current build, test it for a week, save an nvram backup, then try a latest build (after reading its build thread, per mrjcd) and compare. If you have any issues, reset and manually setup (no backup restore) to retest before posting. If it still has issues, you can revert to 36079 and restore your backup.
Thank you for the quick replies, guys! SFE is actually already enabled. I don't remember enabling it so I'm guessing it was like that out of the box. So yeah, my speeds top out at ~60Mbps wired directly to the router. Is there maybe another option I'm overlooking? Or do you think I should try K3.0 r39572 mega-nv64k (04/19/19) according to the wiki database? I am really happy this router is still supported and this community is still around! Thanks a bunch!
Edit* Also, sorry for posting in the wrong section. Been a while since I've been on this site.
SFE is actually already enabled. I don't remember enabling it so I'm guessing it was like that out of the box. So yeah, my speeds top out at ~60Mbps wired directly to the router. Is there maybe another option I'm overlooking? Or do you think I should try K3.0 r39572 mega-nv64k (04/19/19) according to the wiki database?
Use a latest broadcom_K3X/ build unless there are reports of k3.10 build issues in the forum. Report back in that build thread.
Do you have QoS enabled? I think that may have silently disabled SFE back then... _________________ #NAT/SFE/CTF: limited speed w/ DD#Repeater issues#DD-WRT info: FAQ, Builds, Types, Modes, Changes, Demo#
OPNsense x64 5050e ITX|DD: DIR-810L, 2*EA6900@1GHz, R6300v1, RT-N66U@663, WNDR4000@533, E1500@353,
WRT54G{Lv1.1,Sv6}@250|FreshTomato: F7D8302@532|OpenWRT: F9K1119v1, RT-ACRH13, R6220, WNDR3700v4
Joined: 08 May 2018 Posts: 14249 Location: Texas, USA
Posted: Thu Aug 08, 2019 22:49 Post subject:
jwh7 wrote:
Do you have QoS enabled? I think that may have silently disabled SFE back then...
QoS has always disabled SFE, but it wasn't unloading the kernel module until more recent builds, I think. This is why default is SFE disabled or something. All this flurry of commits with SFE and QoS and stuff....