Opened 3 years ago

Closed 3 years ago

Last modified 5 weeks ago

#867 closed defect (duplicate)

ietf-hotel connection heavy packet losses from the hotel room

Reported by: tobias.gondrom@… Owned by: cdoyle@…
Priority: tbd Milestone: ietf-091
Component: network Keywords:
Cc: My Current Location:
My MAC Address: My OS:

Description

Hi dear NOC team,

it seems I loose a lot of packets and have large latency when using 
ietf-hotel wifi from my hotel room (Alii tower floor 15, room 1514). 
When connecting in the conference centre terminal room, I have no problems.

As a quick illustration, here three pings I just did to a www, and one 
to a mail-server:

$ ping facebook.com
PING facebook.com (173.252.120.6) 56(84) bytes of data.
64 bytes from edge-star-shv-12-frc3.facebook.com (173.252.120.6): 
icmp_seq=33 ttl=78 time=125 ms
64 bytes from edge-star-shv-12-frc3.facebook.com (173.252.120.6): 
icmp_seq=49 ttl=78 time=122 ms
64 bytes from edge-star-shv-12-frc3.facebook.com (173.252.120.6): 
icmp_seq=50 ttl=78 time=121 ms
64 bytes from edge-star-shv-12-frc3.facebook.com (173.252.120.6): 
icmp_seq=52 ttl=78 time=130 ms
64 bytes from edge-star-shv-12-frc3.facebook.com (173.252.120.6): 
icmp_seq=62 ttl=78 time=121 ms
^C
--- facebook.com ping statistics ---
62 packets transmitted, 5 received, 91% packet loss, time 65584ms
rtt min/avg/max/mdev = 121.354/124.173/130.195/3.423 ms

$ ping www.gondrom.org
PING www.gondrom.org (5.35.241.16) 56(84) bytes of data.
64 bytes from www.gondrom.org (5.35.241.16): icmp_seq=13 ttl=48 time=232 ms
64 bytes from www.gondrom.org (5.35.241.16): icmp_seq=14 ttl=48 time=224 ms
64 bytes from www.gondrom.org (5.35.241.16): icmp_seq=16 ttl=48 time=229 ms
64 bytes from www.gondrom.org (5.35.241.16): icmp_seq=17 ttl=48 time=239 ms
64 bytes from www.gondrom.org (5.35.241.16): icmp_seq=20 ttl=48 time=218 ms
64 bytes from www.gondrom.org (5.35.241.16): icmp_seq=21 ttl=48 time=219 ms
64 bytes from www.gondrom.org (5.35.241.16): icmp_seq=23 ttl=48 time=236 ms
64 bytes from www.gondrom.org (5.35.241.16): icmp_seq=34 ttl=48 time=230 ms
^C
--- www.gondrom.org ping statistics ---
35 packets transmitted, 8 received, 77% packet loss, time 34208ms
rtt min/avg/max/mdev = 218.953/228.861/239.729/7.159 ms

$ ping mail.gondrom.org
PING mail.gondrom.org (5.35.241.16) 56(84) bytes of data.
64 bytes from 5.35.241.16: icmp_seq=3 ttl=48 time=218 ms
64 bytes from 5.35.241.16: icmp_seq=9 ttl=48 time=219 ms
64 bytes from 5.35.241.16: icmp_seq=17 ttl=48 time=219 ms
64 bytes from 5.35.241.16: icmp_seq=20 ttl=48 time=218 ms
64 bytes from 5.35.241.16: icmp_seq=23 ttl=48 time=219 ms
64 bytes from 5.35.241.16: icmp_seq=27 ttl=48 time=218 ms
^C
--- mail.gondrom.org ping statistics ---
27 packets transmitted, 6 received, 77% packet loss, time 35379ms
rtt min/avg/max/mdev = 218.760/219.057/219.512/0.448 ms


I hope you could help in any way?

Thanks a lot for all your good work making our IETF meetings happen and 
all the best,

Tobias



Tobias Gondrom
IETF Administrative Oversight Committee (IAOC)
email: tobias.gondrom@gondrom.org
mobile: +852 56002975
mobile: +44 7521003005
skype: tgondrom
twitter: @tgondrom


Change history (5)

comment:1 Changed 3 years ago by llynch@…

Component: incomingnetwork
Owner: changed from llynch@… to nkukich@…
Status: newassigned
Type: requestdefect

comment:2 Changed 3 years ago by cdoyle@…

Owner: changed from nkukich@… to cdoyle@…

Sorry to hear you are having issues with the hotel wireless. This system uses motorola radios and is managed by AT&T with our SSID riding over the top. There are a few things we can try to isolate the issue.

First, have you tried using your wired connection? The cable on your desk should plug into a small distribution block. Port 2 provides access via the hotel infrastructure to the IETF network.

Second, if you connect to the Hilton SSID (and presumably the same WAP), do you experience the same issues? The access code for the Hilton network is "moku".

Finally, can you provide the BSSID of the access point you are connected to in your room?

It may be that the wifi in your room is just simply going to be poor and the wire is your best option. That being said, we'll let AT&T know you are having an issue (once you provide your BSSID) and hopefully they can make adjustments to improve your service.

comment:3 in reply to:  2 Changed 3 years ago by cdoyle@…

Replying to cdoyle@…:

Sorry to hear you are having issues with the hotel wireless. This system uses motorola radios and is managed by AT&T with our SSID riding over the top. There are a few things we can try to isolate the issue.

First, have you tried using your wired connection? The cable on your desk should plug into a small distribution block. Port 2 provides access via the hotel infrastructure to the IETF network.

Second, if you connect to the Hilton SSID (and presumably the same WAP), do you experience the same issues? The access code for the Hilton network is "moku".

Finally, can you provide the BSSID of the access point you are connected to in your room?

It may be that the wifi in your room is just simply going to be poor and the wire is your best option. That being said, we'll let AT&T know you are having an issue (once you provide your BSSID) and hopefully they can make adjustments to improve your service.

Turns out that the ticketing system is handling replies different now then it was before. So sorry for the radio silence. Please click the link to check the ticket directly to see the current notes.

comment:4 Changed 3 years ago by jim@…

Resolution: duplicate
Status: assignedclosed

Tobias,

We're tracking this issue in https://tickets.meeting.ietf.org/ticket/882 so I'm closing this one as duplicate. Please do continue to work with us in that other ticket as we do hope to resolve or at least ameliorate your issues...

  • Jim

comment:5 Changed 5 weeks ago by Rick Alfvin

Milestone: ietf-91ietf-091

Milestone renamed

Note: See TracTickets for help on using tickets.