4 ms·

My beef with airplay and pretty much every other Zeroconf based service is that they require weird stuff to work across subnets. Here I isolate every “IOT” devi

My beef with airplay and pretty much every other Zeroconf based service is that they require weird stuff to work across subnets. Here I isolate every “IOT” device specially the ones that potentially has a phone home capability into a separate network. The wireless network is also segregated and routed. To make everything Zeroconf/Bonjour work I have to create lots of SRV, PTR and TXT records in my internal DNS which is a Samba4 AD. This document http://www.grouplogic.com/Knowledge/PDFUpload/Info/WanBonjour_1.pdf http://www.grouplogic.com/Knowledge/PDFUpload/Info/WanBonjou... is great to setup the basics but you will have to find out the specific RR for each type of service.

X-Istence 8y ago
You could also set up Avahi or some other mDNS daemon to relay mDNS packets across the two different networks, so long as you can route the UDP/IP from one network to another you shouldn't need to create a whole bunch of TXT records.
- tjohns 8y ago
  Indeed. The usual term for this is a “mDNS Reflector”. There’s a guide for setting it up with Avahi here: http://chrisreinking.com/need-bonjour-across-vlans-set-up-an-avahi-gateway/ http://chrisreinking.com/need-bonjour-across-vlans-set-up-an...
- robocat 8y ago
  Here is an article about mDNS and bonjour: https://community.cisco.com/t5/wireless-mobility-documents/basic-theory-behind-mdns/ta-p/3148577 https://community.cisco.com/t5/wireless-mobility-documents/b... However it is not particularly clear!
- ulzeraj 8y ago
  Going DNS has its advantages like being a less broadcasty solution that can work across VPNs. I've first implemented it some years ago when a client wanted to share authenticated wireless AirPrint to wireless guests on his huge school wireless network. The system is still working. I guess another advantages of going DNS besides not having to broadcast information is that you chose what you want to publish.

X-Istence 8y ago

You could also set up Avahi or some other mDNS daemon to relay mDNS packets across the two different networks, so long as you can route the UDP/IP from one network to another you shouldn't need to create a whole bunch of TXT records.

tjohns 8y ago
Indeed. The usual term for this is a “mDNS Reflector”. There’s a guide for setting it up with Avahi here: http://chrisreinking.com/need-bonjour-across-vlans-set-up-an-avahi-gateway/ http://chrisreinking.com/need-bonjour-across-vlans-set-up-an...
robocat 8y ago
Here is an article about mDNS and bonjour: https://community.cisco.com/t5/wireless-mobility-documents/basic-theory-behind-mdns/ta-p/3148577 https://community.cisco.com/t5/wireless-mobility-documents/b... However it is not particularly clear!
ulzeraj 8y ago
Going DNS has its advantages like being a less broadcasty solution that can work across VPNs. I've first implemented it some years ago when a client wanted to share authenticated wireless AirPrint to wireless guests on his huge school wireless network. The system is still working. I guess another advantages of going DNS besides not having to broadcast information is that you chose what you want to publish.