When I make the rule my client pc's are ignoring the rule that I just made, what am i doing wrong?
I am fairly new to the sophos firewall.
This thread was automatically locked due to age.
When I make the rule my client pc's are ignoring the rule that I just made, what am i doing wrong?
I am fairly new to the sophos firewall.
A few things I see.
A quick thing to check would be the Live Connections tab of current activities while a client is streaming. Find the YouTube Video Streaming in the list of apps, click the underlined "total connections" count to bring up the details and it will show you which firewall rule was applied to the traffic. If you can confirm it is hitting your "limit streaming" rule then we can dig down deeper.
Gary
A few things I see.
A quick thing to check would be the Live Connections tab of current activities while a client is streaming. Find the YouTube Video Streaming in the list of apps, click the underlined "total connections" count to bring up the details and it will show you which firewall rule was applied to the traffic. If you can confirm it is hitting your "limit streaming" rule then we can dig down deeper.
Gary
Hi Gary Parr,
When I make a rule that is before rule 2 i get this error message from my browser
to give you a rough discription (becasue it is in Dutch) my conncection is not protected.
it says that google has an invalid certificate.
Error code SEC_ERROR_UNKNOWN_ISSUER
So basicly i am not allowed to go on the internet if it is setup like this.
to go back on your point 3. i basicly selectedd everything with youtube in the name.
My guess is that the certificate error you are seeing is caused by a redirect to the captive portal. By default, XG uses SSL for the captive portal but the factory-installed SSL certificate is self-signed and not trusted. You can either replace the SSL certificate with a "real" one, import the Sophos CA so the self-signed becomes trusted, or you can disable HTTPS redirection for the captive portal. Other alternatives include removing the "known users" requirement for that rule or using a different authentication mechanism.
Oh, it could also mean you have enabled decryption and scanning of HTTPS which uses the same self-signed cert causing the same untrusted issues.
-Gary