I think that only applies to 224.0.x.x not all 224.x.x.x. see http://www.iana.org/assignments/multicast-addresses/multicast-addresses.xml#multicast-addresses-3
The range of addresses between 224.0.0.0 and 224.0.0.255, inclusive, is reserved for the use of routing protocols and other low-level topology discovery or maintenance protocols, such as gateway discovery and group membership reporting. Multicast routers should not forward any multicast datagram with destination addresses in this range, regardless of its TTL. Regards, Karl Gerling | Senior Solutions Engineer | ECE-Networking, ECE-Security Enterasys Networks | A Siemens Enterprise Communications Company Cell: 404-915-9409 Email: [email protected] *There is nothing more important than our customers. * On Fri, Apr 5, 2013 at 1:53 PM, Dave Traller <[email protected]> wrote: > 224.x.x.x is a link local multicast address which means I will not be > routed with dvmrp or pim > > On Apr 5, 2013, at 1:51 PM, Francois Scheun <[email protected]> wrote: > > > Hi All > > > > I've recently been faced with a similar requirement. Please see the > > Enterasys approach in attached pdf. > > > > I've tried another option using IGMP and DVMRP but it seems like the > > switches don't yet recognize mDNS traffic (224.0.0.251) as multicast and > > drops the packets. > > > > Would also appreciate some assistance should someone have a working > > Enterasys mDNS solution out there. > > > > > > > > Francois Scheün > > > > Senior Support Engineer > > > > Duxbury Networking > > Specialist Networking Distributor > > tel: +27 (0) 11 351 9800 > > fax: +27 (0) 11 646 3079 > > email: [email protected] > > > > web: www.duxbury.co.za <http://www.duxbury.co.za/> > > > > > > > > > > > > > > > > > > > > > > > > -----Original Message----- > > From: Jason Grubbs [mailto:[email protected]] > > Sent: Friday, April 05, 2013 7:22 PM > > To: Enterasys Customer Mailing List > > Subject: RE:[enterasys] Bonjour / mDNS > > > > We also use Aruba access points and have successfully enabled BonJour on > > our network. We created routed interfaces on the controllers (one for > > each vlan that we wanted to use AirPlay). Once we did that, BonJour was > > able to traverse the network. There may have been another step in the > > Aruba controller. I will double check and report back. > > > > Jason Grubbs > > Network Engineer > > Pottsgrove School District > > > > -----Original Message----- > > From: Summers, William [mailto:[email protected]] > > Sent: Friday, April 5, 2013 1:19 PM > > To: Enterasys Customer Mailing List > > Subject: RE:[enterasys] Bonjour / mDNS > > > > We created a series of Airplay SSIDs that keep traffic on a particular > > vlan as a work around. > > > > It's my understanding that BonJour/mDNS won't route without a proxy or > > middleware. Enterasys has a solution using policy, but my SE said it > would > > not improve the solution we already have (SSDs mapped to a vlan). (See > > webinar: > > > > http://pages.enterasys.com/ODWSupportingApplesBonjourProtocol_lp.html and > > other materials.) > > > > We're an aruba shop so we will be implementing Aurba's AirGroup this > > summer. > > > > William Summers > > Network Administrator > > Deerfield Academy > > Tel. 413.774.1838 > > ________________________________________ > > From: Auger, Jay (IS) [[email protected]] > > Sent: Friday, April 05, 2013 1:04 PM > > To: Enterasys Customer Mailing List > > Subject: [enterasys] Bonjour / mDNS > > > > Hello, > > > > Has anyone had the need/requirement to modify network configuration to > > allow for Bonjour (Apple) connectivity between routed subnets that are > > wired and wireless? > > > > If so, any tips/tricks/horror stories? Also, any reason why you chose > > _not_ to do it? > > > > Thanks! > > Jay > > > > > > * --To unsubscribe from enterasys, send email to > > [email protected]<mailto:[email protected]> with the body: unsubscribe > > enterasys [email protected] > > > > --- > > To unsubscribe from enterasys, send email to [email protected] with the > > body: unsubscribe enterasys [email protected] > > > > This email and any files transmitted with it are to be treated as > > confidential and as such are not to be used or disclosed except for the > > purpose for which it has been sent. Any views or opinions presented in > > this e-mail are solely those of the author and do not represent those of > > the Pottsgrove School District. The School District accepts no liability > > for any damage caused by this e-mail. The recipient is required to > > indemnify the School District against any claims for loss or damage > caused > > by any viruses or otherwise. > > > > --- > > To unsubscribe from enterasys, send email to [email protected] with the > > body: unsubscribe enterasys [email protected] > > > > --- > > To unsubscribe from enterasys, send email to [email protected] with the > body: unsubscribe enterasys [email protected] > > <EnterasysReferenceGuideforBonjourMulticastDiscoveryProtocol v1.1 > clean.pdf> > > --- > To unsubscribe from enterasys, send email to [email protected] with the > body: unsubscribe enterasys [email protected] > --- To unsubscribe from enterasys, send email to [email protected] with the body: unsubscribe enterasys [email protected]
