Cisco Blogs


Cisco Blog > Mobility

Get Your WLAN Ready for Google Android L and Apple iOS 8

July 24, 2014 at 5:00 am PST

This fall your wireless networks will experience many devices upgrading to the new Android 5.0(L-release) and Apple iOS 8 releases (cue: IT managers groan). There have now been many blogs attempting to capture the enhancements expected with these releases. Today I am going to focus on describing how Android L and iOS 8 may affect customers deploying Cisco enterprise grade Wi-Fi networks based upon our research and testing of the Apple seed. Our verdict: Carry on with business as usual.

Here are four features we predict will have the most impact your networks:

1. Chromecast and Google Cast Enhancements (Android L)

Rishi Chandra, the Director of Chromecast Product Management announced that, starting with the Android L release, users have the ability to cast to your neighboring devices such as a TV without having to connect to your Wi-Fi network. In the demo, a phone used the cellular connection to connect to chromecast through the cloud. A variety of techniques are used to authenticate the users in the same room OR use a pin-code as an alternative. Users can Google Cast an ecosystem of applications or even their own applications over any Android or iOS device as well as Cloud based apps on Chrome.

Predicted Impact: Given that this feature works transparently to the Wi-Fi, it is expected that there is no impact on the WLAN in your classrooms or dorm rooms or auditoriums where this will most likely be used.

2. Peer-to-peer AirPlay discovery and playback (iOS 8)

Starting with the iOS 7.1 release, AirPlay devices will discover an AppleTV via the bluetooth network. Users could also secure their AppleTV via a 4 digit pin-code. With the iOS 8 release, Airplay devices can also mirror their content via Airdrop. This feature offers an alternative method for customers to discover and mirroring of Bonjour traffic without accessing the corporate Wi-Fi network.

Predicted Impact: Again this feature operates transparent to the Wi-Fi and therefore customers using this feature should not see any impact on the WLAN. Cisco wireless customers also have the ability to use the Service Discovery Gateway on Cisco IOS based switches, routers or wireless LAN controllers or the Bonjour Services Directory on AireOS controllers. Read More »

Tags: , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , ,

Extending Zeroconf Services: Cache Tuning

Introduction

With the introduction of Cisco mDNS Service Discovery Gateway in IOS, customers that have implemented the solution are observing client behavior they haven’t seen prior to extending services across subnet boundaries. One of the effects is the duplicate name issue seen when devices with enabled services are moved from one L3 subnet to another L3 subnet and these two subnets happen to be connected to the same router/switch running the Service Discovery Gateway (SDG).

Background

When devices (like a Mac OS X computer) offer a service such as Remote Login (SSH) or Screen Sharing (VNC), they will announce these services using mDNS/Bonjour/Zeroconf using their hostname as configured in ‘System Preferences -> Sharing -> Computer Name’ (see Fig. 1).
Read More »

Tags: , , , , , , , , , ,

Cisco Service Discovery Gateway – Enabling Zeroconf in Enterprise Networks

Cisco Service Discovery Gateway – Enabling Zeroconf in Enterprise Networks

I’ll admit it: I’m what others call an Apple fan boy. One of the many reasons for being one is the polished user experience and the ease-of-use of their products. One of the underlying technologies that enables the user to discover devices and services on the network is Zeroconf or, as Apple calls it, Bonjour.

Zeroconf consists of three major components:

  • Address auto configuration,
  • Naming –and–
  • Service discovery.

If your network doesn’t have a DHCP server or you haven’t statically assigned an IP address to your host, most operating systems will use an automatic private IP address. I’m not going into much detail on address auto configuration except that this is typically done using a technique called APIPA (Automatic Private IP Addressing) for IPv4 the host will use the famous 169.254.0.0/16 addresses or, in case of IPv6, by using link-local addresses only (FE80::/10) which has been designed into IPv6 as a basic functionality from day one. Also, naming is not of much of a concern in the context of this discussion. However, it is worth mentioning that Zeroconf names can contain Unicode characters and whitespace, which can make those names a lot more user friendly and meaningful contrary to pure DNS names.

The more interesting part, as it pertains to Zeroconf, is the service discovery. Read More »

Tags: , , , , , , , , , ,