Hi Brian, I guess the issue is with DBus activation of PacRunner. NM pushes config into PacRunner iff later one is available on Bus. This discussion may be relevant[1].
You can check if NM is actually sending data to PacRunner by starting it and reading logs: # pacrunner -nd [1] https://lists.01.org/pipermail/connman/2017-February/021585.html Thanks, Atul Anand On 3/5/17, Brian J. Murrell <[email protected]> wrote: > Hi, > > I read with great interest about the autoproxy configuration that is > supposed to be available in 1.6, so I installed 1.6.1. > > My DHCP server provides a WPAD option and NM is receiving it: > > $ nmcli connection show 'pc_bridge' | grep wpad > DHCP4.OPTION[17]: wpad = http://server.example.com/proxy.pac > DHCP4.OPTION[22]: requested_wpad = 1 > > Is that now supposed to be enough to expect my pacrunner to have been > configured to use that proxy.pac file? Or is there more that needs to > be done? I ask of course because my pacrunner still does not seem to > be getting configured to use that PAC script: > > $ proxy http://www.google.com/ > direct:// > > If I manually poke the PAC url into pacrunner it does work though: > > # gdbus call --system --dest org.pacrunner --object-path > /org/pacrunner/manager --method > org.pacrunner.Manager.CreateProxyConfiguration "{'Method': <'auto'>, 'URL': > <'http://server.example.com/proxy.pac'>;}" > (objectpath '/org/pacrunner/configuration33',) > $ proxy http://www.google.com/ > http://proxy.example.com.:3128 > > Thoughts? > > Cheers, > b. > _______________________________________________ networkmanager-list mailing list [email protected] https://mail.gnome.org/mailman/listinfo/networkmanager-list
