Guest User!

You are not Sophos Staff.

This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Please explain this odd diagnostic tool behaviour.

Hi folks,

I have another thread which the  issue has been resolved about accessing coles.com.au.

I can now access that site without any issues. I was using the policy tester during my investigations and received some strange answers which did not help with the resolution.

Policy tester results. The first is with the SSL/TLS in the selection process. The second is just the web proxy with the web policy used the access rules.

Why does the SSL/TLS cause the site to show blocked in the testing when in practice it is not blocked?

Ian



This thread was automatically locked due to age.
Parents
  • No answers, very disappointing. Today the XG started to block access to the coles.com.au site for most users, again. Testing shows DNS does not return a IPv8 address for the site which seems to be the issue. XG cannot test access to IPv6 sites which makes diagnosis very difficult.

    Ian

    XG115W - v19.5.1 mr-1 - Home

    If a post solves your question please use the 'Verify Answer' button.

  • I have identified why coles.co,.au is not accessible from some device on the local network

    Further to the diagnostic failure, the same issue occurs with otthe websites, so there is a bug in the diagnostic tool.

    Ian

    update on connection issue. Disable the wifi for awhile seems to work on most devices.

    XG115W - v19.5.1 mr-1 - Home

    If a post solves your question please use the 'Verify Answer' button.

  • I am not able to follow you:
    The policy tester can do the web proxy rules and the firewall rules. 

    You do not have a matching Firewall rule for this traffic. Should there be one firewall rule? 

    Because proxy is simply testing itself, solely on the base of "what would the proxy say". 

    If you are getting a blocked page, this would be fine, as this is the expected behavior, due no firewall rule in place. 

    __________________________________________________________________________________________________________________

Reply
  • I am not able to follow you:
    The policy tester can do the web proxy rules and the firewall rules. 

    You do not have a matching Firewall rule for this traffic. Should there be one firewall rule? 

    Because proxy is simply testing itself, solely on the base of "what would the proxy say". 

    If you are getting a blocked page, this would be fine, as this is the expected behavior, due no firewall rule in place. 

    __________________________________________________________________________________________________________________

Children