#1221 closed request (fixed)

multi-second ping times in Viscount

Reported by: kaduk@… Owned by: panda@…
Priority: tbd Milestone: ietf-101
Component: wireless Keywords:
Cc: My Current Location: Viscount
My MAC Address: 30:52:cb:e7:7c:45 My OS: debian unstable

Description

I'm in Viscount for the DOTS session, and have been seeing poor network performance in interactive usage, quantified by ping responses exceeding 3 seconds.

Change history (4)

comment:1 in reply to:  1 ; Changed 18 months ago by kaduk@…

On Tue, Mar 20, 2018 at 04:33:05PM +0000, IETF Tickets/NOC wrote:
> #1221: multi-second ping times in Viscount
> -------------------------------------+-------------------------------------
>            Reporter:  kaduk@…        |           Owner:  llynch@…
>                Type:  request        |          Status:  new
>            Priority:  tbd            |       Milestone:  ietf-101
>           Component:  incoming       |        Keywords:
> My Current Location:  Viscount       |  My MAC  Address:  30:52:cb:e7:7c:45
>               My OS:  debian         |
>   unstable                           |
> -------------------------------------+-------------------------------------
>  I'm in Viscount for the DOTS session, and have been seeing poor network
>  performance in interactive usage, quantified by ping responses exceeding 3
>  seconds.

Perhaps it cleared up already by when I managed to figure out the
ticket submission process...

Thanks for looking, and sorry if this was noise.

-Ben

comment:2 Changed 18 months ago by panda@…

Hi,

Thank you for reporting.

I'm investigating the issue with spectrum analyzer and other logs. I'll let you know if I could clear the problem.

Thank you.
-- Hirochika Asai

comment:3 Changed 18 months ago by odonoghue@…

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

comment:4 Changed 18 months ago by panda@…

Resolution: fixed
Status: assignedclosed

Hi,

I've checked the log, statistics, and channel allocation. We found that we had a large amount of traffic on the channel you were using, and thus your SNR was low at that moment.

We tried to rearrange our channel design last night and this morning. We hope the quality gets better.
I'll close this ticket but please feel free to reopen it if you experience bad quality again.

Thank you.
Hirochika Asai

Note: See TracTickets for help on using tickets.