Port 443 or 5001 (inbound, TCP) HTTPS for Presence and Provisioning, or the custom HTTPS port you specified. Port 5090 (inbound, UDP and TCP) for the 3CX tunnel.
DHCP servers built into routers are really a sort of last resort. You could block DHCP messages at the layer-2 pfSense firewall so that the modem never sees them, and let pfSense still perform DHCP. If pfSense is the source of your trouble, you need to replace it with a router which works.Search for private DNS in your browser's settings. Alternatively, disable DoT/DoH on the offending clients. To block DoH you need to block access to each individual DoH servers by their IP address. DoH runs over port 443 and is indistinguishable from other HTTPS traffic. DoT can be easily blocked by blocking port 853.The end result is something like this: Test it out by attempting to access the pfSense web interface from a host on the blocked VLAN. Go to the Floating Firewall Rules and create a rule which blocks certain VLANs from accessing the pfSense GUI from its TCP Port. Mine is currently 443 but I changed it to 444. src ip any dest ip any src port any dst port 443 inbound block outbound allow SSLServer:443 ->YourPC- src ip any dest ip any src port 443 dst port any inbound allow outbound block The outbound traffic seems OK, but I am dropping packets like this (This example is loading a twitter page, the akamai content): 23.9.229.210:443 > XXX.XXX.
0 kommentar(er)
