WebWorks  Freshman Member

All these devices have a public IP, DNS-Name like xxxxx.customer.com and a changed https port. But Access open (now closed). I had these Problems with VPN 100, Firmware V5.37(ABFV.2) Other User mentioned Problems with other Devices on Firmware V5.38 I checked other devices, Flex 200 and 500 on Firmware V5.39, There where…

Another remark to zyxel: I use many VPN100, because of VPN Performance and the use of L2TP. The existing Flex Series use the same interface and functionality like the VPN Series but lack of VPN Performance. So I wanted to implement an new Flex 100H with enhanced VPN performance. Bad Idea, Registration to Nebula, missing…

Here a basic follow up on this case: VPN100 V5.37(ABFV.2), lastest Version for this Device. Europe, time in UTC+1 and european summertime, attack monday morning beween 2 and 6am. Attacked many VPN100, found the "config file" zzz1.conf on all these devices with this timestamps. in one device I found a User account and a SSL…

Here a follow up. On the night to monday, someone tried to gain access to many zywalls vpn100. Starting at 2h for about 4h utc+1. I found traces in many devices. First sign is a configfile with the name zzz1.conf uploaded to the zywall. In one case they where successfull to compromise the zywall and to get access to the…

Thanks for the long and complete answer. I figured about the same. Now I solved the problem with a internal website, based on iis and a wol asp net script. Runs like a charm and avoids all the problems.

This means a security rule from IPSEC_VPN TO ZyWall, VPN-Range TO Lan1Subnet, Any_UDP Allow should solve the problem?

This link just saved me from "rebuilding" 3 USG110. Procedure is logic and works perfect. Hints, default Com Settings are missing and use putty.exe as terminal BaudRade 115200, Data 8bit, Parity none, Stop 1bit, FlowControl none. @Zyxel. These problems are often triggered by the "new" password change requests. Built in…