Unofficial WPAD package for pfSense software

warmadmax

any news on if this will make it to official package status?

xchaz

Hi,

squid+WPAD bypasses my captive portal. Is there any other way?

Thanks,
Chaz

asterix

@Bigdaddy168:

Nice! Can you make this package official?

I can submit a pull request to oficial repo. But need core team review to get merged.

Great work here marcelloc. Finally I have wpad hosted with webconfigurator on https.

Any update on the pull request to official repo?

vicpome

Hi, Marcelloc , Is there a step-by-step manual or instuctions for config the GUI of the "wpad" after it is installed?.
Thanks.

chicago_cs

@vicpome , check out this topic

kklouzal

@marcelloc said in Unofficial WPAD package for pfSense software:

fetch -q -o /usr/local/etc/pkg/repos/Unofficial.conf https://raw.githubusercontent.com/marcelloc/Unofficial-pfSense-packages/master/Unofficial.24.conf

I logged into SSH, opened Shell, pasted in the 2.4 unofficial repo command and hit enter.

Now when I go to my package manager inside web gui there are no available packages being listed, none at all.

Going to Diagnostics->Edit File and saving "/usr/local/etc/pkg/repos/Unofficial.conf" as a blank file brings my official packages back thankfully.

EDIT:

Solved it, a little searching found that the github repo supplies a patch you must apply so PfSense can display unofficial repos. Check the main page on the github page for more info.

KOM

That's a lot of hassle with the potential to break pfSense just to configure WPAD, which is simple to configure by hand.

vicpome

@chicago_cs Agradezco tu respuesta, yo ya instale el pack , pero queria saber cuales son los pasos que siguen despues del 7, o sea como completar el "Gui" ya que no me funciona.
Gracias.

vielfede

@KOM if you use FW as wpad server, It is to avoid web interface protocol change, that's a secuirty issue

vielfede

@kklouzal said in Unofficial WPAD package for pfSense software:

I logged into SSH, opened Shell, pasted in the 2.4 unofficial repo command and hit enter.

Now when I go to my package manager inside web gui there are no available packages being listed, none at all.

Going to Diagnostics->Edit File and saving "/usr/local/etc/pkg/repos/Unofficial.conf" as a blank file brings my official packages back thankfully.

EDIT:

Solved it, a little searching found that the github repo supplies a patch you must apply so PfSense can display unofficial repos. Check the main page on the github page for more info.

Just to clarify 2.4.4 Install

System=>Pakages=>Available packages=>System_Patches=>install
System=>Patches=>add new patch=>244_unofficial_packages_list.patch (download it from https://github.com/marcelloc/Unofficial-pfSense-packages)
save
Apply (patch)

fetch -q -o /usr/local/etc/pkg/repos/Unofficial.conf https://raw.githubusercontent.com/marcelloc/Unofficial-pfSense-packages/master/Unofficial.24.conf

System=>Pakages=>Available packages=>WPAD=>install
configure wpad from Services=>WPAD

KOM

@vielfede Sorry, what? I don't understand what you mean. There is no inherent security issue using the firewall as the WPAD source. You're already running a web server on it. Serving up wpad.dat and proxy.pac from it doesn't make it insecure.

vielfede

@KOM said in Unofficial WPAD package for pfSense software:

@vielfede Sorry, what? I don't understand what you mean. There is no inherent security issue using the firewall as the WPAD source. You're already running a web server on it. Serving up wpad.dat and proxy.pac from it doesn't make it insecure.

I think that If you configure WPAD by hand, you have to switch fw web interface from https to http and this is an issue. Or am I wrong?

KOM

OK, now I see what you mean. No, you're right that WPAD needs an HTTP server. I don't see how a WPAD package gets around that unless it's installing its own http server.

vielfede

@Kom, In the first post there is the answer...

@marcelloc said in Unofficial WPAD package for pfSense software:

Here are install instructions for UNOFFICIAL wpad package for pfSense(R) software 2.3.x

It's based on forum tutorials to configure a second nginx instance to host pac file(s) in http and leave gui on https.
.....

aGeekhere

@marcelloc
I have installed the WPAD package, added the DNS host overrides in the DNS Resolver

wpad pfsensedomain.local 192.168.1.1 wpad

added the DHCP additional BOOTP.

number: 252 type: string value: "http://192.168.1.1/wpad.dat"
number: 252 type: string value: "http://192.168.1.1/wpad.da"
number: 252 type: string value: "http://192.168.1.1/proxy.pac"

pfsense webConfigurator is set to https with webGUI redirect selected

However I am having issues downloading the wpad file

http://192.168.1.1/proxy.pac This site can’t be reached
https://192.168.1.1/proxy.pac 404 Not Found nginx
http://192.168.1.1/wpad0/proxy.pac This site can’t be reached
https://192.168.1.1/wpad0/proxy.pac the pac file downloads

I seem to only be able to download the proxy.pac with

https://192.168.1.1/wpad0/proxy.pac

Am i missing something?

UPDATE: I had the wpad listen port set to the proxy port 3128, changing it to port 80 now downloads the file