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

    Weird ClamAV problem after 2.2.6 to 2.3 upgrade

    Scheduled Pinned Locked Moved Cache/Proxy
    1 Posts 1 Posters 675 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.
    • K
      Kei
      last edited by

      Hello everyone,
      I had to reinstall squid after 2.2.6 to 2.3 upgrade and I got it correctly working with squidguard again.
      Unfortunately I've noticed that ClamAV is not working as before. The part when it redirects to a page showing that a virus was found, seems to be broken.
      From the screenshot, you can notice that ClamAV redirects to the hostname instead of the IP address belonging to the subnetwork where the PC resides.
      Also, the hostname (that I had to cover in black) appears to be slave.companyname instead of the ip address of the master.
      How can I revert back this behavior, and why is he redirecting to the slave pfsense firewall?
      Anyone else is having this problem?
      clamav_error.png
      clamav_error.png_thumb

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