BT HomeHub 5 - mDNS / Bonjour incompatiblity / BUG...

I stringly believe that the BT HomeHub 5 has an incompatibility with Apple's Bonjour service, which is an implementation of mDNS - an industry standard.
When my computer is connected to my home hub using WiFi then bonjour works perfectly. Specifically: I can detect and use my Network attached printer.
When my computer is connected to my home hub using a Cable and WiFi is switched off (on the PC) then I cannot detect and use my Network attached printer.
Here is a wireshark dump of the mDNS packets when connected with WiFi - note the proper query and response:
Now here is the wireshark screen shot when connected with a wire - note the queries being sent, but NO responses.
I believe the home hub is somehow not passing the queries, or blocking the responses, when usng Wired instead of WiFi.

I too have exactly the same problem - it is extremely frustrating - as it is definitely a HH5 problem but BT do not seem to have recognised it as such (When I moved from HH4 to HH5 I started to have problems). On these forums there is lots of red-herring advice about separating the 2.4GHz and 5GHz WiFi networks (or switching one off) and things apparently working after. I believe that the essential problem is that the HH5 does not allow the proper broadcast of parts of the nDNS protocol between networks (i.e. between the wired, 2.4GHz and 5GHz wifi networks) - so bonjour/airplay will work if the client and the server are on the same physical network, but not if they are on different networks -e.g. one on wired and another on wireless.
I have been playing with wireshark too, and it is is clear that if you switch on a bonjour enabled server then the initial announcement of the device does make it between the networks, but there is some later part of the protocol that is being blocked - It would be really great if there was a BT engineer responsible for HH5 what was reading this that could look into this problem - I have tried all the usual support routes, but to no avail.
It should be noted that mDNS is not just an apple protocol - on my home network a non-apple network printer was able to announce itself on DHCP to windows clients before HH5.

Similar Messages

MDNS/Bonjour port 0 service registration broken on Solaris 11 Express

I'm using Solaris 11 Express on x86-64, and found a pretty bad bug with registering mDNS/Bonjour services. Most service registration works fine, but registering a service that uses port 0 does not work. It claims to work, but the service never gets registered, and can't be browsed for.
It's easy to reproduce: in one window, run
$ dns-sd -B test.tcp
You should see 'Browsing for test.tcp', and no services found.
Then, in another window, run
$ dns-sd -R solaris test.tcp local. 0
to register a test.tcp service on port 0. It seems to succeed, but the first window doesn't show the new service.
Now, kill the 'dns-sd -R' registration process with ctrl-c, and run
$ dns-sd -R solaris test.tcp local. 1
This time, the first window will show the service. Registering on port 1 works fine, but port 0 does not.
Port 0 service registration works fine on every other OS, and many services use port 0 by convention if they aren't advertising an actual service. For example, netatalk can register a device-info.tcp service to mimic a certain Mac model (so your Solaris server shows up with an Xserve icon). This "service" uses port 0, and doesn't work on S11 Express unless the source is changed to a non-zero port.
Can someone test this out on Solaris 11 EA and other versions, to see if it's been fixed or not?
Edited by: 887058 on Sep 22, 2011 11:57 PM

It is registering fine with port 0. You can test by trying to register the same service on another host in the local network
with the same service name and port. You will see the service name automatically renamed.
For example:
root@estrada:~# dns-sd -R solaris test.tcp local. 0
Registering Service solaris._test._tcp.local. port 0
Got a reply for solaris._test._tcp.local.: Name now registered and active
root@testz:~# dns-sd -R solaris test.tcp local. 0
Registering Service solaris._test._tcp.local. port 0
Got a reply for solaris (2)._test._tcp.local.: Name now registered and active
^C
You can also query and see the SRV record for it:
# dns-sd -Q solaris._test._tcp.local. SRV
Timestamp A/R Flags if Name T C Rdata
23:38:58.949 Add 2 2 solaris._test._tcp.local. 33 1 21 bytes: 00 00 00 00 00 00 07 65 73 74 72 61 64 61 05 6C 6F 63 61 6C 00
It appears to me the service is not seen in the service browse call. These port 0 registrations are used to indicate the service
is not available on the host so this could be by design. I have tested the same on Mac OS X 10.6.8 and observe the same
results.
Rishi

Firewall causes slow mDNS (Bonjour) Lookups

