Bonjour Gateway on 7.4

I work in a k-12 school district and we have around 100 ipads, 10 apple tvs, a half dozen air print capable printers, and about 300 mac computers.
I'm running vwlc 7.4 with fifty 3602i ap's.
I'm unable to get the mdns / bonjour gatway to work. I have it enabled it, added the different services I want, and enabled the profiles on the wlans.
I have followed the guide @ http://www.cisco.com/en/US/docs/wireless/technology/bonjour/Bonjour_DG_Guide.pdf which seems pretty simple.
Is there anything I need to do to my switches? Do I need to enable multicast or pim?
I have the ipads and the apple tvs on the same subnet/vlan. It seems to flap. Sometimes when I try to airplay from a ipad, the apple tvs will show up right away. The next time they won't (this is most of the time).
I also have a imac that has apple remote desktop installed. If the imac is on the wired network, it can pull up all the other computers that are on the wired network with it, but no wireless clients. When I put the imac onto the wireless network along with the other wirless mac's, apple remote desktop does not pull up any clients from either the wired or wireless.
Non of the ipads can see any of the air print pinters on my wired network.
Is there something more I need to do on my switching, or shouldn't the bounjour gateway take care of this?

#Display the Multicast config, try with Multicast mode Unicast.
#mDNS does two things
a) Eliminate Multicast Routing being enabled on Wired side when WLC and AP on different subnet to avoid Multicast capwap routing.
b) Voluntarily display the Bonjour services on other wired/wireless vlan based on the configuration.
#Rules, Limitations and Guidelines when using Multicasting on Wireless Controller.
https://supportforums.cisco.com/docs/DOC-32337
#Multicast mode Multicast is for wireless Multicast traffic efficiency on capwap only(btw WLC to AP) and it doesn't affect the actual Multicast traffic and with mDNS, M-M mode is optional and can also say it is of not much use because only Bonjour Discovery is Multicast and real data connection is P2P tcp unicast.

Similar Messages

Client isolation and the Bonjour gateway on WLC 7.4.1

Hi,
I am considering upgrading our 5508 WLCs to version 7.4.1 to take advantage of the Bonjour gateway. What I want to do is allow clients on our guest wireless network to access things like the Apple TV in our conference rooms. My intention would be to have the Apple TVs on a separate vlan. Obviously, the Bonjour gateway would allow for access between these 2 networks. The question I have is this. If I have client isolation turned on my guest wireless network, is it still possible for these devices to access Apple TVs on another network?
Any and all information is appreciated!
Thanks!

If the Apple TV on the wireless lan , that wont work.
here is the reference:
http://www.cisco.com/en/US/products/hw/wireless/ps4570/products_tech_note09186a0080bb1d7c.shtml
please make sure to rate correct answers

Bonjour Gateway - Airplay / AirServer - Random Disconnects

I am experiencing random disconnects during an Airplay session to AirServer. Airserver disappears from the screen and Airplay session is gone. Here is the details of my setup:
WLC 5508 7.5.102.0
1142n APs
AirServer (1.9.4) installed on wired PCs.
Wireless clients (iOS Devices 7.x and 6.x) use Airplay to mirror to the PCs running AirServer.
APs are in mDNS mode and snooping the vlan the PCs reside in.
Wireless clients in separate BYOD WLAN.
Enabled bonjour gateway and mDNS AP (trunk mode)
http://www.cisco.com/en/US/docs/wireless/technology/bonjour/7.5/Bonjour_Gateway_Phase-2_WLC_software_release_7.5.html#wp44311
Enabled videostream
http://www.cisco.com/en/US/products/ps10315/products_tech_note09186a0080b6e11e.shtml
Verified via packet capture the client traffic is being marked for QoS (and Gold enabled on BYOD WLAN)
Differentiated Services Field: 0x80 (DSCP 0x20: Class Selector 4; ECN: 0x00: Not-ECT (Not ECN-Capable Transport))
This is an intermittent issue. I can play a YouTube video for 60 mins with no issues sometimes. Sometimes the disconnect happens. WLC mdns error debug output does not look significantly different when the crash happens.
Any thoughts? Similar experience?

