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

    Accessing WPAD on /usr/local/www with port 80 (SOLVED)

    Scheduled Pinned Locked Moved Cache/Proxy
    12 Posts 3 Posters 2.5k 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.
    • A
      aGeekhere
      last edited by

      NAT backup

      To catch any PCs which aren’t configured with ‘auto configure’ in their settings, you could implement a port forward for any traffic directed at port 80 through to 3128.

      Can I have an example of how you can do this?

      Never Fear, A Geek is Here!

      1 Reply Last reply Reply Quote 0
      • KOMK
        KOM
        last edited by

        some ideas ?

        Are you running WebGUI in HTTP mode or HTTPS mode?

        1 Reply Last reply Reply Quote 0
        • E
          exa_gon
          last edited by

          @aGeekHere:

          NAT backup

          To catch any PCs which aren’t configured with ‘auto configure’ in their settings, you could implement a port forward for any traffic directed at port 80 through to 3128.

          Can I have an example of how you can do this?

          Here in attach.

          2016-05-26_19-19-27.png_thumb
          2016-05-26_19-19-27.png

          1 Reply Last reply Reply Quote 0
          • E
            exa_gon
            last edited by

            @KOM:

            some ideas ?

            Are you running WebGUI in HTTP mode or HTTPS mode?

            HTTPS.
            So I used another lighttpd for the wpad.

            But I have another problem with sgerrro.php.. ( the last one problem )

            1 Reply Last reply Reply Quote 0
            • KOMK
              KOM
              last edited by

              To catch any PCs which aren’t configured with ‘auto configure’ in their settings, you could implement a port forward for any traffic directed at port 80 through to 3128.

              That's what Transparent mode basically is.  Don't do it this way or you lose the advantages of an explicit proxy in regard to client certificates with HTTPS sites.

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

                This is what I was trying hard to understand as the guide suggest you can have a wpad and create a Nat rule to redirect all remaing traffic from port 80 to 3128.

                Never Fear, A Geek is Here!

                1 Reply Last reply Reply Quote 0
                • KOMK
                  KOM
                  last edited by

                  If you're running Transparent (boo!) then you don't need WPAD.  If you're running explicit then you don't need manually-added NAT rules.

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

                    And for programs that have no proxy setting and want to go direct you have to create a bypass on port 80 and 443 for each program. Google play and other apps on Android have too many servers to find and bypass (though chrome on Android uses the wpad). I am just thinking there has got to be a better way to handel programs that have no proxy settings and want to go direct with using a wpad.

                    Never Fear, A Geek is Here!

                    1 Reply Last reply Reply Quote 0
                    • KOMK
                      KOM
                      last edited by

                      I am just thinking there has got to be a better way to handel programs that have no proxy settings and want to go direct with using a wpad.

                      If these things aren't smart enough to handle a manual proxy, what makes you think they're WPAD-aware???

                      What you do is simple here:

                      • Run your proxy in explicit mode

                      • Create your wpad files and put them on an HTTP server

                      • Edit DNS & DHCP to support wpad.YourDomain.blah and point it to pfSense LAN IP

                      • Create firewall rule that blocks access to ports 80/443 on LAN for all

                      • Create a rule just above that rule that allows the Roku and whatever other devices to access ports 80/443 on LAN

                      The only downside is that nothing the Roku accesses will be cached.

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

                        That is exactly my set up

                        Never Fear, A Geek is Here!

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