From mboxrd@z Thu Jan  1 00:00:00 1970
From: erik quanstrom <quanstro@quanstro.net>
Date: Fri,  1 Jan 2016 19:42:48 -0800
To: marc@boschma.cx, 9fans@9fans.net
Message-ID: <3e9e24eac4cebcbec3805d16d0081dc5@mule>
In-Reply-To: <E4A21AAA-FE61-4FE5-B3F2-E4CD500526DE@boschma.cx>
References: <383D8F53-3364-420A-93ED-E1034CB0C258@quintile.net>
	<E4A21AAA-FE61-4FE5-B3F2-E4CD500526DE@boschma.cx>
MIME-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Subject: Re: [9fans] bonjour mDNS?
Topicbox-Message-UUID: 7cf54e6c-ead9-11e9-9d60-3106f5b1d025

On Fri Jan  1 19:32:25 PST 2016, marc@boschma.cx wrote:
>=20
> > On 2 Jan 2016, at 7:05 am, Steve Simon <steve@quintile.net> wrote:
> > anyone done any work to implement mDNS / bonjour on plan9?
> >=20
>=20
> No, but I have an interest; just starting out with Plan9 :)
>=20
> > my rough plan is to write a file server which generates /lib/ndb/mdns
> > which can be included into your /lib/ndb/local.
> >=20
> > I fear the biggest hassle is the clash of UDP port use may mean
> > mDNS must become part of dns(1) rather than a separate file server.
> >=20
>=20
> Shouldn=E2=80=99t dns(1) only bind to unicast UDP port and thus mDNS co=
uld bind to the multicast UDP port?
>=20
> Are you only considering resolution or also publishing services?

it would make sense to me to make a dnsudp request file server that manag=
es requests, and
fork (ha!) that task off to it.  this file server would not care if it's =
querying normal dns,
or mdns.

- erik