Posted: Sun Oct 22, 2017 22:22 Post subject: password issues with virtual interface
I am currently using DD-WRT v24-sp2 (build 21061) on a Linksys E1200 router. I tried adding a virtual interface yesterday, so that some newly-purchased IOT devices could be separated from my main network. I followed the recommended steps to set it up, then tried to connect to the new SSID with my cell phone, in order to configure the IOT gadgets. I discovered that I could connect to the virtual interface without a problem if I had WiFi security turned off, but using WPA2 resulted in an error message stating that I had entered the wrong password. I made the DD-WRT setup page display the password, and made sure to enter it exactly. I still got the bad-password response. I can connect to the physical interface's SSID without a hitch, so the issue appears to be a DD-WRT bug, not a hardware or setting error. Is this a known problem? Is there a known work-around? I don't want to leave the secondary SSID wide open. I have security mode set to WPA2 Personal Mixed, and encryption set to TKIP+AES, at a friend's suggestion.
Sorry, not an answer or fix for your issue, but I've had the same experiences lately, though with absolutely current firmware (as of 10/20/17). I bought a Linksys R8000 and the physical interfaces connect with no problems. The minute I added virtual interfaces I couldn't log into some or all of the physical and most of the virtual interfaces. I found I had to disable security on most, if not all, interfaces to get connectivity. It was a constant battle to set config settings, reboot, reboot, etc. to get connectivity to the interfaces that worked just minutes before.
I'm scrapping the R8000 in favor of an R7800 (due to suggestions and reviews), but fear the problem is more related to the Broadcom chipset than the router release. I'll check in on this thread periodically as it'll probably be relevant in the next few weeks as I fight with my new R7800.
After spending several days struggling with the settings, and trying multiple builds, I finally flashed Tomato firmware. It worked on my first attempt, confirming that the problem is a DD-WRT bug, not a hardware issue.
It was probably a dd-wrt bug but you were running a very old build, don't blame dd-wrt if you don't update to the latest.
See my signature if you are still interested in running dd-wrt. 33525 is good, the next to builds have had numerous problems reported. See the build threads here on the forum. _________________ Before asking a question on the forums, update dd-wrt: Where do I download firmware? I suggest reading it all.
QCA Best WiFi Settings
Some dd-wrt wiki pages are up to date, others are not. PM me if you find an old one.
Atheros:
Netgear R7800 x3 - WDS AP / station, gateway, QoS
TP-Link Archer C7 v2 x2 - WDS Station
TP-Link TL-WDR3600 v1 - WDS Station
TP-Link 841nd v8 - NU
D-Link 615 C1/E3/I1 x 7 - 1 WDS station
D-Link 825 B1 - NU
D-Link 862L A1 x2 - WDS Station
Netgear WNDR3700v2 - NU
UBNT loco M2 x2 - airOS
Broadcom
Linksys EA6400 - Gateway, QoS
Asus N66U - AP
Netgear WNDR3700v3 - not used
MediaTek
UBNT EdgeRouter X - switch
Posted: Sat Jun 29, 2019 16:23 Post subject: Invalid Password on virtual interface
I'm using a DLINK DIR-880L with firmware DD-WRT v3.0-r39715. The issue appears to still exists but isolated to the 2.4GHz interface. I have it setup as a repeater and then created a virtual interface with a different SSID. I'm using the same security alg WPA2-PSK-AES with the same shared key for both primary and virtual interfaces. The router connects correctly to my main router and gets an IP address. When I try to connect from other devices to the virtual SSID I keep getting invalid password. I tried disabling security on the virtual interface and I was able to connect successfully to it. I tried doing the same setup on the 5GHz interface and had no issues so it appears to be a bug on the 2.4GHz side only. I also tried setting up as a repeater-bridge on both 2.4GHz and 5GHz and did not have any of the invalid password issues. I've tried a few more recent firmware versions and still the same problem.