Opened 10 months ago

Closed 10 months ago

Last modified 2 months ago

#1085 closed defect (fixed)

Wi-Fi flakey in Zurich D

Reported by: ray@… Owned by: panda@…
Priority: major Milestone: ietf-098
Component: wireless Keywords:
Cc: My Current Location:
My MAC Address: My OS:

Description

Hi Jim and co -

FYI, the Wi-Fi seems to be suffering somewhat in Zurich D.

% ping 31.133.128.1
PING 31.133.128.1 (31.133.128.1): 56 data bytes
64 bytes from 31.133.128.1: icmp_seq=0 ttl=64 time=70.279 ms
64 bytes from 31.133.128.1: icmp_seq=1 ttl=64 time=55.285 ms
64 bytes from 31.133.128.1: icmp_seq=2 ttl=64 time=140.829 ms
64 bytes from 31.133.128.1: icmp_seq=3 ttl=64 time=252.530 ms
64 bytes from 31.133.128.1: icmp_seq=4 ttl=64 time=649.491 ms
64 bytes from 31.133.128.1: icmp_seq=5 ttl=64 time=181.937 ms
64 bytes from 31.133.128.1: icmp_seq=6 ttl=64 time=222.974 ms
Request timeout for icmp_seq 7
64 bytes from 31.133.128.1: icmp_seq=7 ttl=64 time=1897.860 ms
64 bytes from 31.133.128.1: icmp_seq=8 ttl=64 time=1951.382 ms
Request timeout for icmp_seq 10
64 bytes from 31.133.128.1: icmp_seq=9 ttl=64 time=2506.882 ms
64 bytes from 31.133.128.1: icmp_seq=10 ttl=64 time=1597.103 ms
64 bytes from 31.133.128.1: icmp_seq=11 ttl=64 time=2576.747 ms
Request timeout for icmp_seq 14
Request timeout for icmp_seq 15
Request timeout for icmp_seq 16
64 bytes from 31.133.128.1: icmp_seq=12 ttl=64 time=5114.501 ms
64 bytes from 31.133.128.1: icmp_seq=13 ttl=64 time=4204.371 ms
64 bytes from 31.133.128.1: icmp_seq=14 ttl=64 time=3350.782 ms
64 bytes from 31.133.128.1: icmp_seq=15 ttl=64 time=2869.893 ms
64 bytes from 31.133.128.1: icmp_seq=16 ttl=64 time=2258.604 ms
64 bytes from 31.133.128.1: icmp_seq=17 ttl=64 time=2808.947 ms
64 bytes from 31.133.128.1: icmp_seq=18 ttl=64 time=1923.856 ms
64 bytes from 31.133.128.1: icmp_seq=19 ttl=64 time=2028.737 ms
64 bytes from 31.133.128.1: icmp_seq=20 ttl=64 time=1993.952 ms
64 bytes from 31.133.128.1: icmp_seq=21 ttl=64 time=2092.593 ms

% ifconfig en0
en0: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu 1500
	ether a4:5e:60:cf:bf:9b
	inet6 fe80::1ccc:7c66:e6d2:b53b%en0 prefixlen 64 secured scopeid 0x4
	inet6 2001:67c:370:128:448:9ce1:407:9e71 prefixlen 64 autoconf secured
	inet6 2001:67c:370:128:c55b:6eb6:be50:ed25 prefixlen 64 autoconf temporary
	inet 31.133.135.81 netmask 0xfffff000 broadcast 31.133.143.255
	nd6 options=201<PERFORMNUD,DAD>
	media: autoselect
	status: active

Change history (4)

comment:1 Changed 10 months ago by llynch@…

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

comment:2 Changed 10 months ago by panda@…

Status: assignedaccepted

Hi Ray,

Thank you for the report.

I'll go down there and check now. The short outage of uplink switch we observed ~10 min ago might be related to this issue.

Best,
Hirochika Asai

comment:3 Changed 10 months ago by panda@…

Resolution: fixed
Status: acceptedclosed

Hi,

We also occasionally hit some packet losses on the same AP as you saw this issue.

To fix it, we rebalance the client load with other APs. It should become better now. We will also improve the channel allocation after today's session. If you experience this issue again, please re-open this ticket.

Thank you.
Hirochika Asai

comment:4 Changed 2 months ago by Rick Alfvin

Milestone: ietf-98ietf-098

Milestone renamed

Note: See TracTickets for help on using tickets.