I can "break" Guest VAP on 36410 more than one way...
with no IPv6 (router power cycled after configuration changes) it shows up but just connecting to it seems to crash it (DNSMasq still in use but not configured for ipv6)
with IPv6 enabled (again after a power cycle) the SSID doen't even show up.
i configured a guest vap first without ipv6 and later added ipv6. I think I added dnsmasq and definitely added dhcp6c with ipv6.
to get ipv6 with a guest VAP I used multiple sources. Most of the wiki and forum posts are listed below. As this may not be useful to anyone reading this, I've listed my guest vap, ipv6, dhcp6c, dnsmasq configs that work on 33535 below with some redactions out of privacy concerns:
Current Bridging Table
Bridge Name STP enabled Interface
br0 no vlan1 eth1
From Services
DHCP Server
Use JFFS2 for client lease DB(Not mounted)
Use NVRAM for client lease DB
Used Domain LAN & WLAN
LAN Domain xxxx.lan
Additional DHCPd Options
DNSMasq
DNSMasq Enable
Cache DNSSEC data Disable
Local DNS Enable
No DNS Rebind Enable
Query DNS in Strict Order Enable
Add Requestor MAC to DNS Query Disable
Joined: 24 Feb 2013 Posts: 1634 Location: Belgrade
Posted: Tue Jul 31, 2018 19:57 Post subject:
If I were you, I would do it like this:
1) Reset to defaults (erase nvram)
2) On default settings add VAP
3) Reboot
4) See if both wifi interfaces broadcast (shows up) and if you can connect (both AP and VAP) to them...
then add complexity (ipv6 etc) and search where problem is...
if VAP doesn't work with 4 steps above then it is "VAP bug"... otherwise problem is somewhere else...
1) Reset to defaults (erase nvram)
2) On default settings add VAP
3) Reboot
4) See if both wifi interfaces broadcast (shows up) and if you can connect (both AP and VAP) to them...
then add complexity (ipv6 etc) and search where problem is...
if VAP doesn't work with 4 steps above then it is "VAP bug"... otherwise problem is somewhere else...
Thank you for your comments. As it turns out, your suggested sequence is mostly how I did it. I suspect that I didn't notice that connecting to the VAP didn't work initially since I noticed later that my client rolls over to the non VAP network once the connection to the VAP fails and disappears.
What could myself or other users do that is more helpful than what I detail below?
FWIW, this feels like a combination of issues such as poor configuration on my part (that still works on 33525 but breaks 36410), more than one bug manifesting as VAP interoperability (the observed difference in behavior between using ipv6/dnsmasq and not using ipv6), or a combination of both.
Assuming any troubleshooting I'd do is considered helpful in this community and given the complexity of my set up, I think a more detailed suggested configuration sequence is necessary to make it worth the effort to draw some conclusion about the result.
When I do a manual "from scratch" set up starting from a configured build, my gui configure sequence is something like:
1. choose reset to defaults and upload new build
2. hardware clear nvram via wps button (a RT-N66U specific method detailed on the wiki)
3. choose username and temp password after boot
4. set https management and unset http management
5. save and reboot router via GUI
6. set permanent password
7. save and reboot router via GUI
8. configure setup, basic setup, items under network setup (I use non default IP addresses) including use DNSMasq and ntp and save
9. configure 2.4 GHz wireless basic settings, physical (I disable 5 GHz) and guest VAP then save
10. configure wireless security (WPA2 personal AES) for each AP (including 5 GHz) and save
11. configure Setup, Networking, Bridging, networking configuration for wl0.1, and DHCPD and save
12. configure Services, DNSMasq (no additional options at this point) SSHD (auth key, no password login), enable syslogd, and save
13. configure Security, firewall, limits on ssh, telnet etc., enable log at high level for accepted connections (I'll use this in a wol script from an internal usb microsd card - a RT-N66U feature - mounted on /opt later...) and save & apply
14. reboot router via GUI, take a quick look and fix anything I missed, and then power cycle router
15. test Guest VAP
16. move on to configure static hosts, DDNS, IPV6, USB for internal microsd card, etc.
Is repeating this really going to help a dev debug the issue?
I'm 50.05% certain that if I do up to step 15 again, VAP will start up but not connect and crash as I've described. I'm 87.342% certain that if I then power cycle the unit continue with step 16, the guest VAP will not start up as described before.
Given the sequence above, I suspect I should wait and "let the horses work as their heads are bigger than mine."
Are you making fun of me with these "%"?
Just tried to help you, no need for vanity and sarcasm...
I know you thought you were trying to help me. I didn't ask for help. When you write:
Mile-Lile wrote:
you have to erase nvram and manually enter configs, do not restore old nvram backups... tehn report if not working... 99,9% it will work, if you just do it as told...
(bold my emphasis)
in response to a bug report it generates this kind of emotional reply especially after you choose to ignore some of the new build thread instructions here.
If you want user to reset before posting an observation in the thread, it will help to request that in the opening post given we all ignore the instructions and don't do as we are told to various extents.
FWIW,
I reset/retried 36410. Using as many default settings as possible and still have a guest VAP, I can get the VAP up, connect, browse, etc.
However, I lost the VAP SSID just by changing the 2.4 GHz wireless physical from "mixed" channel 6 to "NG mixed" channel 11 (save and apply). It comes back after a reboot and I can still connect to the VAP but this seems kinda fragile.
I can go back and forth with the above settings on 33525 (save & apply, no reboot) and not lose the guest VAP.
If there is something specific I can test, please feel free to ask.
I will note that 36410 also did not fix my WNDR4000 VAP (specifically, it broke the VAP that was working with the 36404 test build), including trying the usual steps to fix it; restarting wlconf and clicking 'Apply' on the Wireless GUI page. The former fixed the BSSID, and even retained over a reboot, but I could not connect (Win10 nor Android 8.1) to wl1.1, but wl1 was fine. BS didn't say much about it. This is a CB+(AP+VAP) w/ IPv6 disabled, and using the dnsmasq method.
Anyway, I still need to reset and test again, but won't be able to until next week. _________________ #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
The purpose of this post is to verify what I observed before.
That is: changing the 2.4 GHz wifi from "Mixed" channel 6 to "NG Mixed" channel 11 makes the guest VAP non-functional. This time I tried to be a bit more careful about doing so. The short of it is that I can reproduce this but there was an unintended difference compared the first time. The difference is my client reconnected on wl1 (5 GHz) after the change to the 2.4 GHz settings.
Pseudo transcript:
client = ubuntu 18.04 4.15.0-29-generic #31-Ubuntu SMP
33525 = previous build on Asus RT-N66U
36410 = build being tested
I tried to used ">" for multiple events on a given device or screen. Not every thing I did on the client is shown, but every configuration change I did on the router should be here.
33535: hw nvram clear
33525: load 36410 w/ reset
36410:
> hw nvram clear
> set user psswd
> services syslog/klogd save
> security, firewall log, high dropped, rejected, accepted enabled save
client: telnet 192.168.1.1 -> connection refused
36410:
> wireless, virtual interfaces, add, ap isolation, unbridged, net isolation, forced dns redirection, optional dns target: 208.67.222.222, IP address: 192.168.2.10, subnet mask: 255.255.255.0 save
> setup, networking, no wl0.1 in DHCPD, apply
> setup, networking, DHCPD, wl0.1, save, apply
> admin, gui reboot
client: telnet 192.168.1.1 -> connected
client: connect to VAP (via GUI) SSID: dd-wrt_vap, aka wl0.1
#VAP connected, can browse WWW, seems to work fine
client: iwlist observed no wl1 (5 GHz)???
#a bug for another day...
client: disconnected VAP
client: iwlist observed wl1 (and client connected to wl1 now)
#well ain't that special
36410:
> wireless, wpi wl0, change network mode from mixed to ng-mixed
> wireless, wpi wl0, change wireless channel from 6 to 11
client: iwlist shows wl0, wl0.1, wl1 still visible
36410: wireless, apply
client: iwlist SHOWS wl0, wl0.1, wl1 still visible
#WHAT??? wl0.1 is still there but VAP not shown on client GUI!!! Is it just "hidden" from view for my inconvience!!!
#FLIPPIN PUTERS!!! I hate em
client: nmcli d wifi list
IN-USE SSID MODE CHAN RATE SIGNAL BARS SECURITY
dd-wrt Infra 11 195 Mbit/s 100 ▂▄▆█ --
* dd-wrt Infra 36 195 Mbit/s 63 ▂▄▆_ --
client: nmcli d disconnect wlp2s0
Device 'wlp2s0' successfully disconnected.
client: nmcli d wifi list
IN-USE SSID MODE CHAN RATE SIGNAL BARS SECURITY
dd-wrt Infra 11 195 Mbit/s 100 ▂▄▆█ --
dd-wrt Infra 36 195 Mbit/s 74 ▂▄▆_ --
client: nmcli c up dd-wrt_vap
Error: Connection activation failed: The Wi-Fi network could not be found
#ohhh, well mabey I don't hate em so much... verified what I observed before
client: configure force connection on 2.4 GHz via GUI, disconect,reconect
client: "nmcli d wifi list" still does not show VAP
client: configure force connection on 5 GHz via GUI, disconect,reconect
client disconnect, nmcli c up dd-wrt_vap
Error: Connection activation failed: The Wi-Fi network could not be found
At first I thought I couldn't reproduced what I observed before as I can see the wl0.1 via iwlist. However, I cannot connect to the VAP after changing the wl0 from "Mixed" channel 6 to "NG Mixed" channel 11.
