Opened 12 months ago

Closed 12 months ago

Last modified 8 months ago

#1138 closed defect (pending)

Network is flaky in Tyrelka

Reported by: mellon@… Owned by: panda@…
Priority: tbd Milestone: ietf-099
Component: wireless Keywords:
Cc: My Current Location:
My MAC Address: My OS:

Description

I keep associating and disassociating with the AP.   Happens about every 30
seconds.   While connected, seems to be working okay.   I'm using
ietf-nat64.

Change history (7)

comment:1 Changed 12 months ago by llynch@…

Component: incomingwireless
Owner: changed from < default > to panda@…
Status: newassigned
Type: requestdefect

Ted

Can you supply your max address and OS please ?

Lucy

comment:2 in reply to:  2 ; Changed 12 months ago by mellon@…

I'm currently happily associated with ietf-hotel, by the way.

On Wed, Jul 19, 2017 at 2:45 PM, Ted Lemon <mellon@fugue.com> wrote:

> I believe this is my MAC address: 6c:29:95:3c:8c:f5
> It's running the latest ChromeOS.
>
> On Wed, Jul 19, 2017 at 2:37 PM, IETF Tickets/NOC <
> tickets@meeting.ietf.org> wrote:
>
>> #1138: Network is flaky in Tyrelka
>> ---------------------------+--------------------------------
>>       Reporter:  mellon@…  |                Owner:  panda@…
>>           Type:  defect    |               Status:  assigned
>>       Priority:  tbd       |            Milestone:  ietf-99
>>      Component:  wireless  |           Resolution:
>>       Keywords:            |  My Current Location:
>> My MAC  Address:           |                My OS:
>> ---------------------------+--------------------------------
>> Changes (by llynch@…):
>>
>>  * owner:  < default > => panda@…
>>  * status:  new => assigned
>>  * component:  incoming => wireless
>>  * type:  request => defect
>>
>>
>> Comment:
>>
>>  Ted
>>
>>  Can you supply your max address and OS please ?
>>
>>  Lucy
>>
>> --
>> Ticket URL: <https://tickets.meeting.ietf.org/ticket/1138#comment:1>
>> IETF Tickets/NOC <https://tickets.meeting.ietf.org>
>> IETF Meeting Tickets - NOC pages
>>
>
>

comment:3 in reply to:  3 ; Changed 12 months ago by mellon@…

I believe this is my MAC address: 6c:29:95:3c:8c:f5
It's running the latest ChromeOS.

On Wed, Jul 19, 2017 at 2:37 PM, IETF Tickets/NOC <tickets@meeting.ietf.org>
wrote:

> #1138: Network is flaky in Tyrelka
> ---------------------------+--------------------------------
>       Reporter:  mellon@…  |                Owner:  panda@…
>           Type:  defect    |               Status:  assigned
>       Priority:  tbd       |            Milestone:  ietf-99
>      Component:  wireless  |           Resolution:
>       Keywords:            |  My Current Location:
> My MAC  Address:           |                My OS:
> ---------------------------+--------------------------------
> Changes (by llynch@…):
>
>  * owner:  < default > => panda@…
>  * status:  new => assigned
>  * component:  incoming => wireless
>  * type:  request => defect
>
>
> Comment:
>
>  Ted
>
>  Can you supply your max address and OS please ?
>
>  Lucy
>
> --
> Ticket URL: <https://tickets.meeting.ietf.org/ticket/1138#comment:1>
> IETF Tickets/NOC <https://tickets.meeting.ietf.org>
> IETF Meeting Tickets - NOC pages
>

comment:4 Changed 12 months ago by panda@…

Status: assignedaccepted

Hi Ted,

Thank you for providing your MAC address. I have examined the association log.

Your device has successfully associated with ietf-nat64 more than once at various locations according to the association log. Therefore, I think this issue is location-specific. Can I ask you to confirm that you have no similar problems in other meeting rooms?

In case it is location-specific, we have deployed an AP in Tyrelka and I could connect to the AP in Tyrelka in front of the room, and use it 10 minutes ago. I didn't enter the room because there's a meeting inside, but I confirmed the AP in the room was functional and radio quality was good.

We see some other devices could use that AP at the time of your issue, but I suspect it was temporarily unavailable for you due to interferences or some reasons.

So can you try it again? If you still have problems, can you try other ietf SSIDs except for ietf-hotel so that we can identify the issue is nat64 specific or not. Since ietf-hotel uses different APs, we would like you to try ietf or ietf-legacy99.

Thank you.
Hirochika Asai

comment:5 in reply to:  5 ; Changed 12 months ago by mellon@…

It is correct that I do not have this problem in other meeting rooms.
Unfortunately I'm not in Tyrelka anymore.   The symptoms were persistent
over a period of about 45 minutes.   ietf-hotel works fine in that room.
I verified that while ietf-hotel was working fine, ietf-nat64 was not.
I'm connected to ietf-nat64 right now in Barcelona and it is stable.

On Wed, Jul 19, 2017 at 3:25 PM, IETF Tickets/NOC <tickets@meeting.ietf.org>
wrote:

> #1138: Network is flaky in Tyrelka
> ---------------------------+--------------------------------
>       Reporter:  mellon@…  |                Owner:  panda@…
>           Type:  defect    |               Status:  accepted
>       Priority:  tbd       |            Milestone:  ietf-99
>      Component:  wireless  |           Resolution:
>       Keywords:            |  My Current Location:
> My MAC  Address:           |                My OS:
> ---------------------------+--------------------------------
> Changes (by panda@…):
>
>  * status:  assigned => accepted
>
>
> Comment:
>
>  Hi Ted,
>
>  Thank you for providing your MAC address. I have examined the association
>  log.
>
>  Your device has successfully associated with ietf-nat64 more than once at
>  various locations according to the association log. Therefore, I think
>  this issue is location-specific. Can I ask you to confirm that you have no
>  similar problems in other meeting rooms?
>
>  In case it is location-specific, we have deployed an AP in Tyrelka and I
>  could connect to the AP in Tyrelka in front of the room, and use it 10
>  minutes ago. I didn't enter the room because there's a meeting inside, but
>  I confirmed the AP in the room was functional and radio quality was good.
>
>  We see some other devices could use that AP at the time of your issue, but
>  I suspect it was temporarily unavailable for you due to interferences or
>  some reasons.
>
>  So can you try it again? If you still have problems, can you try other
>  ietf SSIDs except for ietf-hotel so that we can identify the issue is
>  nat64 specific or not. Since ietf-hotel uses different APs, we would like
>  you to try ietf or ietf-legacy99.
>
>  Thank you.
>  Hirochika Asai
>
> --
> Ticket URL: <https://tickets.meeting.ietf.org/ticket/1138#comment:4>
> IETF Tickets/NOC <https://tickets.meeting.ietf.org>
> IETF Meeting Tickets - NOC pages
>

comment:6 Changed 12 months ago by llynch@…

Resolution: pending
Status: acceptedclosed

I'm closing this ticket - if the issue re-surfaces we can re-open

Thanks for the input!

  • Lucy

comment:7 Changed 8 months ago by Rick Alfvin

Milestone: ietf-99ietf-099

Milestone renamed

Note: See TracTickets for help on using tickets.