Bart Smaalders wrote: > Rishi Srivatsavai wrote: >> To enable/disable service advertisement of an inetd managed service >> using mDNS, administrators should use the inetadm(1M) tool to modify the >> value of the new service advertised property: 'inetd/advertised'. The >> new boolean property 'advertised' in the property group 'inetd' is >> introduced by this proposed work for services controlled by the inetd >> restarter. The new property indicates whether the service should be >> advertised using mDNS. The property value is of type boolean and is >> false by default. > > Why is the default "false"? > > If you enable a service that's externally available, should you not > advertise it?
For some applications that say use 'rpc' transport cannot advertise with "mDNS" so we cannot have it as the default for all inetd managed applications. And there might be others where additional service information must be advertised before it can be useful. So it would be better turn on each application individually. > How does one control on which interfaces one advertises? Eg > at home I run a machine with one nic that's Internet facing; the > other nic handles local lan traffic. I would happily advertise > on the local nic; the external nic less so :-). Right now the "mDNS" service has no configuration to limit advertisements/queries to a set of interfaces. It is an "all" or "nothing" approach. I understand this means the "mDNS" service will be disabled on machines that must limit "mDNS" traffic to specific interfaces or such machines must employ packet filtering. Thanks, Rishi
