Comments
-
Trial Licenses are usually device based, not organization based. Regarding purchased licenses, please wait for a reply from a Zyxel Employee or professional user.
-
Check the information about "End of Life" for Zyxel products. Even if the product is discontinued, there may still be a "grace period" of support and updates: https://www.google.com/search?q=zyxel+vpn100+end+of+life
-
You probably need to reset to factory defaults: If that does not work, contact vendor in case of hardware claim.
-
English (global) version can be found at this link: (Sorry, I do not know the topic well enough to contribute.)
-
First of all, you will need to unlearn the general meaning of "Whitelist" in a Zyxel/USG environment. In most Zyxel (USG) devices, "whitelist" refers to a list of e-mail addresses from which traffic is allowed. In this IP address access scenario, your main focus will be Security Policy Rules. Look up Security Policy in…
-
Thank you for the extra information. Looks like useful info. I admit that I personally do not know where to look for the cause of the problem now, and I do not have more to suggest than to back up the device config files and reset the whole device to factory defaults, maybe even reinstall the firmware or downgrade and then…
-
Very well, so this is about quite outdated Anti-Malware signatures from November 2023, while at the same time you have got another ATP200 successfully updated to new signatures (March 2024). And as you said, neither reboot nor refreshing services makes any difference. By the way, does this include manual request for…
-
Could you describe the problem in more detail? The problem seems unclear to me. What is the expected result? I do not see a description of any error message.
-
I am not an expert, but your log in the screenshot only contains info about normal packets. You need a debug log, bigger/longer than the normal information log. Anyway, I defer to the Zyxel team members for further assistance. Maybe you will be asked to activate some form of Zyxel Support access in your firewall…
-
I don't know enough about the procedure for specific models, I have only had previous experience with ZyWall 5 and USG 60, but that is now in the past and I am no longer responsible for following up on any Zyxel devices at my workplace. I can only suggest looking at other issue contents, unless someone from the Zyxel team…
-
Unless there are some missing or unset settings to enable correct communication in your terminal software, I must defer to the Zyxel team members for more precise troubleshooting of your issue. Sorry for not being able to help any further.
-
Looking at your last security policy rule entry, it looks like all traffic is blocked: Action Protocol Source Destination Port dst Schedule Description Deny Any Any Any Any Always Default rule I am not 100% sure, but it looks like there is a default rule to block all traffic. Maybe it needs to be modified to block only…
-
(copy-pasting your log output for easy reading) Log entry Date Log Time Source policy type Source address Source port Destination address Port Rule descriptor (name, type, number) Rule identifier Rule port type Rule action 2024-02-20 16:24:11 Security policy 192.168.1.148 56671 216.239.32.117 443 Rule…
-
Not sure how it works on Linux, part of the output message saying /dev/ttyUSB0 makes me think that maybe it does not try to communicate on COM1 (default serial port)?
-
Good question, I don't know. I defer to the ZyXEL team members for an authoritative answer.