Navigation

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

    Squid Caching Not Working

    Cache/Proxy
    1
    1
    601
    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.
    • M
      m0lecule last edited by

      I'm having serious issues getting Squid Caching working on my network. This is really bumming me out :(

      Network Setup:
      –------------------
      192.168.1.0/24 IP Scheme in the LAN

      APU1D4 Firewall / Router with 4gb Ram and 32gb mSATA running pfSense 2.3.3-RELEASE-p1
      [APU1D4 Connects to]
      Dell Powerconnect 5324 Switch
      [Powerconnect Leads to]
      Various pieces of equipment (laptops, desktops, etc.) inside the LAN

      pfSense Setup:
      –-----------------
      Running Squid version 0.4.36_2 along with Lightsquid version 3.0.6_2
      Squid is using the LAN and loopback interfaces under General Settings, Transparent HTTP Proxy is on, logs are on and cycling every 30 days, under Local Cache I'm using heap LFUDA, also using 8000MB for HD caching and aufs, maximum object size is 1024 and min is 0, memory cache size is 2048, max objects in ram is 256 (default), memory replacement policy is LRU, Allowed subnets in the ACLs is 192.168.1.0/24, ACL safe ports is 80 443 and SSLPorts is 443 563

      The Issue:

      After setting up Squid I tested downloading files multiple times expecting the 2nd time to be astronomically faster. It wasn't. Download speeds remain the same no matter how many times I download the same exact file. These test downloads are within the 1024mb range set for maximum object size of course.

      I then checked out the cache.log and access.log files. Strange things in the logs:
      Cache.log says "pinger: Initialising ICMP pinger ..." a whole bunch of times
      Access.log says "TCP_MISS/200" "TCP_MISS/204" "TCP_MISS/302" "TCP_MISS/304" and "TCP_MISS/400" a WHOLE BUNCH OF TIMES.

      Can anyone help?

      1 Reply Last reply Reply Quote 0
      • First post
        Last post

      Products

      • Platform Overview
      • TNSR
      • pfSense
      • Appliances

      Services

      • Training
      • Professional Services

      Support

      • Subscription Plans
      • Contact Support
      • Product Lifecycle
      • Documentation

      News

      • Media Coverage
      • Press
      • Events

      Resources

      • Blog
      • FAQ
      • Find a Partner
      • Resource Library
      • Security Information

      Company

      • About Us
      • Careers
      • Partners
      • Contact Us
      • Legal
      Our Mission

      We provide leading-edge network security at a fair price - regardless of organizational size or network sophistication. We believe that an open-source security model offers disruptive pricing along with the agility required to quickly address emerging threats.

      Subscribe to our Newsletter

      Product information, software announcements, and special offers. See our newsletter archive to sign up for future newsletters and to read past announcements.

      © 2021 Rubicon Communications, LLC | Privacy Policy