Комментарии
-
I've seen this before, I think it was on the regular content filter, tho, not the DNS. Seems to vary on the amount of oooo's in google. I never did get to the bottom of it. No one ever complained about anything not working.Раздел: www.goooooooooooooooooooooooooooooooooooooooooooooooooooooooooogle.com Комментарий от electsystech 18 янв
-
I would try blocking port 80 UDP as well.Раздел: USG FLEX 50 Content Filtering not working with chrome browser Комментарий от electsystech 18 янв
-
The client is on a cellular connection and we determined the attack used up all the data. It's on tmobile and once you go over your data plan, it throttles the speed to 128kbps or so, making the internet unuseable.
-
I'm getting the 504 Gateway timeout on a USG 20VPN router that had the 5.36 Patch 2 applied last week. I suspect there's another vulnerability or the patch wasn't completely effective. I'll have to do more testing.
-
So far we've been able to get into the router after a restart and then run the firmware update. It's best practise to keep download a copy of the startup-config file for a backup.
-
See concept description here:
-
+1
-
You need to add *verizon.com *tello.com *att.com You will have to watch the logs under Monitor>Logs>Category>Blocked Websites to see what else is being blocked. Like he said, there may be many other domains that have to be allowed for the site to work.
-
This is now 3 years later. What's the plan for this enhancement?
-
That's the point, it's supposed to be blocking all internet access. I setup another policy like your screenshot shows and it's still working. I had to add more ips to the blocked ip range to get adobe blocked. It needs to be blocked by domain name not ip because the ips will keep changing.Раздел: Why doesn't Content filter block adobe.com on USG20-VPN? Комментарий от electsystech октября 2022
-
PM sent with config file.Раздел: Why doesn't Content filter block adobe.com on USG20-VPN? Комментарий от electsystech сентября 2022
-
Update. If your router is running firmware 4.35 firmware, please note that NATing configuration looks a bit different. Here's an update: In cases where the devices behind the Zyxel hold private IPsbecause they required firewall protection. Typically this method is used when servers are connected behind the Zyxel. Method…
-
You can also reference this article: https://businessforum.zyxel.com/discussion/1324/how-to-route-multiple-public-static-ips-with-zyxel