>Philip Guenther wrote: >> And, perhaps more directly, how would I block this in pf.conf? >> > >> >> Excellent choice, blocking dhclient from receiving the leases that it >> requests. >> "What problem are you trying to solve?" > >Well, this may be something of a lost cause, but I would prefer that chrome >not listen for stuff I don't understand. It listens on port 5353 as well, for >mDNS, and I can block that easily enough. It's the socket without a port >that's giving me trouble.
So it doesn't bind() and it doesn't connect(), but uses sendto It is part of POSIX If you want to block that piece of talking to the mothership you're going to have to get into the source code.
