This thread seems to have gone off track and started to talk about a platform for RIPE Atlas v4 hardware. While I encourage that discussion I'm wondering if anyone has any comments on WLAN authentication testing and tests being run over the /current/ Atlas platform?
Anything left out in my 5 points below? -Brook On 27 November 2014 at 17:52, Brook Schofield <[email protected]> wrote: > MAT-WG, > > thankyou for giving me the opportunity to present on "The Value of WLAN > Measurements for the R&E Community" at the Measurement and Tools Working > Group at RIPE69. > > You can find my presentation and stenography logs at: > https://ripe69.ripe.net/presentations/91-eduroam-and-Atlas-RIPE69.pdf > https://ripe69.ripe.net/archives/steno/40 > > > To progress this work within the RIPE NCC Atlas development team I'd like > your input into the following five (5) points: > > > #1: For "opt-in" WLAN measurements to be enabled on RIPE Atlas > > As a point of clarification (and reiterated by Daniel Karrenberg) the > intention is that ALL v3 probes will be capable of WLAN measurements - but > measurements will ONLY be turned on by a probe host. > > > #2: WLAN measurements will support associating to an "open" or 802.1X > protected network for the purposes of performing a measurement > > As an active monitoring network the Atlas probes WILL NOT scan and report > on all/available SSIDs. It will ONLY associate with EXPLICITLY defined > SSIDs listed in the measurement. > > For eduroam quality purposes the success/failure of an 802.1X associations > is initially the most interesting part of the measurement in determining > whether sites are correctly deploying this service. There will be results > related to the authentication process. > > > #3: Any measurements performed over the wireless interface are aligned > with a request to associate/authenticate to a particular network. > > The wireless interface will be connected only for particular tests bundled > with the association to an SSID. All other tests will be performed via the > wired interface as is currently the case. > > > #4: The schedule for implementation will be determined by the RIPE NCC R&D > team > > ...but hopefully your support for this work will allow them to prioritise > this work while not jeopardising the other commitments the team has made > to the community. > > > #5: This proposal is inline with your understanding of "WiFi measurements" > on the Atlas roadmap > > I'd be particularly interested in your feedback on whether you thought > that the WiFi Measurements listed in the > http://roadmap.ripe.net/ripe-atlas/ would accomplish the above or > something completely different. > > > My feeling from the room was that the above was largely accepted. I'd > appreciate those that voiced their support to also do this on the mailing > list again. If there's any confusion I'm willing to clarify further. > > Thanks, > > -Brook > -- > =================================================== > Brook Schofield, Project Development Officer > GÉANT Association, Singel 468 D, 1017 AW Amsterdam, The Netherlands > Tel +31 20 530 4488 Fax +31 20 530 4499 Mob +31 65 155 3991 > www.géant.org <http://www.xn--gant-bpa.org> > -- =================================================== Brook Schofield, Project Development Officer GÉANT Association, Singel 468 D, 1017 AW Amsterdam, The Netherlands Tel +31 20 530 4488 Fax +31 20 530 4499 Mob +31 65 155 3991 www.géant.org <http://www.xn--gant-bpa.org>
