If you do not need to accept INCOMING connections(a connection coming from WAN to ZONE_xxx) then you do not need a rule allowing traffic from WAN. If only traffic to WAN was allowed, replies from WAN would be dropped? You said: I'm assuming that both traffic from and to WAN must be allowed for internet access. I would suggest setting them to 'Internal' so you don t have to mess around with setting routes for everything, you can use firewall/Security Policy to control access to other zones/networks, MUCH easier. If they are set to general, that means the built-in 'internal' routes are disabled and you will need to manually setup routes for these VLANs to all other networks including the internet. Also you said you have all VLANs set to 'General'. You said you have DHCP disabled on the VLANs, I assume you are manually assigning IPs?ģ. EDIT: actually it looks like ALL of your physical eth_xxx interfaces are in the same subnet, you need to change this I noticed your eth_wan1 interface(10.1.10.2) is in the same subnet as your eth_lan1 interface(10.1.10.3)- why? This is going to screw up routing. You should then be able to re-add HTTPS to the WAN Service Group.In the doc linked above, you stated: Still none of my devices connected to the switch (or directly to the USG40) gets a connectionġ. It’ll take the newer firmware in the standby partition as active, putting you on the latest release.Īs of this time/date, Zyxel doesn’t have a fix yet but you’d want to repeat this procedure to manually update the fix firmware once it’s released.

If the device doesn’t auto-reboot, afterwards on your own schedule, reboot the device. The Zyxel should start the upload process (be patient, it’ll take a while) and it shouldn’t reboot on you (I’ve had several USG40’s that rebooted regardless). If you need to update, upload the firmware manually to the standby partition with the option not to reboot when prompted. Compare version numbers for the active and standby partition. I find the Cloud Update in the GUI misreports highest firmware versions.Ĭonfirm the actual version for your product by logging in to, accessing My Devices, and attempt to download the latest firmware. My Advice: Don’t trust the Cloud Update procedure inside of the device. Take the necessary remediation steps or prove that your device wasn’t affected. Walk through the remediation article I cited above to see if your Zyxel product was affected by the attack. Your Zywall is now protected from the attack. Strike the OK button and the configuration will be saved.

Zyxel usg 40