Jerry, Jerry,
Thanks for the feedback. We have been digesting these reports for about a year now and rejects per MAC was on our agenda. We had two issues with that one: -Storing failed authentications is really overwhelming for our Top Level Servers (we might have storage issues .. there is a lot of nasty stuff in those failed attempts :) -Calling-Station-ID (MAC address) is not always reliable…some of you don't send it, and some have different formats for the same MAC address (if you have two Wi-Fi vendors on campus) But, with all the feedback we will look into it again. As a request to all of you, please make sure that you send Calling-Station-ID (it is actually required). Thanks, Philippe Philippe Hanset, CEO > On Jul 6, 2018, at 11:47 AM, Bucklaew, Jerry <[email protected]> wrote: > > Philippe, > > I like the reports, but as people have pointed out the errors are > concerning. It might be good to quantify the errors to unique macs instead > of just failures. You have unique users authenticated and then authenticated > percentage. But is that the percentage of total request vs total failures or > unique macs that have succeeded vs unique mac that have failed? If our guess > is correct, the failure percentage will be high (ours is around 20% for our > users and 30% for guest) for total request vs failures, but should be > relatively low for total unique request vs unique failures. Maybe that would > be a stat worth adding? > > > > From: The EDUCAUSE Wireless Issues Constituent Group Listserv > <[email protected] > <mailto:[email protected]>> On Behalf Of Philippe Hanset > Sent: Friday, July 6, 2018 11:34 AM > To: [email protected] > <mailto:[email protected]> > Subject: Re: [WIRELESS-LAN] Your eduroam semi-annual report > > All, > > When we designed the reports we had two main goals in mind: > 1) Quantitative data (how many, and where), both as SP and IDP > 2) Qualitative data (is my service ok), both as IDP and SP > > Many of you like the reports and also many have asked to have comparisons > with other schools especially for “rejects”. > > We cannot reveal other schools’ data without their consent, > but I have asked Stephanie(our data specialist) to work on graphs showing the > distribution of errors (eg: 7 schools are at 0% success rate, 10 at 10%, > etc…) also integrating into the stats the size of schools. > She will be brainstorming some of this in the coming weeks and post it on > the eduroam.us <http://eduroam.us/> website > > Just looking roughly at data as an IDP and SP you should be around 60+ % > Bear in mind that you cannot control poorly configured users coming to your > campus as an SP. > As an IDP you can definitely check your stats and optimize your user’s > configuration (to a point!). > > In summary as an SP you have very little control, as an IDP you have a lot > more! > > Philippe > > Philippe Hanset, CEO > www.anyroam.net <http://www.anyroam.net/> > www.eduroam.us <http://www.eduroam.us/> > +1 (865) 236-0770 > > GPG key id: 0xF2636F9C > > > > > > > > On Jul 6, 2018, at 11:00 AM, Mike Atkins <[email protected] > <mailto:[email protected]>> wrote: > > Our identity group typically manages the eduroam configuration. I was > recently added to troubleshoot some very specific issues. Things I found > useful are/were access to eduroam radius logs, realm testing tool, reports > going back to January 2018, and a dashboard that has data going back to 2012. > I do not think there is read only access but it might be worth inquiring > with your admin if you do any sort of regular radius troubleshooting. > (remote for your users or locally for guests) I see a timeouts (frequent no > response even though packet captures show our server responded) and on our > six month eduroam success rate is 69.7% I am still in the process of > troubleshooting but the information is very helpful. E-mail me off list and > I’ll send you our reports if you want to compare sites. > > > > > > Mike Atkins > Network Engineer > Office of Information Technology > University of Notre Dame > > From: The EDUCAUSE Wireless Issues Constituent Group Listserv > [mailto:[email protected] > <mailto:[email protected]>] On Behalf Of Patrick McEvilly > Sent: Friday, July 06, 2018 8:08 AM > To: [email protected] > <mailto:[email protected]> > Subject: Re: [WIRELESS-LAN] Your eduroam semi-annual report > > As the admin contact I was getting them but asked if we could add some > internal mailing lists. In your eduroam profile they have added a “report > contact” option which is working well. > > Patrick > > > From: The EDUCAUSE Wireless Issues Constituent Group Listserv > <[email protected] > <mailto:[email protected]>> on behalf of "Watters, John" > <[email protected] <mailto:[email protected]>> > Reply-To: The EDUCAUSE Wireless Issues Constituent Group Listserv > <[email protected] > <mailto:[email protected]>> > Date: Friday, July 6, 2018 at 8:01 AM > To: "[email protected] > <mailto:[email protected]>" > <[email protected] > <mailto:[email protected]>> > Subject: Re: [WIRELESS-LAN] Your eduroam semi-annual report > Resent-From: Patrick McEvilly <[email protected] > <mailto:[email protected]>> > > What person at a school receives them? I want to see ours. > > Thanks. > > Sent from my iPhone > > On Jul 6, 2018, at 6:40 AM, Philippe Hanset > <[email protected] > <mailto:[email protected]>> wrote: > > Yahya, > > These reports are provided to all IdPs > and SPs in the US. ANYROAM, the operator of eduroam on behalf of Internet2 > has built those reports based on the US top level RADIUS logs. > > Philippe > > Philippe Hanset, CEO > ANYROAM LLC > www.anyroam.net > <https://urldefense.proofpoint.com/v2/url?u=http-3A__www.anyroam.net&d=DwMGaQ&c=WO-RGvefibhHBZq3fL85hQ&r=NEt1bAdOCtalVd4Ws0dvlC8LeF95Hl1p6yYgtTh8luM&m=PXBR2nrMAcW7e0QP6NFQUP_IE0Xafm5WM3RjJzkZd3U&s=XSVDB6hUKN7nYCKHPRaOeBwzf5x7sKWBSgkqwF8O2yA&e=> > www.eduroam.us > <https://urldefense.proofpoint.com/v2/url?u=http-3A__www.eduroam.us&d=DwMGaQ&c=WO-RGvefibhHBZq3fL85hQ&r=NEt1bAdOCtalVd4Ws0dvlC8LeF95Hl1p6yYgtTh8luM&m=PXBR2nrMAcW7e0QP6NFQUP_IE0Xafm5WM3RjJzkZd3U&s=nBExgSVb3S72y2W1z9jcHvCQu1bWmus2HEI8f-6ee_M&e=> > > On Jul 6, 2018, at 6:17 AM, Yahya M. Jaber <[email protected] > <mailto:[email protected]>> wrote: > > Is this only for Idp’s who has it as primary network? Eduroam is a secondary > one for us here. > > > Best Regards, > > Yahya Jaber > Sr. Wireless Engineer > IT Network & Communications – Engineering > > Email [email protected] <mailto:[email protected]> > Office +966 (0) 12 8081237 > Mobile +966 (0) 558697555 > > From: The EDUCAUSE Wireless Issues Constituent Group Listserv > [mailto:[email protected] > <mailto:[email protected]>] On Behalf Of Turner, Ryan H > Sent: Friday, July 6, 2018 4:03 AM > To: [email protected] > <mailto:[email protected]> > Subject: [WIRELESS-LAN] Fwd: Your eduroam semi-annual report > > All: > > We have run eduroam as our primary SSID for several years. For those > institutions that do not, but wonder what it might look like for those that > do, I’ve included our semi annual report. > > Ryan Turner > Senior Manager of Networking, ITS > The University of North Carolina at Chapel Hill > +1 919 274 7926 Mobile > +1 919 445 0113 Office > > Begin forwarded message: > > ********** Participation and subscription information for this EDUCAUSE > Constituent Group discussion list can be found at > http://www.educause.edu/discuss > <https://urldefense.proofpoint.com/v2/url?u=http-3A__www.educause.edu_discuss&d=DwMGaQ&c=WO-RGvefibhHBZq3fL85hQ&r=NEt1bAdOCtalVd4Ws0dvlC8LeF95Hl1p6yYgtTh8luM&m=PXBR2nrMAcW7e0QP6NFQUP_IE0Xafm5WM3RjJzkZd3U&s=KgccghEwWcmyoYQF9PJhISDZh12GnlsSwyjUCpC69Rw&e=>. > > > This message and its contents including attachments are intended solely for > the original recipient. If you are not the intended recipient or have > received this message in error, please notify me immediately and delete this > message from your computer system. Any unauthorized use or distribution is > prohibited. Please consider the environment before printing this email. > ********** Participation and subscription information for this EDUCAUSE > Constituent Group discussion list can be found at > http://www.educause.edu/discuss > <https://urldefense.proofpoint.com/v2/url?u=http-3A__www.educause.edu_discuss&d=DwMGaQ&c=WO-RGvefibhHBZq3fL85hQ&r=NEt1bAdOCtalVd4Ws0dvlC8LeF95Hl1p6yYgtTh8luM&m=PXBR2nrMAcW7e0QP6NFQUP_IE0Xafm5WM3RjJzkZd3U&s=KgccghEwWcmyoYQF9PJhISDZh12GnlsSwyjUCpC69Rw&e=>. > > ********** Participation and subscription information for this EDUCAUSE > Constituent Group discussion list can be found at > http://www.educause.edu/discuss > <https://urldefense.proofpoint.com/v2/url?u=http-3A__www.educause.edu_discuss&d=DwMGaQ&c=WO-RGvefibhHBZq3fL85hQ&r=NEt1bAdOCtalVd4Ws0dvlC8LeF95Hl1p6yYgtTh8luM&m=PXBR2nrMAcW7e0QP6NFQUP_IE0Xafm5WM3RjJzkZd3U&s=KgccghEwWcmyoYQF9PJhISDZh12GnlsSwyjUCpC69Rw&e=>. > > ********** Participation and subscription information for this EDUCAUSE > Constituent Group discussion list can be found at > http://www.educause.edu/discuss > <https://urldefense.proofpoint.com/v2/url?u=http-3A__www.educause.edu_discuss&d=DwMGaQ&c=WO-RGvefibhHBZq3fL85hQ&r=NEt1bAdOCtalVd4Ws0dvlC8LeF95Hl1p6yYgtTh8luM&m=PXBR2nrMAcW7e0QP6NFQUP_IE0Xafm5WM3RjJzkZd3U&s=KgccghEwWcmyoYQF9PJhISDZh12GnlsSwyjUCpC69Rw&e=>. > > ********** Participation and subscription information for this EDUCAUSE > Constituent Group discussion list can be found at > http://www.educause.edu/discuss <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 <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 <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 <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.
