Hi. I'm jon.404, a Unix/Linux/Database/Openstack/Kubernetes Administrator, AWS/GCP/Azure Engineer, mathematics enthusiast, and amateur philosopher. This is where I rant about that which upsets me, laugh about that which amuses me, and jabber about that which holds my interest most: *nix.
"Are we there yet?"
Windows has this nasty habit of spamming a dhcp server with DHCPINFORM messages unless the dhcp server provides a proxy auto-configuration script. As I've not yet found a way to make Windows stop doing this, I've set up the following in my dhcpd.conf:
The above is for OpenBSD dhcpd. For dnsmasq:
Or for ISC dhcpd:
10.42.0.11 is a web server on my local network (apache2 running on Linux) that serves a few network monitoring scripts. I dropped the wpad.pac script (below) in the root of the server, and set the following in apache2.conf:
This is the content of the wpad.pac script:
Yes, you read that right. I set up a proxy auto-configuration script to tell Windows that there is no proxy to automatically configure.
Edit - After letting this run for a few hours, I now realize that the dhcpd logs are clean, but my apache2 logs are full of accesses to wpad.pac. Sigh. The madness never ends =)
Code:
option autoproxy-script "http://10.42.0.11/wpad.pac";
Code:
dhcp-option=252,http://10.42.0.11/wpad.pac
Code:
option local-pac-server code 252 = text; option local-pac-server "http://10.42.0.11/wpad.pac";
Code:
AddType application/x-ns-proxy-autoconfig .pac
Code:
function FindProxyForURL(url, host)
{
return "DIRECT";
}
Edit - After letting this run for a few hours, I now realize that the dhcpd logs are clean, but my apache2 logs are full of accesses to wpad.pac. Sigh. The madness never ends =)
Total Comments 0
