Opened 2 years ago

Closed 2 years ago

Last modified 11 months ago

#1015 closed defect (worksforme)

reverting back to non-encrypted access

Reported by: marc.blanchet@… Owned by: panda@…
Priority: tbd Milestone: ietf-096
Component: wireless Keywords:
Cc: My Current Location:
My MAC Address: My OS:

Description (last modified by panda@…)

Thank you, Marc. I'll close this ticket but we'll keep this issue in mind and seek a better solution for future meetings.

-- Hirochika Asai

Change history (7)

comment:1 Changed 2 years ago by llynch@…

Component: incomingwireless
Owner: changed from llynch@… to panda@…
Status: newassigned
Type: requestdefect

comment:2 Changed 2 years ago by llynch@…

Hey Marc -

can you add your MAC address?

  • thanks

Lucy

comment:3 Changed 2 years ago by marc.blanchet@…

en0: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu 1500
         ether b8:e8:56:30:ce:d4
         inet6 fe80::bae8:56ff:fe30:ced4%en0 prefixlen 64 scopeid 0x4
         inet 31.133.180.92 netmask 0xfffff800 broadcast 31.133.183.255
         inet6 2001:67c:370:176:bae8:56ff:fe30:ced4 prefixlen 64 
autoconf
         inet6 2001:67c:370:176:15ec:445d:6287:83bb prefixlen 64 
autoconf temporary
         nd6 options=1<PERFORMNUD>
         media: autoselect
         status: active

Marc.

On 20 Jul 2016, at 16:35, IETF Tickets/NOC wrote:

> #1015: reverting back to non-encrypted access
> ----------------------------------+--------------------------------
>       Reporter:  marc.blanchet@…  |                Owner:  panda@…
>           Type:  defect           |               Status:  assigned
>       Priority:  tbd              |            Milestone:  ietf-96
>      Component:  wireless         |           Resolution:
>       Keywords:                   |  My Current Location:
> My MAC  Address:                  |                My OS:
> ----------------------------------+--------------------------------
>
> Comment (by llynch@…):
>
>  Hey Marc -
>
>  can you add your MAC address?
>
>  - thanks
>
>  Lucy
>
> --
> Ticket URL: <https://tickets.meeting.ietf.org/ticket/1015#comment:2>
> IETF Tickets/NOC <https://tickets.meeting.ietf.org>
> IETF Meeting Tickets - NOC pages

comment:4 in reply to:  description Changed 2 years ago by panda@…

Hi Marc,

Thank you for your report.

We sometimes experience the same problem when we associate with the SSID previously associated with but its configuration (e.g., certificate) has been changed.

There is a workaround, and can you try this if you still keep ietf-legacy.

  1. Delete the ietf SSID from the WiFi? list.
  2. Associate with the ietf SSID. (Certificate verification and ID/password will be prompted.)
  3. Set the ietf SSID to higher preference than the others such as ietf-legacy

Thank you.
Hirochika Asai

comment:5 Changed 2 years ago by marc.blanchet@…

On 20 Jul 2016, at 16:46, IETF Tickets/NOC wrote:

> #1015: reverting back to non-encrypted access
> ----------------------------------+--------------------------------
>       Reporter:  marc.blanchet@…  |                Owner:  panda@…
>           Type:  defect           |               Status:  assigned
>       Priority:  tbd              |            Milestone:  ietf-96
>      Component:  wireless         |           Resolution:
>       Keywords:                   |  My Current Location:
> My MAC  Address:                  |                My OS:
> ----------------------------------+--------------------------------
>
> Comment (by panda@…):
>
>  Hi Marc,
>
>  Thank you for your report.
>
>  We sometimes experience the same problem when we associate with the 
> SSID
>  previously associated with but its configuration (e.g., certificate) 
> has
>  been changed.
>
>  There is a workaround, and can you try this if you still keep 
> ietf-legacy.
>  1. Delete the ietf SSID from the WiFi list.
>  2. Associate with the ietf SSID.  (Certificate verification and
>  ID/password will be prompted.)
>  3. Set the ietf SSID to higher preference than the others such as 
> ietf-
>  legacy

thanks. I did that and it does not change the issue. It looks like for 
some reasons the OS seem to be « impatient » and then revert back. I 
haven’t investigated if it is the WPA negotiation or IP address 
assignment which is « too slow », but I thought it was WPA nego, 
since the L2 is not even up before reverting to the opened ssid.  
Anyway, we all know how much OS are adding various heuristics to 
« speed up » access and that might be the issue.

(case closed for me, but I wanted to inform you in case others have same 
issues and it might show a slowness in the access network 
infrastructure)

Marc.

>
>  Thank you.
>  Hirochika Asai
>
> --
> Ticket URL: <https://tickets.meeting.ietf.org/ticket/1015#comment:4>
> IETF Tickets/NOC <https://tickets.meeting.ietf.org>
> IETF Meeting Tickets - NOC pages

comment:6 in reply to:  5 Changed 2 years ago by panda@…

Description: modified (diff)
Resolution: worksforme
Status: assignedclosed

Replying to marc.blanchet@…:

On 20 Jul 2016, at 16:46, IETF Tickets/NOC wrote:

> #1015: reverting back to non-encrypted access
> ----------------------------------+--------------------------------
>       Reporter:  marc.blanchet@…  |                Owner:  panda@…
>           Type:  defect           |               Status:  assigned
>       Priority:  tbd              |            Milestone:  ietf-96
>      Component:  wireless         |           Resolution:
>       Keywords:                   |  My Current Location:
> My MAC  Address:                  |                My OS:
> ----------------------------------+--------------------------------
>
> Comment (by panda@…):
>
>  Hi Marc,
>
>  Thank you for your report.
>
>  We sometimes experience the same problem when we associate with the 
> SSID
>  previously associated with but its configuration (e.g., certificate) 
> has
>  been changed.
>
>  There is a workaround, and can you try this if you still keep 
> ietf-legacy.
>  1. Delete the ietf SSID from the WiFi list.
>  2. Associate with the ietf SSID.  (Certificate verification and
>  ID/password will be prompted.)
>  3. Set the ietf SSID to higher preference than the others such as 
> ietf-
>  legacy

thanks. I did that and it does not change the issue. It looks like for 
some reasons the OS seem to be « impatient » and then revert back. I 
haven’t investigated if it is the WPA negotiation or IP address 
assignment which is « too slow », but I thought it was WPA nego, 
since the L2 is not even up before reverting to the opened ssid.  
Anyway, we all know how much OS are adding various heuristics to 
« speed up » access and that might be the issue.

(case closed for me, but I wanted to inform you in case others have same 
issues and it might show a slowness in the access network 
infrastructure)

Marc.

>
>  Thank you.
>  Hirochika Asai
>
> --
> Ticket URL: <https://tickets.meeting.ietf.org/ticket/1015#comment:4>
> IETF Tickets/NOC <https://tickets.meeting.ietf.org>
> IETF Meeting Tickets - NOC pages

comment:7 Changed 11 months ago by Rick Alfvin

Milestone: ietf-96ietf-096

Milestone renamed

Note: See TracTickets for help on using tickets.