Opened 3 years ago

Closed 3 years ago

Last modified 2 months ago

#961 closed defect (duplicate)

Significant packet loss on ietf-hotel SSID on L2

Reported by: furry13@… Owned by: creilly@…
Priority: tbd Milestone: ietf-093
Component: wireless Keywords:
Cc: My Current Location:
My MAC Address: My OS:

Description

Hello,

I'm on L2 (room 2017).
Right now (11:27) I'm seeing some connectivity issues (ietf-hotel
SSID), BSSID: 24:c9:a1:41:98:a8

Ping results:
 furry@Wintermute:~/IETF/IETF93>ping6 www.google.com
PING6(56=40+8+8 bytes) 2001:67c:370:136:61c3:234d:7432:cc36 -->
2a00:1450:4009:800::2004
16 bytes from 2a00:1450:4009:800::2004, icmp_seq=0 hlim=56 time=40.284 ms
16 bytes from 2a00:1450:4009:800::2004, icmp_seq=2 hlim=56 time=199.906 ms
16 bytes from 2a00:1450:4009:800::2004, icmp_seq=3 hlim=56 time=106.576 ms
16 bytes from 2a00:1450:4009:800::2004, icmp_seq=9 hlim=56 time=28.064 ms
16 bytes from 2a00:1450:4009:800::2004, icmp_seq=16 hlim=56 time=90.883 ms
16 bytes from 2a00:1450:4009:800::2004, icmp_seq=17 hlim=56 time=24.949 ms
16 bytes from 2a00:1450:4009:800::2004, icmp_seq=22 hlim=56 time=32.590 ms
16 bytes from 2a00:1450:4009:800::2004, icmp_seq=24 hlim=56 time=40.173 ms
16 bytes from 2a00:1450:4009:800::2004, icmp_seq=25 hlim=56 time=39.465 ms
16 bytes from 2a00:1450:4009:800::2004, icmp_seq=26 hlim=56 time=33.671 ms
16 bytes from 2a00:1450:4009:800::2004, icmp_seq=27 hlim=56 time=26.826 ms
16 bytes from 2a00:1450:4009:800::2004, icmp_seq=28 hlim=56 time=31.027 ms
16 bytes from 2a00:1450:4009:800::2004, icmp_seq=29 hlim=56 time=37.070 ms
16 bytes from 2a00:1450:4009:800::2004, icmp_seq=33 hlim=56 time=114.130 ms
16 bytes from 2a00:1450:4009:800::2004, icmp_seq=34 hlim=56 time=26.218 ms
16 bytes from 2a00:1450:4009:800::2004, icmp_seq=36 hlim=56 time=650.475 ms
16 bytes from 2a00:1450:4009:800::2004, icmp_seq=37 hlim=56 time=33.478 ms
16 bytes from 2a00:1450:4009:800::2004, icmp_seq=38 hlim=56 time=29.863 ms
16 bytes from 2a00:1450:4009:800::2004, icmp_seq=41 hlim=56 time=40.295 ms
16 bytes from 2a00:1450:4009:800::2004, icmp_seq=42 hlim=56 time=53.248 ms
^C
--- www.google.com ping6 statistics ---
49 packets transmitted, 20 packets received, 59.2% packet loss
round-trip min/avg/max/std-dev = 24.949/83.960/650.475/136.630 ms


Ping to default gateway:
furry@Wintermute:~/IETF/IETF93>ping6  fe80::136:1%en0
PING6(56=40+8+8 bytes) fe80::6aa8:6dff:fe12:f7b2%en0 --> fe80::136:1%en0
16 bytes from fe80::136:1%en0, icmp_seq=12 hlim=64 time=16.197 ms
16 bytes from fe80::136:1%en0, icmp_seq=13 hlim=64 time=51.286 ms
16 bytes from fe80::136:1%en0, icmp_seq=14 hlim=64 time=29.276 ms
16 bytes from fe80::136:1%en0, icmp_seq=15 hlim=64 time=9.808 ms
16 bytes from fe80::136:1%en0, icmp_seq=17 hlim=64 time=92.033 ms
16 bytes from fe80::136:1%en0, icmp_seq=18 hlim=64 time=18.522 ms
16 bytes from fe80::136:1%en0, icmp_seq=22 hlim=64 time=101.642 ms
16 bytes from fe80::136:1%en0, icmp_seq=23 hlim=64 time=9.015 ms
16 bytes from fe80::136:1%en0, icmp_seq=27 hlim=64 time=19.339 ms
16 bytes from fe80::136:1%en0, icmp_seq=31 hlim=64 time=17.487 ms
^C
--- fe80::136:1%en0 ping6 statistics ---
33 packets transmitted, 10 packets received, 69.7% packet loss
round-trip min/avg/max/std-dev = 9.015/36.461/101.642/32.338 ms




