Netgate Discussion Forum
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Search
    • Register
    • Login

    Squidguard calling sgerror.php in wrong interface

    Scheduled Pinned Locked Moved Cache/Proxy
    2 Posts 2 Posters 1.4k Views
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • A
      alvayag
      last edited by

      Hi guys.

      I'm running Pfsense (2.3.2) with squid (0.4.22) and squidguard (1.14_3) using transparent proxy and man-in-the-middle filtering.
      I must say that for now everything is working properly, except when squidguard try to block anything.
      When a host makes a conection to a page in the blacklist, the browser is pointed to sgerror.php to generate the block page, but the call is made to the wrong interface.

      I have two interfaces in the same nic.
      One is just for administrative purposes, in 10.0.1.80.
      The other interface, is the transit network that my core switch uses to connect to Pfsense, in 172.16.20.20.

      So, when a block is made by squidguard, it redirects to sgerror.php in 10.0.1.80, but I need the redirect to be made to sgerror.php in 172.16.20.20
      If not, the page can't be reacheable to the hosts.
      Any idea how can I change that?

      Thanks! ;D

      1 Reply Last reply Reply Quote 0
      • KOMK
        KOM
        last edited by

        Try changing the redirect mode from int page to ext URL error page and then supply the full URL with IP address.

        1 Reply Last reply Reply Quote 0
        • First post
          Last post
        Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.