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

Webfilter Fehler. Webfilter with wrong Gateway IP

Hello,

we two different LANs

Port 1 192.168.12.0/24 Gateway 192.168.12.254 Zone LAN

Port 2 WAN 192.168.112.254 Gateway 192.168.112.1 Zone WAN

Port 3 192.168.20.0/24 Gateway 192.168.20.254 Zone LAN2

192.168.20.0/24 ist blocked to 192.168.12.0/24

Everything works fine but the web filter is the problem.

If the Webfilter is active I can see on Lan 192.168.12.0 the Block Page from Sophos

If I am in the 192.168.20.0/24 an go to a blocked site 

I can see in the Webbrowser the URLhttp://192.168.12.254:8090/ips/block/webcat?cat=66&pl=1&url=aHR0cDovL3RpdHRlbi5kZS8~

But there is no Page, because the lan 192.168.20.0/24 has no Rule to 192.168.12.254

I expect the URL form the block site http://192.168.20.254:8090/ips/block/webcat?cat=66&pl=1&url=aHR0cDovL3RpdHRlbi5kZS8~

Please help



This thread was automatically locked due to age.
Parents Reply Children
  • Blockpage will be loaded by the hostname of the XG. So the hostname is used by XG to redirect the client to this blockpage. Its 8090

    __________________________________________________________________________________________________________________

  • Ok, so i have to add a Firewall rule from the lan to xg Hostname with only Port 8090 für the blockpage?

  • No you dont have to do this. The XG will simply replay from this address. This system can intercept the request on all interfaces without the need to have a firewall rule. Except this traffic to this IP is blocked by some other device or routed differently. 

    Try to setup a FQDN for the XG anyways. It will resolve a lot of your frustration. 

    __________________________________________________________________________________________________________________

  • I mean, change the hostname of the XG to a DNS/FQDN of your domain. Instead of having your 192.168.12.254 you can setup xg.domain.local. 

    This DNS can be registered in the DNS of your AD. 

    Then register a certificate for this DNS record (internal or external) and push it to the clients. 

    I assume, the issue of your block page is not showing, is caused by the browser in the first place, as the website is not secure etc. 

    __________________________________________________________________________________________________________________

  • there is a hostname in our configuration

    but the users on the 

    192.168.20.0/24 do not have contact to the local dns. they are separated. they only have traffic to the sofos xg port / gateway 192.168.20.254 an than to the lan port

  • I assume, the issue of your block page is not showing, is caused by the browser in the first place, as the website is not secure etc. 

    I can't push it to the client, because some clients are customers. these customers can go the internet, but they should se block site if they won't to use a blocked page

    I assume, the issue of your block page is not showing, is caused by the browser in the first place, as the website is not secure etc. 

    No, because it is a different ip Adress wich is not possible to connect from this lan. There must be a blockpage on every gateway of the xg

  • Because you redirect the user to the IP, its selected there as the second point. PS: Your Screenshot still shows your Hostname. 

    __________________________________________________________________________________________________________________

  • First of all: Guest proxy is a easy to avoid setup. As you cannot intercept the HTTPS traffic, you are likely to be blind and cannot block everything in the first place. So to think, there is a "good way to block" unwanted websites for Guest (external) users, is not possible. 

    For those pages, you can actually block, you need to have a certificate, which is publicly known. LetsEncrypt or you purchase a certificate. 

    This can be pointed to an IP of XG. So for example, you can still use your first IP of your network, but it should be a DNS. (proxy.domain.com). Then register a cert with your public CA. 

    Another point you need to activate is the captive portal under Device Access: 

    __________________________________________________________________________________________________________________

  • ok 

    I changed it to the host name. point 1. and now on the normal lan 192.168.12.0/24 i come to the block site.

    but on the lan 192.168.20.0/24 I can't connect to the block site because it is on the wrong subnet?