[Top] [All Lists]

Re: meeting ietf-legacy ssid

2017-07-12 08:09:37
On 12 Jul 2017, at 09:37, Randy Bush <randy(_at_)psg(_dot_)com> wrote:

On Wed, 12 Jul 2017 07:38:20 +0200, a linux hacker wrote privately:

Ive used it because my linux laptop wouldnt bind to anything else. Not
sure why.

this is a case that worries me deeply.  folk with issues should visit
the help desk in the terminal-less room or visit the noc.

This recent Apple support article is relevant, at least for iOS users :)

On Wed, 12 Jul 2017 07:54:44 +0200, Eliot Lear wrote:

Why not just turn it off and see what happens?

because the noc thinks of the attendees as those strange critters called
"customers."  this creates implications for service continuity.

On Wed, 12 Jul 2017 08:46:11 +0200, Christian Huitema wrote:

You may want to tabulate the OS version of the devices on the
un-encrypted network. Can your DHCP server do that? That should give you
some indication.

i proposed measuring a number of aspects of use of ietf-legacy, mostly
port use; wanting to get a feel if the use was protected above layer
three.  i specifically avoided proposing looking inside the packsts as i
do not have time to deal rigorously with the PII issues.  when i asked
if i could measure port use, i was asked to write up a formal project
description.  as this is not my paying $dayjob, i hit delete.

for me, the botttom line here is

  please try networks other than ietf-legacy.  if you have problems
  which drive you to legacy, please come to the noc and debug.

  this is something to be revisited when we know more.

thanks for the clues.

The above Apple article suggests that once you do switch, your device will 
prefer the most recently used SSID.

Personally I use eduroam, and it’s preferred for me by iOS. The snag is that if 
some other SSID is auto-joined, it’s not clearly indicated on the device; you 
just see the WiFi indication in place of 3/4G.



<Prev in Thread] Current Thread [Next in Thread>