Posted: Sat Sep 25, 2021 20:09 Post subject: [SOLVED]Linksys WRT320N VAP issue
Hi,
I was trying to solve an issue and just found another and I'm starting to get out of ideas.
I've a WRT320N with DHCP off, connected to a main WRT610N with DHCP on.
I'm trying to add a guest network at the WRT320N but without success.
At the WRT320N I need "Assign Wan Port to Switch" and CH11.
From a previous post, I was told that last known "Assign Wan Port to Switch" was r46788. So, I've updated from r14829.
1st issue: I've immediately notice (with a WIFI analyzer) that the router is always stuck at CH1, no matter the channel choice
2nd issue: I've made several attempts with builds mentioned at the forum and I've found r26138 in which the channel really changes and also possesses "Assign Wan...". But if I put a password ao the guest network, I'll no longer access it and also after a while the SSID just disappears.
I've only installed K2.6 builds so far and I can tell that even with these latest ones, the CH1 stuck issue also occurs.
Would it be possible to have some hints to overcome these problems ?
The good news is that I've now a masters on how to unbrick the WRT320N
Thanks.
Joined: 08 May 2018 Posts: 14126 Location: Texas, USA
Posted: Sat Sep 25, 2021 22:16 Post subject:
Is it a matter of the channel not being selectable at all, or is it a matter of being able to change to channel 11 in the webUI and the router broadcasting on channel 1 only? I found the following discussion regarding this issue, but it doesn't seem that it was addressed (I didn't read the rest of the entire thread):
All I know is (especially on Broadcom), you select the channel width, save; extension channel, save; select channel, save & apply on the main AP settings. I do not use VAPs for guest network access, so I do not know what carries over from the main AP settings or not without looking at the source code.
The other issue with VAPs seems to require startup commands so that the VAP works properly with authentication (this has been mainly discussed on Broadcom ARM/Northstar devices).
I have not tested K2.6 builds in a while, so I may have to consider that, but it might be time to consider one of two things: Switching to K3.x builds or converting to an E2000. The first option would be easier _________________ "Life is but a fleeting moment, a vapor that vanishes quickly; All is vanity"
Contribute To DD-WRT Pogo - A minimal level of ability is expected and needed... DD-WRT Releases 2023 (PolitePol)
DD-WRT Releases 2023 (RSS Everything)
----------------------
Linux User #377467 counter.li.org / linuxcounter.net
Hi,
Thank you for your fast reply.
Regarding the channel, you can select it and apply changes but it won't change from CH1 at the spectrum. From what I've seen by testing several builds this is being around for several time.
Regarding K3.0, that was a possible approach but I believe that I need the "Assign Wan..." feature. Please correct me if I'm wrong but I have several routers "cascading" and with all the ports occupied. Since only the main one is assigning DHCP, I was taking advantage of this feature, which I think no longer seems to be support "Assign WAN port to Switch" feature removed; likely no longer required.".
Is there another way to assure this behavior ?
I'll read the suggested posts in the meantime.
Thanks
Hi,
I've followed the advice and installed v3.0 r47495 mega two weeks ago. This solved the "Assign WAN port to switch issue". Since then I've been trying to put the Guest network to operate but I keep getting "Connected without internet". IP for Guest network checks OK.
I'm using wl0.1 unbridged and I've inserted at firewall: "iptables -t nat -I POSTROUTING -o br0 -j SNAT --to $(nvram get lan_ipaddr)".
What am I missing ?
I've notice that this built doesn't provide the "Masquerade / Nat" feature at "Network Configuration wl0.1". Could this be related ?
Thanks
Hi egc,
I've tried workarounds 1, 3 and 4 (skip 2 because I have BROADCOM BCM4716 chip rev 1). Still no luck.
Main router: stock firmware - wireless with internet
Cascade router: v3.0 r47495 mega - wl0 wireless with internet (same range of IPs as main router); wl0.1 - wireless without internet at different range of IPs.
Joined: 18 Mar 2014 Posts: 12837 Location: Netherlands
Posted: Thu Oct 21, 2021 9:18 Post subject:
I just checked with my own E2000 (which started life as an WRT320N)
Reset to defaults
On Setup Page (these are instructions to setup as a WAP: https://wiki.dd-wrt.com/wiki/index.php/Wireless_access_point ):
Disable WAN
Set Local IP address in range of primary router, e.g. my primary router is 192.168.0.1 so I choose 192.168.0.2/24 (must be outside DHCP scope)
Set Gateway and Local DNS to primary router e.g. 192.168.0.1
Disable DHCP
On Wireless page:
Made an unbridged VAP as outlined in the Document I send, I choose 192.168.13.1/24 as IP address
Save and Apply
On Wireless security page:
Set usual security WPA2-PSK/128 AES
Save and Apply
On Networking page:
Scroll to the bottom and make a DHCP server on WL0.1
Save and Apply
Administration Commands:
Add the NAT rule as outlined, and Save Firewall
Hi egc,
I think I've finally managed to put the VAP to work.
What I've done:
1) Installed "dd-wrt.v24-47581_NEWD-2_K3.x_mega_wrt320n"
2) From https://wiki.dd-wrt.com/wiki/index.php/Wireless_access_point:
Services -> Services tab
DNSMasq: Enabled (even without additional DNSMasq settings)
3) From your doc:
Removed from firewall command: iptables -I FORWARD -i wl0.1 -d $(nvram get lan_ipaddr)/$(nvram get lan_netmask) -m state --state NEW -j REJECT
Conditions 2) and 3) were mandatory after having installed 1).
Without 2) no IPs at guest network (simply won't connect).
Without 3) no Internet at guest network.
Now still needs further testing but seems to be working, even without any workaround for Broadcom.
Thank you and the other members so much for all the feedback and support.
[jwh7 - link edit]
Joined: 08 May 2018 Posts: 14126 Location: Texas, USA
Posted: Mon Oct 25, 2021 15:12 Post subject:
Sorry for not seeing the obvious. For the VAP, you do need dnsmasq enabled to enable the VAP's dhcp server, which can be enabled under multiple dhcp servers. _________________ "Life is but a fleeting moment, a vapor that vanishes quickly; All is vanity"
Contribute To DD-WRT Pogo - A minimal level of ability is expected and needed... DD-WRT Releases 2023 (PolitePol)
DD-WRT Releases 2023 (RSS Everything)
----------------------
Linux User #377467 counter.li.org / linuxcounter.net
Hi,
I'm now overcoming some frustration because it seems that I've spoken too soon.
Well, I've just had an unexpected reboot and lost all the configurations.
After several hours more trying to get the VAP to get ethernet access, this was what I've found so far using r47581 v3.0 mega:
a) The way to get VAP ethernet access was not using multiple DHCP and just following this post: https://forum.dd-wrt.com/phpBB2/viewtopic.php?p=1047143#1047143 - in fact, just don't mess with the Networking Tab
b) The unexpected reboot is being generated whenever I try to enable QOS at NAT/QOS tab and give priorities to both wireless interfaces. The router just reboots to default settings.
I think I can say again that VAP is working (without any Broadcom workaround) but I would like to understand why the multiple DHCP method don't seems to be working (it provides VAP IPs but no ethernet connection). Any thoughts ? I believe I've been misled at my previous post with the firewall rules because I've also tested this latest method along the way and it may have kept VAP running until reboot.
Also, anyone have messed lately with QOS, just to check ?
Thanks.
Joined: 08 May 2018 Posts: 14126 Location: Texas, USA
Posted: Fri Oct 29, 2021 22:27 Post subject:
Yep, good ol mrjcd knows his stuff. And I doubt much of that has changed over time on how to do things. This is why I am looking at reviewing some of the wikis and such. Lots of misinformation running around, even some of my own doing Hopefully, that has it sorted and solved for good. _________________ "Life is but a fleeting moment, a vapor that vanishes quickly; All is vanity"
Contribute To DD-WRT Pogo - A minimal level of ability is expected and needed... DD-WRT Releases 2023 (PolitePol)
DD-WRT Releases 2023 (RSS Everything)
----------------------
Linux User #377467 counter.li.org / linuxcounter.net
but I would like to understand why the multiple DHCP method don't seems to be working (it provides VAP IPs but no ethernet connection). Any thoughts ?
A unit in WAP mode generally will be put in 'router' mode so that is main reason some the other GUI stuff don't work.
AND
a VAP on a WAP you must use DNSMasq (that is what does DHCP) but only with it 'Enabled' ...all other DNSMasq junk left turned off.
I have that post bookmarked and check to see if it still works every few years with new DD-WRT builds
prolly 'bout time for me to check again before too long
glad you got it sorted
ps -
some will tell ya to leave it in 'Gateway' mode but I never seen that point....it is a WAP within your own network...ain't NO need for any other type firewall or other junk