we're attempting enable number of mdns advertised services on our campus wide wireless network, notably airplay. in our case, airservers sit on our wired network, need advertise services manually either dns-sd or mdns on wireless side. we've gotten working using static service advertisements in avahi , it's pretty slick, have scaling problem.
we have potentially 150 airserver hosts in variety of classrooms around campus. if enable of them, list choose on ipads outrageously large (to nothing of students thoroughly enjoying taking on airserver across campus when faculty member forgets change password).
what segregate our wireless network on single vlan per building basis form 27 mdns segments , run avahi advertise services in each segment, preferably on single, multi homed host access of segments.
i hoping avahi-daemon take parameter in avahi-daemon.conf points unique services directory, have multiple config files, each different allow-interfaces clause , pointer different services directory, doesn't appear configurable option.
i thinking of chroot jailing multiple copies of avahi, seems kludgy.
am missing more obvious strategy handle without creating 27 separate hosts?
thanks much!
jd
it possible achieve want if build own application publishing services in interfaces want. method call gnustep "base" framework, class gsavahinetservices (can used on linux) , method based on avahi api.
- (id) initwithdomain: (nsstring*)domain type: (nsstring*)type name: (nsstring*)name port: (nsinteger)port avahiifindex: (avahiifindex)anifindex avahiprotocol: (avahiprotocol)aprotocol as can see possible specify network interface index want service published on. can limit protocol (ipv4 or ipv6). if want 1 service available in more 1 interface, publish in each interface.
Comments
Post a Comment