kruess

You've got a nice list, here :-/ and unfortunately, it's still only the cap of the iceberg. We're fighting with one of those devices at a customer's site, too, and whatever comes to your mind to get things going: "sorry, you cannot do that!". 😠

Yeah, it's awful to work with this GUI. So many missing things, unexpected behaviour, instabilities - even instabilities of the device itself, not only the GUI…. :-((( It's kind of pre-alpha state, but already sold as the gadget. 😬

Hi Jeff, thanks for the hint, I've managed to get the most urgent settings back in place, now, following your examples…

Hi Emily Thanks for the code snippets - I've been able to adopt those to our urgent DHCP fine-tuning requirements. Interestingly, the "user-defined" options only allow 3 params (code#, type, value), but usually (and also on the ATP/USG series) that one consisted of 4 params (name, code#, type, value). Also, I could not…

Ufff, and when will v1.20 be available? Will it also contain the DHCP Options? What about a more condense layout? Currently, the GUI is loosing soooo much valuable space by all that empty room (ie between the lines, etc) and requires much more scrolling compared to the GUI of the previous models (ATP).

Wow, what a bad start for the new GUI… how can Zyxel go forward with such a minimal and cumbersome management GUI… :-(((

Hi, we've observed troubles while updating HA pairs, too. USG's in those cases. We've been able to reduce the risk by rebooting the active device, waiting for the pair to be in-sync and again boot the other, now active device and wait again for sync'ing and then initiate the upgrade. Doing so, the upgrade seems to be…

Hi, did you get any further with that investigation? We have been observing similar behaviour in the past, too. But it's hard to analyse with ~20 active IPSec VPN's.