IRELESS-LAN@LISTSERV.EDUCAUSE.EDU>
> Date: Friday, April 28, 2017 at 2:51 PM
> To: "wireless-lan@listserv.educause.edu" <WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU>
> Subject: Re: [WIRELESS-LAN] Eduroam adoption (and migration process)
>
>
> On Apr 28, 2017, at 3:49 P
.EDUCAUSE.EDU>
on behalf of Philippe Hanset <phan...@anyroam.net>
Reply-To: "wireless-lan@listserv.educause.edu"
<WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU>
Date: Friday, April 28, 2017 at 2:51 PM
To: "wireless-lan@listserv.educause.edu" <WIRELESS-LAN@LISTSER
ent Group Listserv
> <WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU> on behalf of Hunter Fuller
> <hf0...@uah.edu>
> Sent: Friday, April 28, 2017 12:39 PM
> To: WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU
> Subject: Re: [WIRELESS-LAN] Eduroam adoption (and migration process)
>
> C
riday, April 28, 2017 at 11:14 AM
> To: "wireless-lan@listserv.educause.edu
> <mailto:wireless-lan@listserv.educause.edu>"
> <WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU
> <mailto:WIRELESS-LAN@listserv.educause.edu>>
> Subject: Re: [WIRELESS-LAN] Eduroam adoption (
e EDUCAUSE Wireless Issues Constituent Group Listserv
<WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU> on behalf of Hunter Fuller <hf0...@uah.edu>
Sent: Friday, April 28, 2017 12:39 PM
To: WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU
Subject: Re: [WIRELESS-LAN] Eduroam adoption (and migration process)
Cur
roup Listserv <
> WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU> on behalf of Hunter Fuller <
> hf0...@uah.edu>
> Sent: Friday, April 28, 2017 8:51 AM
> To: WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU
> Subject: Re: [WIRELESS-LAN] Eduroam adoption (and migration process)
>
> I'm still not sure I fo
Jeff,
>
> Why do I say this?
> · Organization - A university can’t assume and/or guarantee that
> “eduroam” is administered at another campus in the same way that it is at
> home. There is no guarantee of privacy, be it the data collected during
> authentication/authorization, or
edu>
+1 919 445 0113 Office
+1 919 274 7926 Mobile
From: The EDUCAUSE Wireless Issues Constituent Group Listserv
[mailto:WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU] On Behalf Of Jeffrey D. Sessler
Sent: Friday, April 28, 2017 1:18 PM
To: WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU
Subject: Re: [WIRELESS-LAN] E
No matter what direction I come at it, “eduroam” is fundamentally a guest
network with very little intrinsic value, but with many downsides. As such, I
would be reluctant to make it our default SSID, and I caution those that use it
as such to explore its shortcomings.
Why do I say this?
·
Mobile
From: The EDUCAUSE Wireless Issues Constituent Group Listserv
[mailto:WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU] On Behalf Of Hunter Fuller
Sent: Friday, April 28, 2017 10:52 AM
To: WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU
Subject: Re: [WIRELESS-LAN] Eduroam adoption (and migration process)
I'm
EDU> on behalf of Hunter Fuller <hf0...@uah.edu>
Sent: Friday, April 28, 2017 10:51:51 AM
To: WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU
Subject: Re: [WIRELESS-LAN] Eduroam adoption (and migration process)
I'm still not sure I follow.
It sounds like, in your current config, you have your constitu
LAN@LISTSERV.EDUCAUSE.EDU> on behalf of Hunter Fuller <hf0...@uah.edu>
Sent: Friday, April 28, 2017 8:51 AM
To: WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU
Subject: Re: [WIRELESS-LAN] Eduroam adoption (and migration process)
I'm still not sure I follow.
It sounds like, in your current config, y
___
> From: The EDUCAUSE Wireless Issues Constituent Group Listserv <
> WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU> on behalf of Les Ridgley <
> les.ridg...@newcastle.edu.au>
> Sent: Thursday, April 27, 2017 10:10 PM
> To: WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU
ppalli, Tim (Aruba
Security) <t...@hpe.com>
Sent: Friday, April 28, 2017 3:54 AM
To: WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU
Subject: Re: [WIRELESS-LAN] Eduroam adoption (and migration process)
Can you elaborate on this comment?
“whereas with eduroam we were kind of locked-in to the PEAP mode
On Fri, Apr 28, 2017 at 09:54:55AM +, Cappalli, Tim (Aruba Security) wrote:
> Can you elaborate on this comment?
>
> “whereas with eduroam we were kind of locked-in to the PEAP model.”
>
> Eduroam is EAP agnostic.
Quite - I was thinking the same thing.
There's no reason why you can't use
lman
Sent: Friday, 28 April 2017 1:26 PM
To: WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU
Subject: Re: [WIRELESS-LAN] Eduroam adoption (and migration process)
A related question came up today when discussing whether or not to get rid
of our branded SSID or not once eduroam is up and
;WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU> on behalf of Les Ridgley
<les.ridg...@newcastle.edu.au>
Sent: Thursday, April 27, 2017 10:10 PM
To: WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU
Subject: Re: [WIRELESS-LAN] Eduroam adoption (and migration process)
We retained both the eduroam SSID and the universi
: Re: [WIRELESS-LAN] Eduroam adoption (and migration process)
A related question came up today when discussing whether or not to get rid of
our branded SSID or not once eduroam is up and running on our network.
Specifically:
For those who decided to keep both the branded and eduroam SSID's
@LISTSERV.EDUCAUSE.EDU
Subject: Re: [WIRELESS-LAN] Eduroam adoption (and migration process)
Ahh, I see. They are separate networks. We are using a NAC to place users in
their proper vlan, so there’s no differentiation between our current university
ssid and eduroam.
By the way, I keep writing
2017 at 11:19 AM
> *To: *"WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU" <WIRELESS-LAN@LISTSERV.
> EDUCAUSE.EDU>
>
> *Subject: *Re: [WIRELESS-LAN] Eduroam adoption (and migration process)
>
>
>
> We rolled out eduroam a couple of years ago, and like most others appea
e EDUCAUSE Wireless Issues Constituent Group Listserv
<WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU> on behalf of Walter Reynolds
<wa...@umich.edu>
Sent: Tuesday, April 25, 2017 3:33 PM
To: WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU
Subject: Re: [WIRELESS-LAN] Eduroam adoption (and migration proces
--
>> From: The EDUCAUSE Wireless Issues Constituent Group Listserv [mailto:
>> WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU] On Behalf Of Fligor, Debbie
>> Sent: Monday, April 24, 2017 4:38 PM
>> To: WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU
>> Subject: Re: [WIRELESS-LAN] Eduroam adoption (and migratio
> To: WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU
> Subject: Re: [WIRELESS-LAN] Eduroam adoption (and migration process)
>
> I can’t speak for the campuses you named, but we have not switched to
> eduroam as our main SSID, and we have no current plans to. I’m sure someone
> is happy about
S-LAN@LISTSERV.EDUCAUSE.EDU] On Behalf Of Fligor, Debbie
Sent: Monday, April 24, 2017 4:38 PM
To: WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU
Subject: Re: [WIRELESS-LAN] Eduroam adoption (and migration process)
I can’t speak for the campuses you named, but we have not switched to eduroam
as our main SSID, a
!
-Brian
From: The EDUCAUSE Wireless Issues Constituent Group Listserv
[mailto:WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU] On Behalf Of John Heartlein
Sent: Tuesday, April 25, 2017 1:52 PM
To: WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU
Subject: Re: [WIRELESS-LAN] Eduroam adoption (and migration process)
Hello Brian
Group Listserv [mailto:
> WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU] *On Behalf Of *John Heartlein
> *Sent:* Friday, April 21, 2017 5:08 PM
> *To:* WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU
> *Subject:* Re: [WIRELESS-LAN] Eduroam adoption (and migration process)
>
>
>
> Saint Louis Universit
I can’t speak for the campuses you named, but we have not switched to eduroam
as our main SSID, and we have no current plans to. I’m sure someone is happy
about the branding somewhere, but it’s also for technical reasons. Eduroam,
like our guest wireless, is routed outside our campus border
On Mon, 24 Apr 2017 19:18:51 +
Marcelo Maraboli wrote:
> I still wonder why Universities like MIT,Harvard,Stanford and Berkeley
> only use Eduroam as a secondary SSID and still keep their main SSID.
> The only thing I can think of is branding.
Branding and inertia of
I would like to thank all who responded.
Everybody who responded is making EduRoam their main SSID
deprecating their old SSID (MAC or .1x).
I still wonder why Universities like MIT,Harvard,Stanford and Berkeley
only use Eduroam as a secondary SSID and still keep their main SSID.
The only thing
Hello Jason
thank you for you thorough response.
You should maybe check Radiator instead of Freeradius, since
it makes life much easier with 802.1x and all the complexities
you mentioned.
We will deploy Eduroam/802.1x with Radiator since we too have
some complexities and Freeradius is a painin
On Thu, Apr 20, 2017 at 4:30 PM Marcelo Maraboli
wrote:
> - Did you leave an SSID for legacy devices ? (What AUTH mechanism for this
> SSID?)
>
Our "UAH Get Connected" ESSID is wide open, and will assist users with
connecting to eduroam. It also doubles as our
All,
I recently did a presentation to the business school at University of
Tennessee. UT uses eduroam as the only secure SSID. They all knew about
eduroam. And when I asked the audience of 60 or so students how many knew that
it works seamlessly around the world, only 3 students raised their
We are in the process of migrating to eduroam as our primary SSID also. We
introduced eduroam to our campus in August 2016. Our original college-branded
secure wireless network was already 802.1x, so we don’t need to worry about
supporting legacy devices by holding back a legacy SSID. We did
@LISTSERV.EDUCAUSE.EDU
Subject: Re: [WIRELESS-LAN] Eduroam adoption (and migration process)
Saint Louis University deployed eduroam in late 2015. Besides eduroam we have
an 802.1x SSID SLU-users for our students, faculty, and staff. We also have
SLUguest for guests and legacy devices. Here's a link to more
anded SSID’s are either specialized or they go away.
>
>
>
> -Brian
>
>
>
> *From:* The EDUCAUSE Wireless Issues Constituent Group Listserv [mailto:
> WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU] *On Behalf Of *Bucklaew, Jerry
> *Sent:* Friday, April 21, 2017 8:35 AM
> *To:* WIRE
To: WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU
Subject: Re: [WIRELESS-LAN] Eduroam adoption (and migration process)
We are currently moving to eduraom as the primary ssid. We are doing a
communication campaign and will retire the old 802.1x ssid at some point. We
do have a non802.1x ssid for “other
We are currently moving to eduraom as the primary ssid. We are doing a
communication campaign and will retire the old 802.1x ssid at some point. We
do have a non802.1x ssid for “other” devices. It is a “start here” ssid that
will also configure you for 802.1x.
From: The EDUCAUSE Wireless
Hi
Eduroam is our primary SSID: when we moved to it, we kept an old 802.1x which
we discontinued 1 month after the beginning of the school year. We still kept
an open SSID to allow legacy devices to access the network with a VPN
authentication. We massively advertised and updated all the
38 matches
Mail list logo