Opened 4 years ago

Closed 4 years ago

Last modified 5 weeks ago

#676 closed request (fixed)

broken/slow network in "internet area" between east and tower lifts

Reported by: mellon@… Owned by: cdoyle@…
Priority: minor Milestone: ietf-089
Component: incoming Keywords:
Cc: My Current Location:
My MAC Address: My OS:

Description

I'm getting classic bufferbloat symptoms on the ietf ssid, and no router advertisements on ietf-nat64.   Is there hope?

divertimento% ping toccata.fugue.com
PING toccata.fugue.com (204.152.186.142): 56 data bytes
Request timeout for icmp_seq 0
64 bytes from 204.152.186.142: icmp_seq=0 ttl=51 time=1291.506 ms
64 bytes from 204.152.186.142: icmp_seq=1 ttl=51 time=629.287 ms
64 bytes from 204.152.186.142: icmp_seq=2 ttl=51 time=917.290 ms
64 bytes from 204.152.186.142: icmp_seq=3 ttl=51 time=593.108 ms
64 bytes from 204.152.186.142: icmp_seq=4 ttl=51 time=514.889 ms
64 bytes from 204.152.186.142: icmp_seq=5 ttl=51 time=338.785 ms
64 bytes from 204.152.186.142: icmp_seq=6 ttl=51 time=411.623 ms
64 bytes from 204.152.186.142: icmp_seq=7 ttl=51 time=856.254 ms
Request timeout for icmp_seq 9
Request timeout for icmp_seq 10
Request timeout for icmp_seq 11
64 bytes from 204.152.186.142: icmp_seq=9 ttl=51 time=3334.804 ms
64 bytes from 204.152.186.142: icmp_seq=10 ttl=51 time=2406.744 ms
64 bytes from 204.152.186.142: icmp_seq=11 ttl=51 time=1971.615 ms
64 bytes from 204.152.186.142: icmp_seq=12 ttl=51 time=1114.665 ms
64 bytes from 204.152.186.142: icmp_seq=13 ttl=51 time=275.670 ms
64 bytes from 204.152.186.142: icmp_seq=14 ttl=51 time=514.770 ms
64 bytes from 204.152.186.142: icmp_seq=15 ttl=51 time=2626.635 ms
64 bytes from 204.152.186.142: icmp_seq=16 ttl=51 time=1824.660 ms
64 bytes from 204.152.186.142: icmp_seq=17 ttl=51 time=2692.555 ms
64 bytes from 204.152.186.142: icmp_seq=18 ttl=51 time=1800.277 ms
64 bytes from 204.152.186.142: icmp_seq=19 ttl=51 time=1656.193 ms
64 bytes from 204.152.186.142: icmp_seq=20 ttl=51 time=800.514 ms

Change history (7)

comment:1 Changed 4 years ago by llynch@…

Owner: changed from llynch@… to cdoyle@…
Status: newassigned

comment:2 Changed 4 years ago by cdoyle@…

Priority: tbdminor
Type: requestdefect

To confirm, you were connected to the IETF SSID in the lobby area between towers, correct?

comment:3 Changed 4 years ago by mellon@…

On Mar 3, 2014, at 9:54 AM, IETF Meeting/NOC <tickets@meeting.ietf.org> wrote:
> To confirm, you were connected to the IETF SSID in the lobby area between
> towers, correct?

The lobby area between the east elevators and the tower elevators.

comment:4 Changed 4 years ago by cdoyle@…

Type: defectrequest

We had an IETF WAP in the lobby area by the piano in the atrium bar (Edg I think is the name of the bar there). It's been removed so that users can no longer connect to the IETF meeting SSID's in the public lobby areas. Initially, the ietf-hotel SSID was not configured on the hotel WAP's. Now that ietf-hotel is broadcasting, the utility of an IETF meeting WAP in these public areas is marginal. Further, attendee systems that prefer the IETF meeting SSID's would run the risk of making a less-than-ideal association to this device. This is what I imagine was happening to you. If you were in the lobby area between the tower elevator banks, then you were a good distance from the WAP we had deployed, with a full bank of elevators complicating things further.

So the end result now is that you shouldn't see the IETF meeting SSID's from that area. That being said, you should be able to connect to the many hotel WAP's broadcasting the ietf-hotel SSID.

When you can, would confirm that you can connect to the ietf-hotel SSID in this area and that it's working well for you?

Thank you.

comment:5 Changed 4 years ago by mellon@…

On Mar 3, 2014, at 10:17 AM, IETF Meeting/NOC <tickets@meeting.ietf.org> wrote:
> When you can, would confirm that you can connect to the ietf-hotel SSID in
> this area and that it's working well for you?

I'll try, but I'm not sure when—today is my busiest day... :}

comment:6 Changed 4 years ago by cdoyle@…

Resolution: fixed
Status: assignedclosed

Thank you for your feedback. As we are at the end of the meeting, I am closing this ticket. See you in Toronto!

Colin

comment:7 Changed 5 weeks ago by Rick Alfvin

Milestone: ietf-89ietf-089

Milestone renamed

Note: See TracTickets for help on using tickets.