PeterUK  Guru Member

Does the aruba ap12 support VLAN?

You need to run this in console after addding it to the Forbidden: debug content-filter https-domain-filter cache flush https://community.zyxel.com/en/discussion/16046/content-filter-cache-flush-on-change-to-profile

Yes I get now the cache has to have a allow mainly for the content filter category or it be looking up all the time! so one quick fix would be to have the debug command run on a change to profile.

The LAG on Zyxel current design with say two ports is limited rate as one port. I would also expect the SPI to be a min of 2600Mbps

Done a video of of the problem so if you setup a content filter and then someone goes to a site which you then want blocked the site will still be allowed under the content filter cache until you run the debug command. Really what should happen is if the site is not blocked or allowed under all the content filter rules it…

So for anyone following or has the same problem lets take nordvpn.com or www.nordvpn.com you don't put in forbids nordvpn.com you can put in www.nordvpn.com but then this does not block nordvpn.com you put in www.nordvpn.com nordvpn.com and this does not bock nordvpn.com until you run debug…

By default its 1370 so someone changed it... 

Yes but it's the idea that I could not need to use the debug command when I change back the grc3 profile with *.grc*.com to block grc after using profile grc4?

Its not the case that grc.com will not block grc.com but that if used you go to grc its not blocked then use profile with forbidden *.grc*.com grc will not be blocked because the profile with forbidden grc.com breaks the content filter until you use debug content-filter https-domain-filter cache flush. So first I show…

Is MTU before going VPN 1500? Do you use PPP for WAN?

Maybe a bad cable?

Make a address FQDN with *bidi.net.uk and drop it for destination from LAN1 to WAN 

try firmware 5.35

You want port 8 tagged for both VLAN 2 and 5 Not sure On the AP you have I take it supports VLAN for a given SSID?

No more IP conflicts messages now