06.07.2024 11:53, Klemens Nanni пишет:
> Upstream code last changed in 2013 our README mentions a dhclient.conf `script'
> option, which our manual doesn't even document.
> 
> DESCR reads like unwind.conf(5) 'block list file [log]' could be used instead:
> 
>   adsuck is a DNS relay that returns NXdomain for hosts that match names in a
>   blacklist for quick and non browser plugin based ad blocking.
> 
> 
> Anyone using this and cares enough to unbreak instructions?
> Or can we remove this port?
> 
> pkg/README:
> 
> 
> Running adsuck(1) locally with dhclient(8)
> ==========================================
> 
> To make dhclient(8) play nice with adsuck(1), the following script has
> been installed:
> 
>     ${TRUEPREFIX}/sbin/dhclient-adsuck

... that does 'exec /sbin/dhclient-script' which isn't in base.

  $ pkglocate sbin/dhclient-script
  isc-dhcp-client-4.4.3pl1p1:net/isc-dhcp,-client:/usr/local/sbin/dhclient-script

README doesn't say how to actually run dhclient-adsuck, so I thought perhaps
there's a 'chroot /usr/local/' somewhere, but that would break dhcilent-adsuck's
'. /etc/rc.conf'... later checking of $adsuck_flags won't work, either, as that's
in /etc/rc.conf.local, so I conclude that this port is just plain broken as-is.

  $ sh -o nounset -c '. /etc/rc.conf; echo $adsuck_flags' 
  sh: adsuck_flags: parameter not set

OK to remove?

> 
> Provided that adsuck(1) is installed and adsuck_flags is not set to "NO"
> in rc.conf.local(8), this script will prevent from using
> /etc/resolv.conf to resolve non-blacklisted entries but use
> /var/adsuck/files/resolv.conf instead.
> For a proper use you need to add this line to /etc/dhclient.conf:
> 
>     script "${PREFIX}/sbin/dhclient-adsuck";
> 
> Make sure that /etc/resolv.conf only contains:
> 
>     nameserver 127.0.0.1
>