>Ted Unangst wrote: >> 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. > >Oops, followup question. If the situation is that these are simply unbound >sockets that don't receive traffic, that makes life easier. I wasn't sure if >they were some catch-all sockets or what.
They will receive responses to traffic they send.
