Comments
-
Hi @Zyxel_Charlie , I haven't tested the firmware from your message yet, because I've been trying, unsuccessfully, to apply a hash in V4.39(AAKZ.0). With each hash attempt I get an error in the logs (but none when setting the hash or applying profiles). The logs show an alert and error, something like the following :…
-
Hi @Zyxel_Charlie . Aplogies for the long delay in replying. I just tested this in V4.39(AAKZ.0) and I see that it's still an issue. I also don't see it listed as a known issue in the release notes for 4.39? As far as using the GUI, that would be no different than simply using wpa-psk at the command line (or in a script,…
-
I think seeing if others agree is good, but I feel like the real problem isn't conveyed. It's the password prompt that is presented when entering enable and requires a null entry (and doesn't accept valid passwords) that's the entirety of the problem. There should either be no password prompt, or the prompt should accept a…
-
Switching back and forth between admin privilege without a password is understandable, but, why prompt for a password at all? It's confusing since it doesn't even accept a valid password. No password prompt should appear when the enable command is entered.
-
I first identified these issues on my lab machine, and confirmed on a production switch. In the lab, it's an out of box configuration upgraded from 2.40(AAZI.1) to 2.40(AAZI.2)C0 to V2.40(AAZI.2) to V2.50(AAZI.0). What follows is a copy paste of the terminal commands and output. Note that the username isn't showing via the…
-
I highly recommend using IKEv2 instead of L2TP. In either case, you'll need to make sure that the encryption and authentication proposals that you are using in both Phase 1 and Phase 2 (Gateway and Connection) match those available on your client device. If you are using any Windows based devices, you will have to…
-
Hi Dudley, I don't know if you're still having this issue or not, but I have had this issue on a multitude of sites, primarily on the wireless connected clients. In each case, the resolution has been to increase the session-limit limit from 1000 to at least 4000, sometimes (though, rarely) higher. Keep an eye on it,…
-
Oops. I forgot to include that, after logging in with the default login I and password, it automatically prompts to change the password, which is good, but the new password field does not mask the new password - only the confirm new password field does.
-
I agree that, at the bare minimum, it should be applying the last successful running configuration. I'd be surprised if it wasn't doing that already, though, unless, perhaps, the config you're currently using is failing to load properly in 4.33 and generating errors? Incidentally, I haven't had a configuration fail, yet,…
-
I thought this was in pre-release pending beta testing?
-
I recently had the same problems on two different GS1900 series switches in which the client devices were not getting IP addresses from the USG devices the switch was connected to (even though the USG was receiving the request and assigning an IP). In both cases, the solution was to complete the VLAN configuration, save…
-
@Snowtoy Are you using a mac or a PC?
-
@ChristianG were you also seeing the wireless clients presenting with either failures to connect, or (on iphones) with a prompt to re-enter the password which, when entered, was still rejected with an authentication failure until the router was rebooted?
-
These were all USG40W systems that had been recently been configured for Static WAN IP addresses. Then, some weeks later, the 4.32 update was applied. In all three cases, the systems had been up and running since the change to static IP addresses and not rebooted. When the 4.32 update was applied, the wan interface had…