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

    squid+squidGuard - some apps not working properly

    Cache/Proxy
    2
    3
    617
    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
      MrIT
      last edited by MrIT

      Hi there,

      we are using squid and squidGuard to restrict access from our schools wifi to the internet. Squid runs in transparent mode with the "Splice all" option. We provide a WPAD url through DHCP.

      All configuration seems fine but some apps (like WhatsApp or Threema are not working properly) - either on Android nor on iOS.

      I found the following log entry which related to Threema:

      1b807087-262b-4331-99a1-ef908fc1242f-image.png

      I am surprised that Squid receives an connection request for port 5222 (which is a Threema related port which I also opened on the firewall).

      Does anyone have an explaination for this behavior?

      Regards
      Marcel

      My wpad.dat looks like this:

      function FindProxyForURL(url,host) {
          if(!url.startsWith("http:") && !url.startsWith("https:")) {
              return "DIRECT";
          }
      
          var resolved_ip = dnsResolve(host);
          if(isPlainHostName(host) || isInNet(resolved_ip, "10.0.0.0", "255.0.0.0") || isInNet(resolved_ip, "172.16.0.0", "255.240.0.0") || isInNet(resolved_ip, "192.168.0.0", "255.255.0.0") || isInNet(resolved_ip, "127.0.0.0", "255.255.255.0")) {
               return "DIRECT";
          }
      
      
          return "PROXY 10.70.0.1:3128;DIRECT";
      }
      

      Addition: I am running the 22.05 release (on Netgate hardware)

      A 1 Reply Last reply Reply Quote 0
      • A
        aGeekhere @MrIT
        last edited by

        @mrit You can try enabling the options in "Remote Cert Checks" to see if that is the issue.

        Never Fear, A Geek is Here!

        M 1 Reply Last reply Reply Quote 0
        • M
          MrIT @aGeekhere
          last edited by

          @ageekhere Unfortunately that did not solve my problem :-(

          I tried both variants, but none seems to solve my problem. I ended up checking the "do not verify remote certificate" option anyway.

          5f5023a0-1620-49c9-95fd-875a35eddb8a-image.png

          But I am still surprised, that Squid receives a request for port 5222.

          Regards
          Marcel

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