I'm planning to upgrade our company's tiger server to leopard soon and for testing purposes I'm running Leopard server (10.5.5) on another machine. I've worked out most of the issues except for one major one.
mDNS (Bonjour) lookups take about 60-90 seconds to resolve when the server's firewall is running. This is the same problem across lookups for any service (SSH via terminal, web, AFP). I don't plan to use mDNS on our network as the server will be running DNS for our LAN, but Time Machine backups always connect to the AFP share using the mDNS name rather than the server's Fully Qualified Domain Name. When this lookup takes such a long time it will more or less freeze the client system during this time.
Client machines aren't running firewalls locally.
This happens with both tiger and leopard clients.
I have tried setting the firewall to allow all connections from "any" to "any" but it still doesn't work.
I am not running DNS on the server but I have tried turning it on with still no luck.
Here are the results from running "sudo ipfw list":
00001 allow udp from any 626 to any dst-port 626
01000 allow ip from any to any via lo0
01010 deny log logamount 1000 ip from any to 127.0.0.0/8
01020 deny log logamount 1000 ip from 224.0.0.0/4 to any in
12300 allow tcp from any to any established
12301 allow tcp from any to any out
12302 allow udp from any to any out keep-state
12303 allow tcp from any to any dst-port 53 out keep-state
12303 allow udp from any to any dst-port 53 out keep-state
12304 allow udp from any to any in frag
12305 allow tcp from any to any dst-port 311
12306 allow tcp from any to any dst-port 625
12307 allow udp from any to any dst-port 626
12308 allow icmp from any to any icmptypes 8
12309 allow icmp from any to any icmptypes 0
12310 allow igmp from any to any
12311 allow esp from any to any
12312 allow gre from any to any
12313 allow udp from any to any dst-port 4500
12314 allow ip from 192.168.15.0/24 to any via en0 keep-state
12314 allow ip from 192.168.16.0/24 to any via en0 keep-state
12315 allow udp from any 68 to any dst-port 67 via en0
65534 deny log logamount 1000 ip from any to any
65535 allow ip from any to any
Note that this should block most services but allow machines on our internal subnets (192.168.15.0 and 192.168.16.0) to connect.
Any help or advice will be greatly appreciated.
Thanks.

I have independently confirmed Baerner's results. Last week I installed ethereal and Wireshark from the fink project and traced the IPP data packets between my desktop client and the print server. Bonjour is definitely using IPV6 in Leopard for printing services.
Reading the Wikipedia page, http://en.wikipedia.org/wiki/IPv6#Special_addresses, I used the ip6fw utility to add the firewall rule:
*01101 allow ipv6 from fe80::/10 to fe80::/10*
which allows link-local addresses to communicate with the server.
Printing on the server works well with the new firewall rule. I just need to find out how to get the Server Admin tool to set the rule from the FireWall GUI.

MDNS/Bonjour switchs randomly between multiple NICs

Dear Community,
I have a problem with a MacServer and multiple NICs...lets name it MSERV
NIC1 goes into the WWW (194.x.x.x) (Protected with ASA firewall)
NIC2 goes into LAN (172.x.x.x) (no firewall)
I need the WWW NIC for ProfileManager and also the LAN NIC for filesharing and TMB.
Both IPs are reachable from our LAN. DNS is good (nslookup shows up as expected) but mDNS/Bonjour makes some problems:
If I do ping MSERV.local sometimes it resolves the 194 and sometimes the 172 address.
This is a big problem for our time machine server backups! When clients choose the 194-path when they discover their backup target on the server, we generate a HUGE load on our ASA firewall.
How can I force Bonjour only to use the 172er LAN NIC.
Or did I get something dramatically wrong?
Any suggestions?

Tearjerker wrote:
Thank you for your reply!
So you mean to disable Bonjour on the server and set up DNS name as TM target?
Problem is here: How can I do this? Only way I know to connect to my backup server on clients is
System Prefs. -> TM -> Choose Disk. And as far as I know is this a Bonjour connection, right?
When I disable Bonjour service on the server (already tried!) my clients are unable to connect to their target.
Any thoughts?
You should not need to disable Bonjour. Bonjour aka. mDNS uses the .local domain suffix if you use a hostname like MSERV.local it will use Bonjour to try and find the TCP/IP address. (We will ignore the possibility someone might use the .local domain in an Active Directory setup.)
If your using a full-blown DNS e.g. server.domain.com then this is nothing to do with Bonjour and where it will point to is up to your DNS server. In this case you would point it to the 172.x.x.x IP address of the server.
As you want the same server to be contactable via the WAN interface as well for the rest of the work to access what you will want to do is have a 'split-horizon' DNS setup. With this the internal machines use an internal DNS server which points to the internal IP address of the server. You will also have the same domain hosted externally and the same server name but pointing to the external WAN IP address. What you do then have to be careful about is to ensure that all the external host names in that domain are defined also on the internal DNS server even if they are servers hosted externally. For example if you have a www.domain.com server hosted externally so it only has an external (public) IP address then you will still need to define this on your internal DNS server so your internal machines know where to find it, since your internal machines will be using your internal DNS server. If you fail to do this then while the outside world using an external DNS server may be able to access your www server, your internal machines would not be able to because your internal DNS server would otherwise say it does not exist.

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

Wlc 2106 mDns bonjour AirPlay AirTunes apple??? help

