RE: [WIRELESS-LAN] Defeating Android 8.X Captive Portal detection

[Gavin Pyle]

Richard,

Has Cloudpath built in support for this yet?  We just tried with a Pixel phone 
on Oreo and it still wants us to install the app from Google Play.

Gavin Pyle
Network Engineer
Information Technology
Green River College

-Original Message-
From: The EDUCAUSE Wireless Issues Constituent Group Listserv 
[mailto:WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU] On Behalf Of Richard Nedwich
Sent: Tuesday, October 10, 2017 3:07 PM
To: WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU
Subject: Re: [WIRELESS-LAN] Defeating Android 8.X Captive Portal detection

Hi Thomas, et al,

Just wanted to provide a quick update regarding Android support in the 
industry, and in Cloudpath ES, in hopes this information is helpful.

Best,
Rich

Android:  Starting with Android Oreo, Android is recommending that 
manufacturers include a standard module (provided by Google) to allow app-less 
configuration.  While manufacturers are not required to include it, the 
expectation is that they will.  This module will allow Cloudpath to configure 
Android devices in a manner similar to IOS and without an app.  In addition, we 
are currently testing Passpoint R2 functionality with Android developers, which 
allows auto-provisioning directly from the wireless manager (rather than the 
browser+xmlDocument).
 

**
Participation and subscription information for this EDUCAUSE Constituent Group 
discussion list can be found at http://www.educause.edu/discuss.

**
Participation and subscription information for this EDUCAUSE Constituent Group 
discussion list can be found at http://www.educause.edu/discuss.

RE: [WIRELESS-LAN] Defeating Android 8.X Captive Portal detection

[Thomas Carter]

Yes, we have had some who have had trouble in the past say they also sometimes 
had issues at Starbucks, et al. So the assumption that EDU is the only place 
they have issues may not be correct. I do think there should be better 
communication between wireless vendors, wireless device makers (esp Microsoft, 
Apple, and Google), and customers about these kind of changes. Why do we have 
to figure this out at all? It shouldn't be this hard.

Thomas Carter
Network & Operations Manager / IT
Austin College
900 North Grand Avenue 
Sherman, TX 75090
Phone: 903-813-2564
www.austincollege.edu


-Original Message-
From: The EDUCAUSE Wireless Issues Constituent Group Listserv 
[mailto:WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU] On Behalf Of Curtis K. Larsen
Sent: Wednesday, September 6, 2017 1:51 PM
To: WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU
Subject: Re: [WIRELESS-LAN] Defeating Android 8.X Captive Portal detection

My comment had more to do with standardized captive browser behavior across 
operating systems than ease of use.  Unless you are inferring that all of EDU 
go without a captive portal.  Most of the public places I visit have a captive 
portal so I'd say the same questions apply there too.

-Curtis


From: The EDUCAUSE Wireless Issues Constituent Group Listserv 
<WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU> on behalf of Jeffrey D. Sessler 
<j...@scrippscollege.edu>
Sent: Wednesday, September 6, 2017 11:53 AM
To: WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU
Subject: Re: [WIRELESS-LAN] Defeating Android 8.X Captive Portal detection

On 9/6/17, 8:46 AM, "The EDUCAUSE Wireless Issues Constituent Group Listserv on 
behalf of Curtis K. Larsen" <WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU on behalf of 
curtis.k.lar...@utah.edu> wrote:



It would be really nice if Google would join the club and allow their 
captive browser to switch to a full browser after the internet is reachable, 
but until then I think it's the best we can do.





I'd argue, that again, why are we in EDU making it so hard for users with these 
devices to get access to WIFi? It those devices work in every other setting, be 
it at Starbucks, Panara, Hospitals, HomeDepot, and so on... Then EDU is doing 
something wrong.



The vendors will continue to support/do what's most compatible with "the rest 
of the world" so it's up to EDU to come to terms with why we are so different, 
and so device hostile.



Jeff

** Participation and subscription information for this EDUCAUSE 
Constituent Group discussion list can be found at 
http://www.educause.edu/discuss.

**
Participation and subscription information for this EDUCAUSE Constituent Group 
discussion list can be found at http://www.educause.edu/discuss.

**
Participation and subscription information for this EDUCAUSE Constituent Group 
discussion list can be found at http://www.educause.edu/discuss.

Re: [WIRELESS-LAN] Defeating Android 8.X Captive Portal detection

[Curtis K. Larsen]

My comment had more to do with standardized captive browser behavior across 
operating systems than ease of use.  Unless you are inferring that all of EDU 
go without a captive portal.  Most of the public places I visit have a captive 
portal so I'd say the same questions apply there too.

-Curtis


From: The EDUCAUSE Wireless Issues Constituent Group Listserv 
<WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU> on behalf of Jeffrey D. Sessler 
<j...@scrippscollege.edu>
Sent: Wednesday, September 6, 2017 11:53 AM
To: WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU
Subject: Re: [WIRELESS-LAN] Defeating Android 8.X Captive Portal detection

On 9/6/17, 8:46 AM, "The EDUCAUSE Wireless Issues Constituent Group Listserv on 
behalf of Curtis K. Larsen" <WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU on behalf of 
curtis.k.lar...@utah.edu> wrote:



It would be really nice if Google would join the club and allow their 
captive browser to switch to a full browser after the internet is reachable, 
but until then I think it's the best we can do.





I’d argue, that again, why are we in EDU making it so hard for users with these 
devices to get access to WIFi? It those devices work in every other setting, be 
it at Starbucks, Panara, Hospitals, HomeDepot, and so on… Then EDU is doing 
something wrong.



The vendors will continue to support/do what’s most compatible with “the rest 
of the world” so it’s up to EDU to come to terms with why we are so different, 
and so device hostile.



Jeff

** Participation and subscription information for this EDUCAUSE 
Constituent Group discussion list can be found at 
http://www.educause.edu/discuss.

**
Participation and subscription information for this EDUCAUSE Constituent Group 
discussion list can be found at http://www.educause.edu/discuss.

Re: [WIRELESS-LAN] Defeating Android 8.X Captive Portal detection

[Jeffrey D. Sessler]

On 9/6/17, 8:46 AM, "The EDUCAUSE Wireless Issues Constituent Group Listserv on 
behalf of Curtis K. Larsen"  wrote:



It would be really nice if Google would join the club and allow their 
captive browser to switch to a full browser after the internet is reachable, 
but until then I think it's the best we can do.





I’d argue, that again, why are we in EDU making it so hard for users with these 
devices to get access to WIFi? It those devices work in every other setting, be 
it at Starbucks, Panara, Hospitals, HomeDepot, and so on… Then EDU is doing 
something wrong.



The vendors will continue to support/do what’s most compatible with “the rest 
of the world” so it’s up to EDU to come to terms with why we are so different, 
and so device hostile.



Jeff

**
Participation and subscription information for this EDUCAUSE Constituent Group 
discussion list can be found at http://www.educause.edu/discuss.