On Mar 31, 2016, at 3:43 AM, Quinn The Eskimo! <eskimo1@apple.com> wrote: On 29 Mar 2016, at 21:30, Steve Sisak <sgs-lists@codewell.com> wrote:

...

It would, however, be very useful to be able to exclude interfaces from being advertised by Bonjour You can do this programmatically, but there are no configuration options for it. That would kinda run counter to the whole spirit of 'zeroconf’.

True, but the current case is that “screen sharing doesn’t work unless you know the internal IP address of the machine you’re trying to connect to”. A reasonable default (on a multi-homed machine) which would require no configuration would be for mDNS to advertise services on that machine using the IP address of the interface it is responding on.

...

This could all be solved if I could configure Bonjour to only advertise the IP of the interface it’s multicasting on — or if Apple implemented source-aware routing on multi-homed machines.

Apple implemented source-aware routing on multi-homed machines in, gosh, can't remember, it's a while back now. It's certainly on by default in OS X 10.7 and later [1].

Let me rephrase that as “Mac OS X Server falls over of it’s public IP address isn’t also it’s default interface” — last time I tried making the internal interface the default, it tried to respond to external responses via default route resulting in relies coming from the wrong address and a general mess. That might have been 10.6.8, however. Too much functionality I depended on was removed from 10.7 server. Recently trying again with El Capitan Server on a separate machine.

I recommend you file a bug report describing your (quite unusual) setup and the networking team here at Apple will see if there's anything they can do to help you out.

I’d personally consider it a “standard small business setup” — public and private LANs with a small static IP block. Comcast’s “business gateway” is a complication, but since they are one of the largest providers in the US (and the only non-DSL broadband in many area), we’re not talking about a small number of customers here. If I had dynamic IP I could use my own router and cable modem, however Comcast policy prohibit using anything but their hardware with static IP. I will file a report as soon as I get a minute, although I’ve solved pretty much everything by doing all routing with non-Apple hardware — specifically, putting Ubiquiti EdgeRouter 3-lite (<$100 on Amazon) between the Comcast router and everything else, and switching the AirPort Extreme and Time Capsule to bridge mode. The standard 1-WAN, 2-LAN configuration works out of the box without even resorting to command-line — QoS works in the default configuration — being able to set up an OpenVPN SSH tunnel between multiple sites was an added bonus. Best, -Steve _______________________________________________ Do not post admin requests to the list. They will be ignored. Macnetworkprog mailing list (Macnetworkprog@lists.apple.com) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/macnetworkprog/site_archiver%40lists... This email sent to site_archiver@lists.apple.com