Alright, long story short: Got a wirless repeater, set the printer up to connect wireless, now everything works fine, including AirPrint.
Btw.: Even though it says it is not possible, it is actually possible to access the printer via WLAN and LAN (wired) simultaneosly.
Thanks anyway. I think this can be marked as solved

WLC Bonjour Gateway - Ichat

Hi,
I have an issue with bonjour in my network, I cant get the ichat work when the mdns feature is enable.
We have 2 WLC 5508 and 2504, both of them are in version 8.0.
I put the string _presence._tcp.local. in the local mdns base but the ichat still doesn't work.
Someone had this issue to? And know how to fix it?
PD. I already have a SR in the TAC, but I don't a light from they.

What is the WLC model & software version used in this case ?
Rasika

5508 mDNS (Bonjour Gateway) Communication Error

Hi all,
I have configured mDNS on my 5508 controller for AirPrint but clients are experiencing communication errors when trying to print to the device. I believe the config is accurate on the controller (8.0.100.0) and the device is visible:
Global multicast mode and IGMP snooping enabled
AP multicast mode (multicast): 224.0.0.251 (i'm not 100% sure this multicast address should be used according to a config document I have read)
Default mdns profile has been added to a single interface (which is a member of an interface group)
P2P blocking is disabled
Switch config:
ip multicast routing enabled and pim sparse-mode enabled under the vlan interface.
Any suggestion would be most welcome.
Thanks.

Your multicast should be changed to 239.x.x.x, which maybe use the last three octets of your wlc management ip. Make sure that you have both AppleTV and AirTunes enabled for bonjour services (for Mirror), but make sure you have the specific services for that printer. Make sure mDNS Global Snooping is also enabled. This is really all you need as long as nothing is blocking bonjour. You should also see the devices in the mDNS Domain Names.
Scott

Local Bonjour Gateway display

Firstly, let me tell you about the setup.
SSID for clients and SSID for Apple TV devices common across all buildings in the campus. Uses 802.1x for clients and PSK for Apple TV devices.
Interface group for the SSID uses multiple vlans for the SSID, so also common across the campus. Interface set up for the Apple TV devices, again common across campus.
Now, what I want to be able to do is, when using Apple TV, only show the local Apple TV devices rather than the list that the controller knows about. Now, potentially we are going to be rolling these out everywhere, so the latter approach is not scalable.
I need a user to go to a room with an Apple TV device and only for it only to show the devices that are nearby, rather than a huge long list of devices on the campus.
Is this possible? Will it require a redesign to split SSIDs/VLANs to a per building basis?

Think I have just found the answer. You need to configure location specific services in the WLC CLI. If you run the following command it should tell you if LSS is enabled or not
show mdns service summary
To enable LSS just run the following
config mdns service lss enable <service-name>
Apparently this uses the RRM DB to filter using the ap neighbor list. Think you need 7.6 though.

CSCuh52683 - Bonjour mDNS proxy print servers not supported on mDNS Bonjour Gateway

Since 3rd party print servers are not supported. The question becomes what print servers do you recommend and are supported?

I moved this to the more appropriate "Mac OS X Technologies > Networking and the Web" forum, since it's become apparent that it involves more than Time Capsules.

Wired mDNS (bonjour gateway) support using a centralized 5508 across 3 layer sites

Is it possible to support wired mDNS across sites?
Scenario is as follows:
Hub site hosts the 5508 that services the hub site and 2 spoke sites separated by L3 routing.
The hub site contains the wireless subnets (Layer 2 trunk).
Hub site has wired Apple TVs that the wireless ssids need access to.
mDNS is setup and working between the wireless ssids/vlans/subnets and the wired LAN subnet at the hub site.
We now want to connect Apple TVs to the LAN subnets at the spoke sites and I can't see how to accomplish this as the 5508 has to be physically connected to the wired LAN subnet somehow...
Is there any way to do this? I thought of purchasing a 2504, but then it would have only knowledge of the wired LAN, and not the wireless ssids/vlans/subnets.

I think I found my answer. Has anyone actually done this?
mDNS AP
The mDNS AP feature allows the controller to have visibility of wired service providers that are on VLANs that are not visible to the
controller. You can configure any AP as an mDNS AP and enable the AP to forward mDNS packets to the controller. VLAN visibility on the
controller is achieved by APs that forward the mDNS advertisements to the controller. The mDNS packets between the AP and the controller
are forwarded in Control and Provisioning of Wireless Access Points (CAPWAP) data tunnel that is similar to the mDNS packets from a
wireless client. Only CAPWAP v4 tunnels are supported. APs can be in either the access port or the trunk port to learn the mDNS packets
from the wired side and forward them to the controller.
You can use the configurable knob that is provided on the controller to start or stop mDNS packet forwarding from a specific AP. You can
also use this configuration to specify the VLANs from which the AP should snoop the mDNS advertisements from the wired side. The maximum
number of VLANs that an AP can snoop is 10.
If the AP is in the access port, you should not configure any VLANs on the AP to snoop. The AP sends untagged packets when a query is to be
sent. When an mDNS advertisement is received by the mDNS AP, the VLAN information is not passed on to the controller. The service
provider's VLAN that is learned through the mDNS AP's access VLAN is maintained as 0 in the controller.
By default, the mDNS AP snoops in native VLAN. When an mDNS AP is enabled, native VLAN snooping is enabled by default and the VLAN
information is passed as 0 for advertisements received on the native VLAN.
The mDNS AP feature is supported only on local mode and monitor mode APs.
The mDNS AP configuration is retained on those mDNS APs even if global mDNs snooping is disabled.

WLC - AP Groups - Multicast - Bonjour - Apple TVv3

Good Morning
first off - Should start off by saying I have followed the Apple Bonjour deployment guide [except for interface group] portion
I have searched high and low, here and there to no avail.
http://www.cisco.com/en/US/products/hw/wireless/ps4570/products_tech_note09186a0080bb1d7c.shtml
I am aware that the bonjour gateway IOS may or may not come out in Oct/Nov 2012, which maybe my only option at this point.
Is this not working because of my AP groups setup or have I misssed something
I can only get bonjour to work if multicast - unicast mode is selected, but our network slowly grinds to a halt, so it is not an option
when I first connect to the wireless I see 1 bonjour device for about 3 minutes and then disappears.
I can not see the appletv at all with an ipad, airplay does not appear at all.
We have the following setup.
2 campuses - Campus 2 is simular setup, but WLCs higher model and ios 7.2 and clients and subnets are double
Campus 1
2 WLC 4404 ios 7.0.230.0
30 AP groups mapped to 30 Interfaces using subnets with /23 bit subnetmasks
multicast - multicast is set with multicast addresses of
controller 1 239.239.5.1 and
controller 2 239.239.5.2
multicast is enabled
IGMPsnooping as well
On Switch multicast routing is enabled
all AP group subnets and Mgmt vlans are PIM enabled dense mode
set up a trunk to ubuntu server to act as a bonjour gateway, installed avahi and vlan
mapped all AP and mgmt vlans to Ubuntu server.
avahi see the following + more
+ eth0.136 IPv6 Apple TV                                      _airplay._tcp        local
+ eth0.136 IPv4 Apple TV                                      _airplay._tcp        local
+ eth0.134 IPv6 Apple TV                                      _airplay._tcp        local
+ eth0.134 IPv4 Apple TV                                      _airplay._tcp        local
+ eth0.132 IPv6 Apple TV                                      _airplay._tcp        local
+ eth0.132 IPv4 Apple TV                                      _airplay._tcp        local
+ eth0.130 IPv6 Apple TV                                      _airplay._tcp        local
more goes on forever
+ eth0.136 IPv4 xyz Library                             Apple Home Sharing   local
show ip multicast
Multicast Routing: enabled
Multicast Multipath: disabled
Multicast Route limit: No limit
Multicast Triggered RPF check: enabled
Multicast Fallback group mode: Dense
show ip multicast interface vlan 128
Vlan128 is up, line protocol is up
Internet address is x.x.128.1/23
Multicast routing: enabled
Multicast switching: fast
Multicast packets in/out: 14671352/276693
Multicast boundary: not set
Multicast TTL threshold: 0
Multicast Tagswitching: disabled
Where do I go from here?

Thanks Yahya and Stephen
I have tried to simplify my config as much as possible.
wlc 4404
Ethernet Multicast Forwarding............... Enable
Ethernet Broadcast Forwarding............... Enable
AP Multicast/Broadcast Mode................. Multicast   Address : 239.239.5.1
IGMP snooping............................... Enabled
IGMP timeout................................ 60 seconds
IGMP Query Interval......................... 20 seconds
I have an interface created 10.x.x.x/23
I have created a new SSID APPLETV - assigned Interface
I have added the SSID to just 1 AP Group
show network multicast mgid summary
Layer2 MGID Mapping:
InterfaceName                    vlanId   MGID
2upadhoc                         136      27
Layer3 MGID Mapping:
Number of Layer3 MGIDs........................... 11
My vlan does not show up here.
I only have 2 devices in this vlan the AppleTV and IPAD
checking the switch for all required vlans
show ip multicast
Multicast Routing: enabled
Multicast Multipath: disabled
Multicast Route limit: No limit
Multicast Triggered RPF check: enabled
Multicast Fallback group mode: Dense
admin interface
Management, AP-Manger
Vlan12 is up, line protocol is up
Internet address is x.x.x.1/24
Multicast routing: enabled
Multicast switching: fast
Multicast packets in/out: 238489978/724352
Multicast boundary: not set
Multicast TTL threshold: 0
Multicast Tagswitching: disabled
AP vlan
Vlan222 is up, line protocol is up
Internet address is x.y.z.1/24
Multicast routing: enabled
Multicast switching: fast
Multicast packets in/out: 11423/238338583
Multicast boundary: not set
Multicast TTL threshold: 0
Multicast Tagswitching: disabled
The test Apple TV Vlan
Vlan136 is up, line protocol is up
Internet address is x.xx.1/23
Multicast routing: enabled
Multicast switching: fast
Multicast packets in/out: 156740/0
Multicast boundary: not set
Multicast TTL threshold: 0
Multicast Tagswitching: disabled
interface Vlan12
ip pim dense-mode
interface Vlan222
ip pim dense-mode
interface Vlan136
ip pim dense-mode
Show ip igmp groups
Group Address    Interface                Uptime    Expires   Last Reporter
224.0.1.39       Vlan136                  2d00h     00:02:35 x.x.x.1
So just to recap
Same subnet in a AP Group
New SSID
multicast enabled on WLC - using multicast multicast mode
Broadcast forward enable
Switch -Multicast routing enabled
all vlans enabled for PIM
2 devices - added Imac to see if I could home share through Itunes.
end result
no bonjour clients, no apple tv, no airplay
Bonjour Gateway device - although same subnet it shouldn't be needed
eth0.12   Link encap:Ethernet HWaddr bc:30:5b:x:x:x
          inet addr:x.x.x.244 Bcast:x.x.x.255 Mask:255.255.255.0
          inet6 addr: fe80::be30:5bff:fed6:a178/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
          RX packets:55005 errors:0 dropped:115 overruns:0 frame:0
          TX packets:23003 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:2776156 (2.7 MB) TX bytes:11285256 (11.2 MB)
eth0.136 Link encap:Ethernet HWaddr bc:30:5b:x:x:x
          inet addr:x.x.x.9 Bcast:x.x.x.255 Mask:255.255.254.0
          inet6 addr: fe80::be30:5bff:fed6:a178/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
          RX packets:42167 errors:0 dropped:115 overruns:0 frame:0
          TX packets:22340 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:3251242 (3.2 MB) TX bytes:10373581 (10.3 MB)
eth0.222 Link encap:Ethernet HWaddr bc:30:5b:xx:xx:xx
          inet addr:x.x.x.9 Bcast:x.x.x.255 Mask:255.255.255.0
          inet6 addr: fe80::be30:5bff:fed6:a178/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
          RX packets:152397 errors:0 dropped:115 overruns:0 frame:0
          TX packets:23768 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:12795709 (12.7 MB) TX bytes:11318103 (11.3 MB)
+ eth0.222 IPv6 67665ACD317A45B0                              _appletv-v2._tcp     local
+ eth0.222 IPv4 67665ACD317A45B0                              _appletv-v2._tcp     local
+ eth0.136 IPv6 67665ACD317A45B0                              _appletv-v2._tcp     local
+ eth0.136 IPv4 67665ACD317A45B0                              _appletv-v2._tcp     local
+ eth0.12 IPv6 67665ACD317A45B0                              _appletv-v2._tcp     local
+ eth0.12 IPv4 67665ACD317A45B0                              _appletv-v2._tcp     local
Should Bonjour work same subnet with these settings?
I am going to have read more about the Interface groups and the Multicast vlan.

How do I get my ARD/AppleTV to work through bonjour across multiple vlans?

I am having a heck of a time, I have 200 iMacs running 10.9 and a 10.9 server. We also have 30 apple TVs. These are spread over 5 distinct vlans and I am having a heck of a time getting them all to see each other. I found some information that started getting over my head about adding a bunch of dns entries for each device which would not scale well, and all seemed to be for printers anyways so I have turned here for some hopeful assistance.

Bonjour is designed to stay on the local LAN and not go across routers, with VLANs you have split your network up and Bonjour normally will not cross the splits even if you enable TCP/IP routing between VLANs.
There are various schemes aimed more for site-to-site situations to force Bonjour across links but in your case you might want to look at some newer devices specifically made to 'manage' Bonjour traffic.
Note: Bonjour is the same thing as mDNS i.e. multicast DNS.
See
http://www.cisco.com/c/en/us/td/docs/wireless/technology/bonjour/7-5/Bonjour_Gat eway_Phase-2_WLC_software_release_7-5.html
http://www.aerohive.com/products/software-management/bonjour-gateway
http://www.xirrus.com/Products/Network-Management/Network-Services/Bonjour-Direc tor
http://www.merunetworks.com/products/technology/bonjour/index.html
Apple's AirPort Extreme can also do 'Wide Area' Bonjour between two or more sites but I don't feel it is suited to your case.

How do i get my bonjour to work?

I have bonjour enabled and have gotten it to work before. Somewhere during the last 2 OS updates I stopped being able to see others on my network through bonjour (ichat). I have a desktop wired to an airport. Others on the network can see me, but I cannot see them. I have already tried repairing disc permissions to no avail.
As a side note, laptops have become unable to print from the shared printer (wired directly to desktop computer).
How do I get it to work again?

Bonjour is designed to stay on the local LAN and not go across routers, with VLANs you have split your network up and Bonjour normally will not cross the splits even if you enable TCP/IP routing between VLANs.
There are various schemes aimed more for site-to-site situations to force Bonjour across links but in your case you might want to look at some newer devices specifically made to 'manage' Bonjour traffic.
Note: Bonjour is the same thing as mDNS i.e. multicast DNS.
See
http://www.cisco.com/c/en/us/td/docs/wireless/technology/bonjour/7-5/Bonjour_Gat eway_Phase-2_WLC_software_release_7-5.html
http://www.aerohive.com/products/software-management/bonjour-gateway
http://www.xirrus.com/Products/Network-Management/Network-Services/Bonjour-Direc tor
http://www.merunetworks.com/products/technology/bonjour/index.html
Apple's AirPort Extreme can also do 'Wide Area' Bonjour between two or more sites but I don't feel it is suited to your case.

Apple TV/Bonjour:Localized Implementation

Hi, I am working with a network that spans multiple campuses and we are in the process of installing Apple TVs to conference room projectors in order to do wireless projecting. Our end result is that we want to only have local Apple TVs show up on user's devices(for instance, when connected wirelessly to APs closest to the conference room, only show that Apple TV, and in most general locations, show no Apple TV.) The way our network is set up is that there are 2 major VLANS, the one used for wireless connection via 802.1x, and the wired network.
We have used this guide and deployed the avahi bonjour gateway, which gives us connections over L3. But that is just the issue. Now all Apple TVs will show up to a user's device, regardless of physical location. Does anybody know of an easy way to:
1. Determine the AP a client is connected from(possibly through a SNMP trap?)
2. If the AP is a specified AP, allow the visibility of the specific Apple TV
The only thing I can think of is that in addition of having 1 general purpose wired and wireless VLAN(I'll call them 10 and 11 for namesake), and then create additional VLANS per conference room, for wired devices using the conference room's ethernet jacks(including the Apple TV, it can't do 802.1x), and for the local Access points in that area. So that breaks down to
10-general wired
11-general wireless
12-conference room 1 wired/apple TV and nearby wireless APs
13-conference room 2 wired/apple TV and nearby wireless APs
etc.
Also, according to many articles online, Cisco is going to be integrating a bonjour gateway into their wireless controllers, which should be able to replace the avahi box. It also states that it will have the ability to create user-based access to certain bonjour devices like Apple TVs, but is there a possibility that there will also be the ability to restrict by connected AP?

I don't think there is a good way to prevent that. I don't think the wlc (future code) will have the ability to deny a client access to a device unless its close to an access point.
The only way I can see this work is if you create a vlan for every Apple TV and and the AP in that room on a different ap group so you can map the Apple TV SSID to that specific vlan. You would need I remove the bonjour gateway though.
This means you have to create more vlans (one per Apple TV), add ap groups and create small subnets.
Of course I'm thinking out loud, but that would be the only way I can see it working right now.
Sent from Cisco Technical Support iPhone App

WLC 7.5 Bonjour/mDNS at multiple sites

Hi all,
After reviewing the mDNS/Bonjour features of WLC software 7.5 (although most applies for 7.4 as well), I am left somewhat confused. It seems that once services are discovered, there is no way to filter them to be advertised only to the site they were discovered at.
To simplify our environment, consider the following scenario:
A single WISM2 controller
A single SSID using dynamic VLANs deployed across diverse locations, with Wi-Fi mDNS discoveryeg. Site A has VLANs 11, 12, 13, Site B has VLANs 21, 22, 23
Wired mDNS discovery at both siteseg. Site A has VLANs 101, 102, 103, Site B has VLANs 201, 202, 203
In the instance, let's say a printer, is discovered on wired VLAN 101, and I only want to advertise it to the Site A Wi-Fi VLANs, it seems that I can't. All VLANs that are configured to advertise the printer mDNS service records receive it, which means Site B sees the printer at Site A.
Is there any way to achieve what I want here? It seems a crazy limitation that I can't filter the VLANs to what advertisements they receive, considering the service provider database has the learnt VLAN information in it.
Alex

Scott,
     LSS doesn't support mDNS-AP, it only applies over the wireless: http://www.cisco.com/en/US/docs/wireless/controller/7.5/config_guide/b_cg75_chapter_01011.html – about halfway down under Configuring Multicast Domain Name System, it states that there is no location awareness for wired service provider devices (Apple TVs). It also states that mDNS-AP devices are considered wired – even though these devices were discovered by the APs, they don’t get filtered by LSS.
     If the Service provider is in the same wireless SSID/VLAN, you wouldn't need Bonjour Gateway. If it's in a different wireless SSID/VLAN, but on the same AP, you'd be hairpinning traffic and doubling up wireless airtime. LSS doesn't make much sense to me, unless I'm missing something.
     Our solution so far is to extend the wireless VLAN out to a single port on the wired network, but the AppleTV can only be plugged into that port. It limits our user's mobility with the devices.
     I've sent this on to our Cisco reps, and they are pushing it up the chain for a feature request.
Mark

WLC 5508 -7.4.100 mDNS Bonjour snooping

Hello
Have 7.4 installed and configured for Bonjour Snooping. All is working, but working too well. We have a large campus that house 2 schools and each school is complaining that they can see the other schools AppleTV devices.
I have played around with a few different scenarios to see if I can localize the bonjour traffic.
I guess I am looking to create a logical split for bonjour devices amoung the schools.
Apple came to the school and informed us that the IPAD has a limit of 64 devices that can be seen via the bonjour. At some point we will have over 100 AppleTV added.
so we have 3 wlc 5508's with 7.4.100
we have 2 SSIDs that span the whole campus
using AP groups to segment the floors in buildings
So the schools are logically split with AP groups
Here is what I have tried
I created few mDNS profiles and assigned the services for Apple TV - let's call them school1 and school2
I assign the mDNS profiles to the interfaces dedicated each school
enable snooping on the WLAN with profile of none
The end result is that devices from both schools can be seen.
I tried to create new ssid for apple TVs and a new ssid for 1 schools teachers
I followed the vlan select example
http://www.cisco.com/en/US/products/hw/wireless/ps4570/products_tech_note09186a0080bb1d7c.shtml
end result is that devices from both schools can be seen
I have tried the mDNS without multicast enabled just like the video shows to no avail - I assume maybe my AP groups might be more complicated then the example of just 2 vlans
https://supportforums.cisco.com/community/netpro/wireless-mobility/begin-wireless/blog/2013/01/01/wireless-lan-controller-wlc-release-74--bonjour-gateway-configuration-example
I have tried combinations of things, but I must be missing something
In the webinar, Cisco said it will use filtering to restrict which clients can see which services (Apple TV's, etc). What will Cisco use to filter Bonjour requests?
according to this article
http://www.pcadvisor.co.uk/news/network-wifi/3376119/cisco-answers-user-questions-about-upcoming-apple-bonjour-gateway/#ixzz2SIDqFH49
The filtering options are: · Per WLAN/SSID · Per VLAN or AP Group · Per Interface Group (which is a group of VLANs pooled together).
A Bonjour service policy can be created and applied on any one of the above criteria. In the future, we will support per-user Bonjour service policies which will come as a RADIUS attribute from the AAA server.
Read more: http://www.pcadvisor.co.uk/news/network-wifi/3376119/cisco-answers-user-questions-about-upcoming-apple-bonjour-gateway/#ixzz2SZqMYpdh
Cheers
Any insight would be appreciated

Here are the ACLs for the controller
acl create BlockBonjour
acl apply BlockBonjour
acl counter start
acl rule add BlockBonjour 1
acl rule add BlockBonjour 2
acl rule action BlockBonjour 1 deny
acl rule action BlockBonjour 2 permit
acl rule destination address BlockBonjour 1 224.0.0.251 255.255.255.255
acl rule destination address BlockBonjour 2 0.0.0.0 0.0.0.0
acl rule destination port range BlockBonjour 1 0 65535
acl rule destination port range BlockBonjour 2 0 65535
acl rule source address BlockBonjour 1 0.0.0.0 0.0.0.0
acl rule source address BlockBonjour 2 0.0.0.0 0.0.0.0
acl rule source port range BlockBonjour 1 0 65535
acl rule source port range BlockBonjour 2 0 65535
acl rule direction BlockBonjour 1 In
acl rule direction BlockBonjour 2 Any
acl rule dscp BlockBonjour 1 Any
acl rule dscp BlockBonjour 2 Any
acl rule protocol BlockBonjour 1 Any
acl rule protocol BlockBonjour 2 Any
acl apply BlockBonjour ipv6 acl create BlockAllIPv6
ipv6 acl apply BlockAllIPv6
ipv6 acl rule add BlockAllIPv6 1
ipv6 acl rule action BlockAllIPv6 1 deny
ipv6 acl rule destination address BlockAllIPv6 1 :: 0
ipv6 acl rule destination port range BlockAllIPv6 1 0 65535
ipv6 acl rule source address BlockAllIPv6 1 :: 0
ipv6 acl rule source port range BlockAllIPv6 1 0 65535
ipv6 acl rule direction BlockAllIPv6 1 Any
ipv6 acl rule dscp BlockAllIPv6 1 Any
ipv6 acl rule protocol BlockAllIPv6 1 Any
ipv6 acl apply BlockAllIPv6
Apply to wlan: The wlan index is used in this case, the first wlan created on controller
wlan acl 1 BlockBonjour
wlan ipv6 acl 1 BlockAllIPv6

7.4.100.0 and bonjour - worth the risk?

Afternoon
I'm getting pressure from management to sort out a useable bonour gateway for our wireless systems so we can utilise Apple TV, etc.
I've been keeping an eye on 7.4.100.0 and now 7.4.100.60 and in my opinion it's just not ready, there seem to be way too many issues with it.
I would rather wait until 7.4.110.0 or even 7.5.x before I try it out, rather than disrupt our service just to get Apple TV working. I have said as much as the pressure has lessened but give it a day and questions will come in again.
I'm just after other opinions. What do you think? Better to wait?
Thanks

Well it depends. I have run 7.4 with no issues, as long as your not doing HA:) it also depends on what things your are looking for to work with bonjour. v7.5 will have the same fixes as v7.4 but with added feature sets. That is what you need to know. Anyways, you can alway bring up the Avahi bonjour gateway which works well. You just need to see what works best for you. I have no issues when running the Avahi, but the Cisco's bonjour gateway is getting better.
http://www.cisco.com/en/US/products/hw/wireless/ps4570/products_tech_note09186a0080bb1d7c.shtml
Sent from Cisco Technical Support iPhone App

Bonjour Gateway on 7.4

Similar Messages

Maybe you are looking for