On Thu, May 10, 2012 at 9:21 AM, Phil Mayers <[email protected]>wrote:
> On 10/05/12 17:12, Jonathan Lassoff wrote: > >> On Thu, May 10, 2012 at 2:54 AM, Phil Mayers <[email protected] >> <mailto:[email protected].**uk <[email protected]>>> wrote: >> >> On 09/05/12 22:55, Jonathan Lassoff wrote: >> >> I've gotten this to work in the past, but it ended up being a >> LOT more work >> than just using DNS names and routing (which I've subsequently >> done each >> time). >> >> >> Out of curiosity, how did this work? Isn't most mDNS traffic TTL=1? >> >> >> I don't know about all the various implementations out there (of if the >> standard says anything), but my modern-ish OSX box does 255: >> > > Ok. Though I note that they're both link-local multicast groups, so again > I wonder how people did them cross-subnet. > Oh, I'm not sure if v6 link-local groups can/should be routed. I see no reason that a device could be configured to allow joins from multiple links/LANs and forward frames accordingly. ff02::fb is in the link-local scope however. Interestingly, ff05::fb is a site-local scoped address that's been set aside, but I don't know or haven't run across any clients that use this. It's documented in http://tools.ietf.org/html/draft-cheshire-dnsext-multicastdns-15 In the past, I did this with the v4 traffic. Cheers, jof _______________________________________________ juniper-nsp mailing list [email protected] https://puck.nether.net/mailman/listinfo/juniper-nsp