IPv4 is not much better:
furry@Wintermute:~/IETF/IETF93>ping 31.133.136.1
PING 31.133.136.1 (31.133.136.1): 56 data bytes
Request timeout for icmp_seq 0
64 bytes from 31.133.136.1: icmp_seq=1 ttl=64 time=3.549 ms
Request timeout for icmp_seq 2
64 bytes from 31.133.136.1: icmp_seq=3 ttl=64 time=15.870 ms
64 bytes from 31.133.136.1: icmp_seq=4 ttl=64 time=59.571 ms
64 bytes from 31.133.136.1: icmp_seq=5 ttl=64 time=65.029 ms
Request timeout for icmp_seq 6
Request timeout for icmp_seq 7
64 bytes from 31.133.136.1: icmp_seq=8 ttl=64 time=6.452 ms
64 bytes from 31.133.136.1: icmp_seq=9 ttl=64 time=13.932 ms
64 bytes from 31.133.136.1: icmp_seq=10 ttl=64 time=13.131 ms
Request timeout for icmp_seq 11
Request timeout for icmp_seq 12
64 bytes from 31.133.136.1: icmp_seq=13 ttl=64 time=5.313 ms
^C
--- 31.133.136.1 ping statistics ---
14 packets transmitted, 8 packets received, 42.9% packet loss
round-trip min/avg/max/stddev = 3.549/22.856/65.029/23.182 ms

Let me know if you need more info!

Thanks!

-- 
SY, Jen Linkova aka Furry

Attachments (2)

wifi_morning_tue.png (123.0 KB) - added by furry13@… 3 years ago.
Added by email2trac
wif_Monday_night.png (110.4 KB) - added by furry13@… 3 years ago.
Added by email2trac

Download all attachments as: .zip

Change history (8)

comment:1 Changed 3 years ago by llynch@…

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

hotel side issues

comment:2 Changed 3 years ago by jdishongh@…

Hi Jen,
Thanks for the info. The hotel has turned off their 5Ghz radios and have made adjustments to the radios on the 2.4 band. I'm curious, have you seen improvement?

comment:3 Changed 3 years ago by furry13@…

On Tue, Jul 21, 2015 at 8:31 AM, IETF Meeting/NOC
<tickets@meeting.ietf.org> wrote:
>  Thanks for the info. The hotel has turned off their 5Ghz radios and have
>  made adjustments to the radios on the 2.4 band. I'm curious, have you seen
>  improvement?

I do see an improvement, it's not 50% packet loss anymore and I'm even
able to attach files to my emails ;)
However it is a bit far from working well unfortunately ;(

Just ran ping test to the default gateway and google.com:
furry@Wintermute:~/tmp>ping 31.133.136.1
PING 31.133.136.1 (31.133.136.1): 56 data bytes
64 bytes from 31.133.136.1: icmp_seq=0 ttl=64 time=6.309 ms
Request timeout for icmp_seq 1
64 bytes from 31.133.136.1: icmp_seq=2 ttl=64 time=19.298 ms
64 bytes from 31.133.136.1: icmp_seq=3 ttl=64 time=990.885 ms
64 bytes from 31.133.136.1: icmp_seq=4 ttl=64 time=422.482 ms
64 bytes from 31.133.136.1: icmp_seq=5 ttl=64 time=14.638 ms
64 bytes from 31.133.136.1: icmp_seq=6 ttl=64 time=32.206 ms
Request timeout for icmp_seq 7
Request timeout for icmp_seq 8
Request timeout for icmp_seq 9
64 bytes from 31.133.136.1: icmp_seq=9 ttl=64 time=1389.069 ms
64 bytes from 31.133.136.1: icmp_seq=10 ttl=64 time=501.335 ms
^C
--- 31.133.136.1 ping statistics ---
12 packets transmitted, 8 packets received, 33.3% packet loss
round-trip min/avg/max/stddev = 6.309/422.028/1389.069/489.642 ms

furry@Wintermute:~/tmp>ping www.google.com
PING www.google.com (216.58.210.36): 56 data bytes
64 bytes from 216.58.210.36: icmp_seq=0 ttl=53 time=43.871 ms
Request timeout for icmp_seq 1
64 bytes from 216.58.210.36: icmp_seq=1 ttl=53 time=1359.077 ms
64 bytes from 216.58.210.36: icmp_seq=2 ttl=53 time=613.353 ms
64 bytes from 216.58.210.36: icmp_seq=3 ttl=53 time=75.842 ms
64 bytes from 216.58.210.36: icmp_seq=4 ttl=53 time=38.319 ms
64 bytes from 216.58.210.36: icmp_seq=5 ttl=53 time=24.497 ms
^C
--- www.google.com ping statistics ---
7 packets transmitted, 6 packets received, 14.3% packet loss
round-trip min/avg/max/stddev = 24.497/359.160/1359.077/493.130 ms

Wifi info from my mac attached (one screenshot, "wifi_tue_morning"
just has been taken, another one from the last night which I was not
able to attach in my first email).


-- 
SY, Jen Linkova aka Furry

wifi_morning_tue.png

wif_Monday_night.png

Changed 3 years ago by furry13@…

Attachment: wifi_morning_tue.png added

Added by email2trac

Changed 3 years ago by furry13@…

Attachment: wif_Monday_night.png added

Added by email2trac

comment:4 Changed 3 years ago by creilly@…

Please see Ticket 980

Thank you for your patience.

-Verilan

comment:5 Changed 3 years ago by creilly@…

Resolution: duplicate
Status: assignedclosed

comment:6 Changed 2 months ago by Rick Alfvin

Milestone: ietf-93ietf-093

Milestone renamed

Note: See TracTickets for help on using tickets.