7.6 and up have dns acl feature…
http://www.cisco.com/c/en/us/td/docs/wireless/controller/7-6/configuration-guide/b_cg76/b_cg76_chapter_0110101.html#concept_AEEDD6D25578413784092B48A4636163
From: The EDUCAUSE Wireless Issues Constituent Group Listserv
[mailto:WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU
These devices prompt for a wireless network during the activation process,
but won't let a webauth succeed.
I like Hunter's idea of adding the Apple/Google/Antivirus sites to the
pre-webauth ACL. Cisco WLC's won't let you use DNS names for ACL entries,
d'oh! Is there a known list of these hosts so
Maybe I'm over simplifying this, but for the "average" user, don't those
devices have to be activated BEFORE you can see the settings screen?
Mike
On Thu, Jan 8, 2015 at 6:31 PM, Hunter Fuller wrote:
> This is what we do. While not authenticated to wireless you can still get
> to a few places -
This is what we do. While not authenticated to wireless you can still get
to a few places - Microsoft, apple, Google search, antivirus vendors.
--
Hunter Fuller
OIT
Sent from my phone.
On Jan 8, 2015 5:11 PM, "Frank Sweetser" wrote:
> We already have an unencrypted ssid for students to get to
We already have an unencrypted ssid for students to get to our onboarding
system (Cloudpath). Our plan for this summer is to poke enough firewall holes
for students to also run through the device activation process. If we were to
try to impose any kind of device security policies, we would do i
I just wanted to ask the question to see what all of you are doing at your
institutions to handle users activating new devices. New iOS devices for
example have to reach out to iCloud to validate themselves and make sure
they're not stolen. Android now with version 5 is very similar, having to
reac
I second Brian's comments here. I have yet to speak with a consultant or VAR
that thinks that I should have in-house expertise to perform this kind of work.
They usually want me to pay them for the privilege.
--
Cheers,
Jeff
-Original Message-
From: The EDUCAUSE Wireless Issues Constit
You can make a lot of mistakes in deployment and still come out ahead
vs paying for engineering. That's to say, the cost of engineering will
buy a lot of additional AP's to fill in areas where you guessed a little
wrong.
When we dealt with 2.4Ghz and the "goal" was general coverage, then
engine
Agree about the sweeping statement... We aren't even consistent about
whether we do the design in-house or contract it out. (It's different
building to building based on budget and resources at the time.) There
have been optimal and not-so-optimal results from both approaches. :)
--
Hunter Fuller
I mostly agree with Brian- we do it all in house, have since day 1, and have
seen the work of "integrators" that I can't imagine paying $ for. Not trashing
all VARs, but there are some out there that are really thin on wireless
experience.
Lee H. Badman
Network Architect/Wireless TME
ITS, Syrac
I hate sweeping statements like "most Universities do not do the Wi-Fi
engineering work in house and usually put the design in the RFP", and I would
have to disagree with it. It has been my experience in working with this group
as well as numerous WiFi vendors that it's a pretty even mix of usi
Colleagues,
We are starting an initiative to upgrade our Wi-Fi infrastructure. Our
current infrastructure was built in-house incrementally over the past
several years. It is 802.n based and not as dense as we would like so
we are looking at moving to 802.11ac with a significant increase in
A
12 matches
Mail list logo
