What controller code are you running?
**
Tim Cappalli*, *Network Engineer
LTS | Brandeis University
x67149 | (617) 701-7149
cappa...@brandeis.edu
On Wed, Apr 24, 2013 at 5:23 PM, Zeller, Tom S zel...@indiana.edu wrote:
I'm no longer directly involved in the WiFi here, but I was helping
We have a setup SSID that allows users to access Xpressconnect to configure for
802.1x. Android requires a connection to the Playstore in order to download a
cloudpath applet to complete the profile. So, this setup SSID, which was
restricted from external connections must be opened up so
Ryan, you don't need to open up your ssid to the playstore, xpressconnect has
the app locally on the server you have it running from. You should have three
options to download the xpressconnect app from,playstore, amazon app store and
locally. The devices will need to have allow apps from
Thanks. Unfortunately, I don't know how common that is (the option about
trusting non google apps), or if it's worth having to get those users to follow
more steps. I am not an android user, but for people that I have tested this
on, they are required to go to Playstore.
Ryan
From: The
It is actually pretty simple when they are directed to download the app the
third option in the pull down is local download, and xpressconnect with walk
them through enabling unknown source app install.
We are currently using xpressconnect and do not allow them to get to anything
but the
We have a Surface pro that works fine with Cisco and most of the Meru code
(though do have a problem with the 5.3-112 code)
I did not notice any problems when connected though.
Walter Reynolds
Principal Systems Security Development Engineer
Information and Technology
Instead of address range, you could also just open the port.
http://support.google.com/googleplay/bin/answer.py?hl=enanswer=1647495
ports required to use Google Play (TCP and UDP 5228).
Walter Reynolds
Principal Systems Security Development Engineer
Information and
Yeah, I want to say we tried that a while ago, and users still had issues. I
think that was the first thing I tried. I am only coming back to this after
seeing our previous work was opening up too much and people were using our
authenticated setup portal to do more than grab the config ;)
7.4MR is do out mid-May and the bug mentioned is fixed. The fix will
also be in 8.0.
Jeff
On Wednesday, April 24, 2013 at 11:59 AM, in message
1a1ed2e8-8cba-4e51-8f8d-a9d1cb15c...@ucsd.edu, Sullivan, Ryan
rasulli...@ucsd.edu wrote:
We have two WiSM2s that were ordered with 7.4.100.0 and have
7.4.100.0 has been very stable for us with failover pairs. We're enjoying
the AirPlay support too, which seems very solid.
On Wed, Apr 24, 2013 at 11:03 AM, Joe Roth jr...@binghamton.edu wrote:
Has anyone else seen stability issues with 7.4? We had to downgrade from
7.4 to 7.3 due to our
Mark-
Do you have a Doc on the Airplay thing? Sometimes they come from places other
than CCO...
-Lee Badman
From: The EDUCAUSE Wireless Issues Constituent Group Listserv
[mailto:WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU] On Behalf Of Mark Duling
Sent: Thursday, April 25, 2013 3:50 PM
To:
Hi Lee,
The have a new document based on 7.4:
http://www.cisco.com/en/US/docs/wireless/technology/bonjour/Bonjour_DG_Guide.pdf
It is as simple as it could be now. Doesn't require multicast. Just
enable the Bonjour snooping option globallly on each controller (off by
default), and turn it off
The default profile is even applied to the WLANs by default.
Our position is that airplay is officially unsupported at this point since
there are some unknowns administratively and politically with this, and we
have some old WiSMs running 7.0 for a bit more yet. So we're not
advertising this
Lee,
You can't test for every scenario. With the diverse client base of EDU,
I suspect we run up against many fringe-cases that are impossible to
duplicate (or test for) in a lab.
Jeff
On Thursday, April 25, 2013 at 12:15 PM, in message
On pre-7.4 code as long as you're on the same layer 2 vlan as the AppleTV and
have multicast enabled you'll still see the advertisements and be able to use
it, it's just when you try to cross L3 boundaries or disable multicast that
you'll need 7.4 or greater.
Josh Robertson
Sr. Wireless
Cool, thanks!
Lee H. Badman
Network Architect/Wireless TME
ITS, Syracuse University
315.443.3003
From: The EDUCAUSE Wireless Issues Constituent Group Listserv
[WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU] on behalf of Mark Duling
[mark.dul...@biola.edu]
Sent:
Hi Jeff,
Agreed on client stuff, but not on rebooting APs and code downloads that hang.
Its just too much in line with Cisco's long bug train a' running... Would be
different if this wasnt premium equipment.
Lee H. Badman
Network Architect/Wireless TME
ITS, Syracuse University
315.443.3003
The AP and code download issue, at least the bug mentioned, was a
problem with the code loaded at manufacturing on some WiSM2 cards. The
installed code was missing some of the AP boot code, and without the AP
boot code, AP's never got what they needed. Re-installing the same code
and/or newer
18 matches
Mail list logo
