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

Is there a work-around for bug in "Bypass Proxy for These Destination IPs"?

Scheduled Pinned Locked Moved Cache/Proxy
6 Posts 4 Posters 2.6k 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.
  • B
    bri189
    last edited by May 26, 2016, 9:06 PM

    _Symtom: squidGuard stops filtering altogether, even things explicitly blacklisted.

    Cause: You have entered values (semi-colon delimited) under 'Proxy Server/General/Bypass Proxy for These Destination IPs' that are not in the blacklist.

    Solution: Remove all data and save, squidGuard works properly again._

    –--

    Is there a work around for this?  I really have no need to proxy my email and other such sites.  I found the above solution when I hit the problem but can't find that post again to see if there was a work-around or if a bug had even been submitted yet.

    Thanks!

    1 Reply Last reply Reply Quote 0
    • E
      exograpix
      last edited by May 27, 2016, 8:33 AM

      It is working fine at my end, I think you can only put destination IP not hostname like gmail.com. In some cases it is not working like in wetransfer.com. Any suggestion.

      1 Reply Last reply Reply Quote 0
      • B
        bri189
        last edited by Jun 1, 2016, 12:27 AM

        I'll try IP and post results, but there are some IP's I want to whitelist that are dynamic, so that's why domain is needed versus IP, but first let me try IP for the one's are static and see how that works.  Thanks for the reply!

        1 Reply Last reply Reply Quote 0
        • J
          jimp Rebel Alliance Developer Netgate
          last edited by Jun 2, 2016, 1:03 PM

          Don't put hostnames in there directly. A DNS failure will cause the rules to fail.

          Put all your IP addresses and hostnames for that in an alias, and then reference the alias in that field. The alias code and filterdns will keep the DNS record updated over time. Putting the hostname in that proxy bypass field directly will only attempt to resolve it once, when the rules are reloaded, so it won't keep it updated over time.

          Remember: Upvote with the 👍 button for any user/post you find to be helpful, informative, or deserving of recognition!

          Need help fast? Netgate Global Support!

          Do not Chat/PM for help!

          1 Reply Last reply Reply Quote 0
          • B
            bri189
            last edited by Jun 6, 2016, 10:22 PM

            I will try alias' and follow-up.  Thanks!

            1 Reply Last reply Reply Quote 0
            • R
              resch
              last edited by Nov 28, 2016, 7:15 PM

              Hello there,

              Having the same problem. Currently on 2.3.1 stable release, with squid 0.4.23_1 and squidGuard 1.14_4.

              I am using aliases as recommended above, but still have the problem. Sometimes squidGuard will simply stop filtering and
              allow everything, and cleaning the "Bypass Proxy for those source IP's" field and saving solves the problem.

              Couldn't really find a workout, have to constantly check if filtering is active and wipe the bypass proxy field if
              it doesn't. Maybe I should create a bug report?

              Thank you!

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