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

Squid Clamd and ICAP port questions

Scheduled Pinned Locked Moved Cache/Proxy
1 Posts 1 Posters 325 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.
  • J
    JonathanLee
    last edited by JonathanLee Nov 30, 2022, 8:43 PM Nov 30, 2022, 3:37 PM

    Hello fellow Netgate community,

    Can you please help? I wanted to ask if the port used for ICAP "1344" is the same that is used with Clamd ? Do I need to have an ACL placed for access to the loopback 127.0.0.1, I have already added 127.0.0.1 into the approved use for squid ACLs. I changed my NAT to manual and moved off of automatic also.

    What port does Clamd use for its socket when accessing the loopback?

    What port does I-CAP use outside of 1344 when ClamAV is enabled?

    Do they conflict without automatic NAT enabled?

    The issues I have seemed to resolve when I added an ACL for the firewall for port 127.0.0.1 all to the firewall itself inside of the firewall. I do understand that the Clam and Squid package loads into the firewall and is accessing the loopback when it is running inside of pfSense so with that being said should the firewall require ACLs for that package if you turn off the automatic NAT? Example 127.0.0.1 approve to 127.0.0.1:1344?

    Make sure to upvote

    1 Reply Last reply Reply Quote 0
    1 out of 1
    • First post
      1/1
      Last post
    Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.
      This community forum collects and processes your personal information.
      consent.not_received