Hi guys,
Long time reader, first time poster.. I'm after some advice.
I'm failing dismally trying to configure a 2106 Wlc to allow apple device (iPhone, iPads) to stream AirPlay to an apple tv 2.
Now, I have this working perfectly with a 5508 WLC.
I understand that the apple devices all need to be on the same subnet (they are), that multicast needs to be enabled, and I've tried a variety of multicast addresses as mentioned in many posts.. Also the wired infrastructure is not the problem (as connecting net gear access points into the same wired infrastructure works fine).
I've also read posts where some people say the 2100series doesn't support AirPlay/bonjour/mDns and others saying they have had it work.
But I can't find a definitive answer.
Can anyone confirm or deny which WLC support AirPlay, as if I need to switch I want to make sure they do.
The 5508 works fine.
Anybody able to shed some wisdom?
Thanks Wayne.
Sent from Cisco Technical Support iPad App

I have a 2106 in the lab and it works fine. Here are a few screen shots and a link that may help..
http://www.cisco.com/en/US/docs/ios/12_2/ip/configuration/guide/1cfmulti.html

Delete mdns / Bonjour entry of old printer

On os x 10.5 server, i had set up print services.
These were published via bonjour.
After i installed a new printer, end deleted the old ones,
the Bonjour entries stil remained.
How can i delte the bonjour entries of the old (and not existing) printers?
Tried it with mdns, but was not experienced enough to get a result.
Tahnks for your help!

Check if the printer is set to default, if yes then remove it. Or goto safe mode and remove it.
Arnav Sharma | http://arnavsharma.net/ Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading
the thread.

MDNS/Bonjour ID for server stopped responding .

I recently moved a server and had to start from scratch with a clean install. Everything went pretty well until I switched external DNS providers; now, for whatever reason, my server's mDNS "serverName.local" address no longer responds...
My server is multihomed, with one interface configured with an external public IP address and the other interface using an IP internal to the office LAN. Both still working as intended. Internal IP responds normally, and the firewall allows all LAN ports.
I don't know if switching DNS providers has anything to do with it, other than it's in the series of events. I'm still poking around but I thought I'd post here for thoughts/opinions. Any ideas?

Turn on denied packet logging in the firewall.
Bonjour use multicast addresses in the 224.- "something" range.
http://www.iana.org/assignments/multicast-addresses
I would deny outgoing Bonjour packets on the Internet (WAN) interface and if using SMB, ony use it on the internal (LAN) interface (you set it up in /etc/smb.conf).

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

Disable mDNS, Bonjour

We have installed an Officejet Pro L7590 that we would like to turn off the mDNS broadcast. I see that I can change the mDNS name in the web server settings. There isn't a place to turn it off.
I tried to telnet into the print server and could not get in. I'm not the best at that so I may be missing a step or flag etc.
Thank you all in advance for any help.
MLTI Tech Lead

Sorry, I'm not aware of a method to disable mDNS on the printer.
This is an interesting request. Why do you want this turned off?
One option is to place a router between the network and your printer and configure it to block the mDNS ports (port 5353).
Regards / Jim B / Wireless Enthusiasts
( While I'm an embedded wireless systems engineer at work, on this forum I do not represent my former employer, Hewlett-Packard, or my current employer, Microsoft )
+ Click the White Kudos star on the left as a way to say "thank you" for helpful posts.

OpenVPN & mDNS (Bonjour) ???

Does anyone know how to get Bonjour working over a tunneled OpenVPN connection (NOT bridged)?? I'm using Viscosity as a client, if that helps.

It is registering fine with port 0. You can test by trying to register the same service on another host in the local network
with the same service name and port. You will see the service name automatically renamed.
For example:
root@estrada:~# dns-sd -R solaris test.tcp local. 0
Registering Service solaris._test._tcp.local. port 0
Got a reply for solaris._test._tcp.local.: Name now registered and active
root@testz:~# dns-sd -R solaris test.tcp local. 0
Registering Service solaris._test._tcp.local. port 0
Got a reply for solaris (2)._test._tcp.local.: Name now registered and active
^C
You can also query and see the SRV record for it:
# dns-sd -Q solaris._test._tcp.local. SRV
Timestamp A/R Flags if Name T C Rdata
23:38:58.949 Add 2 2 solaris._test._tcp.local. 33 1 21 bytes: 00 00 00 00 00 00 07 65 73 74 72 61 64 61 05 6C 6F 63 61 6C 00
It appears to me the service is not seen in the service browse call. These port 0 registrations are used to indicate the service
is not available on the host so this could be by design. I have tested the same on Mac OS X 10.6.8 and observe the same
results.
Rishi

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.

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.

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

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.

BT HomeHub 5 - mDNS / Bonjour incompatiblity / BUG...

Similar Messages

Maybe you are looking for