bbp  Ally Member

I'm not going to risk it yet, until they have all hands on deck (in about an hour or so). Thanks for warning! Appreciated.

I'll join the party…

Yes, device was previously registered. Sent you serial and MAC in private message.

Hi Peter, I have no problem reaching he.myzyxel.com. (traceroute -n -p 443 -T he.myzyxel.com) Problem is target responds with 'status code 500' when 200H is querying it via API. That's internal server error (codes 5xx) on target side.

You need to improve on that. People rely on security services.

These days both POP3 and IMAP are encrypted too. @HUBERTKASPRZAK needs to configure "SSL inspection" for 200H to be able to inspect encrypted traffic.

Yes, from my observation, boot times have steadily increased since 1.10. H series doesn't boot faster than previous models, contrary to what Zyxel advertised.

Interesting 'workaround'. Thank you Peter.

It seems if "Certificate for VPN Validation" is set to "Auto" it gets confused if there are more than few generated certificates. Manually selecting certificate solves that issue.

LAG is not yet supported. LAG will be added in 1.40 firmware according to Zyxel.

Can't backup private keys either, nor restore for that matter. Permissions set to 0600. Uploaded keys get deleted immediately. So if you have a wildcard cert signed by legit CA and private key and you combine them into Binary PKCS#12 cert you can't install it. No import like on other Zyxel devices. I mean you can install…

Thank you for the help, Kay.

From PKI logs after trying every possible cert I got hands on. Can't decode certificates to import. Decode imported certificate "xxxxxxxxxxxxx.pem" failed Decode imported certificate "xxxxxxxxxxxxx.pfx" failed etc, etc…

Why is that relevant? The only reason I mentioned it is to assure that certificate is OK, and that they correctly display from/to dates, not only on other Zyxel devices (GS1900-16, GS1900-24E, both on firmware 2.80, 200H, on 1.21 and VPN100 on 5.37) but also other brands. The only device that I have and it doesn't display…

Also, if you change network mask, it will wipe out all reserved IP entries and applied default DHCP setting, regardless if DHCP pool was still within the specified network subnet.