I found a windows ipfw version here http://wipfw.sourceforge.net/ and here https://github.com/luigirizzo/dummynet
So, if I install it on Windows, and do that http://wiki.squid-cache.org/ConfigExamples/Intercept/Ipfw should it work?
Just to be clear, I don't want Windows doing the job of redirecting packets from 80 to 3129. I use iptables on dd-wrt for that (wifi guest only).
The problem is that when I configure squid as "http_port 3129 intercept" instead of "http_port 3129" it show me these errors:
2017/05/06 17:43:08 kid1| ERROR: NAT/TPROXY lookup failed to locate original IPs on local=10.0.0.1:3129 remote=192.168.11.236:57141 FD 9 flags=1
2017/05/06 17:43:08 kid1| WARNING: transparent proxying not supported
2017/05/06 17:43:08 kid1| WARNING: transparent proxying not supported
De: squid-users <squid-users-bounces@xxxxxxxxxxxxxxxxxxxxx> em nome de Amos Jeffries <squid3@xxxxxxxxxxxxx>
Enviado: domingo, 7 de maio de 2017 19:24:57
Para: squid-users@xxxxxxxxxxxxxxxxxxxxx
Assunto: Re: Passing Windows username to parent proxy
Enviado: domingo, 7 de maio de 2017 19:24:57
Para: squid-users@xxxxxxxxxxxxxxxxxxxxx
Assunto: Re: Passing Windows username to parent proxy
On 04/05/17 19:29, BurningSky wrote:
> Is there a way to view what Squid is forwarding so that I can inspect the
> packets to prove that Squid is sending user information as I have a call
> open with the firewall vendor and I want to be able to tell them with
> certainty that it is an issue at the firewall end rather than the Squid end.
Add this to your squid.conf:
debug_options 11,2
That will log the HTTP headers going through. You should see Proxy-Auth*
headers arriving and the exact same value(s) being sent onward, for both
request and response messages.
Amos
_______________________________________________
squid-users mailing list
squid-users@xxxxxxxxxxxxxxxxxxxxx
http://lists.squid-cache.org/listinfo/squid-users
> Is there a way to view what Squid is forwarding so that I can inspect the
> packets to prove that Squid is sending user information as I have a call
> open with the firewall vendor and I want to be able to tell them with
> certainty that it is an issue at the firewall end rather than the Squid end.
Add this to your squid.conf:
debug_options 11,2
That will log the HTTP headers going through. You should see Proxy-Auth*
headers arriving and the exact same value(s) being sent onward, for both
request and response messages.
Amos
_______________________________________________
squid-users mailing list
squid-users@xxxxxxxxxxxxxxxxxxxxx
http://lists.squid-cache.org/listinfo/squid-users
_______________________________________________ squid-users mailing list squid-users@xxxxxxxxxxxxxxxxxxxxx http://lists.squid-cache.org/listinfo/squid-users
