Navigation

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

    Lightsquid generates error in Proxy Report

    Cache/Proxy
    3
    7
    962
    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.
    • S
      Supermule Banned last edited by

      It searches for lightsquid/index.cgi but that generates a 404 error.

      1 Reply Last reply Reply Quote 0
      • D
        doktornotor Banned last edited by

        I'm rewriting this package pretty much from scratch ATM, with the hope that it will at least stop fscking up Squid configuration and cron, if nothing else…

        1 Reply Last reply Reply Quote 0
        • D
          doktornotor Banned last edited by

          Looks pretty good, everything works here incl. cron, plus the package doesn't touch Squid configuration at all any more.

          https://github.com/pfsense/pfsense-packages/pull/1104/

          1 Reply Last reply Reply Quote 0
          • D
            dwood last edited by

            For now, the 404 error can be fixed by entering your psfense LAN IP under Squid Proxy Server GUI, Local Cache TAB, External Cache Mangers field.  I'm guessing the "Doktor" has addressed this issue in the new lightsquid build.

            1 Reply Last reply Reply Quote 0
            • D
              doktornotor Banned last edited by

              That'd be 403, not 404. If you are getting 403, it's actually a whole lot better to let Squid listen on localhost (loopback) – which is what the reworked package tells people to do. If you get 404 it means the package install went belly up.

              1 Reply Last reply Reply Quote 0
              • D
                doktornotor Banned last edited by

                Just adding to the above: the updated package will force localhost. The code was broken in the first place with multiple proxy interfaces, producing random results requiring different ACLs depending on interface names. Localhost works out of the box without any additional ACLs, the only thing to do is check loopback in 'Proxy Interfaces' when doing **non-**transparent proxy. If the proxy is transparent, there's no proxy configuration needed at all, it just works.

                1 Reply Last reply Reply Quote 0
                • D
                  doktornotor Banned last edited by

                  2.42 is now merged. ;)

                  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