kruess  Freshman Member

Not really what the endusers would expect from an idle device. USG/ATP's with current load usually do not more than spike above 10-15% and having them really idle they are somewhere below 5% CPU usage. Combine these high idle usage patterns (our 100H was more around 30-35% on idle!) with the various reports of really slow…

Wow, it took us (or the "H"opeless firewall) roughly 3 days to show the wheels of death on the dashboard and the empty services/addresses/etc tables…. wt*

Dave, What a clever decision - Congrats! I'd wish I would not have to deal with that firewall model, but unfortunately, one of our customers got one from his telephony guy… 😬 I just read some Zyxel statement about a feature which will be available by 2026….!!!! 😵 They should have to pay for the pain they are causing by…

Oh man…. this is a storyline for a horror film, but not for some serious business…!!! :-(((

This is already in the forum for a while - without any useful solution… :-( The only ugly solution I found is a reboot of the firewall……. say hello to the terrible H-series launch… urggghhh…

And again a hanging Web GUI on 100H. The error code seems to count +1 for each login attempt (20001, then 20002, etc). This early "H" series launch is killing Zyxel reputation quickly… 💩

Still happens with firmware 1.20-2… 😬

Only a reboot, initiated through SSH was fixing this behaviour.

Same behaviour here on a 100H with Error code 20001, 20002 or 20003. Prior to this, we tried to disable some expired security services and got an "invalid version" error when trying to save the simplest config change on the respective service. Maybe it's related with the 'get-device-config' error, maybe not… Still "H"…

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… :-(((