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

Unable to browse websites when web filtering is turn off

Hi All,

new sophos user here. I have installed Sophos UTM 9 with all basic "access web" policy during install with no IPS or any of the advance protection stuff. I am not able to access any website when Web filtering is off. However when I turn it on, i can access websites but there still the yellow exclamation point in the network settings on my windows box. Also mobile users are getting weird IP address on wifi. Any idea? 



This thread was automatically locked due to age.
  • Hi and welcome,

    do you have any firewall rules enabled with a MASQ (NAT)?

    Where do your devices get their IP addresses from eg did you setup a DHCP server either in the UTM or on local server?

    Ian

    XG115W - v20.0.2 MR-2 - Home

    XG on VM 8 - v21 GA

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

  • You're able to access sites with web filtering on because that takes precedence over firewall rules (at least for tcp port 80/443 usage).  If you establish a firewall rule to allow port 80/443 access to the internet then you should be able to browse with web filtering off.

    I keep web filtering no to protect against accessing malicious sites and such.

  • Like rfcat_vk says

    Masquerade your Internal Network to Wan interface if not. But i think it is enabled during setup.

    Create a rule in Firewall:

    Internal Network - service:web group - destination: any - allow

  • Dhcp is another question.

    Disable DHCP in Sophos to find out who is giving DHCP. Normaly Access Points dont give DHCP, but depends on the device and service

  • Thank you all. Ive ran wireshark on my network to find out where the dhcp is coming from and found out it was leasing from my modem which is bridge to my router. found it had to find it because only android devices were having issues. anyway as soon as i corrected the bridge, everthing is fine. Actually found it using another firewall product combination with wireshark :)