Opened 9 years ago

Closed 9 years ago

Last modified 8 years ago

#30 closed request (duplicate)

Poor connectivity in Convention2 and 3

Reported by: Elwyn Davies <elwynd@…> Owned by: joelja@…
Priority: major Milestone:
Component: wireless Keywords:
Cc: harald@… My Current Location:
My MAC Address: My OS:

Description (last modified by harald@…)

Hi.

Using the excellent connectivity here on the terrace (very pleasant), I 
would like to report that L3 connectivity in the front left hand corner 
of Convention 2 (RTGWG meeting this morning) was very poor.  Using 
Windows XP/802.11b/g, I could see the phyical networks and connect to 
ietf ,ietf-cgnat or ietf1x (and indeeed ietf-v6only) at L2 but L3 
connectivity varied from poor to non-existent.  Acquiring an address 
took a long time and packet loss variied from 100% most of the time to 
maybe 20% fr about 5 minutes.  DNS service was intermittent and 
connection to mail servers in various locations timed out repeatedly.

I experienced similar problems close to the stage in Convention 3 yesterday.

Regards,
Elwyn

Change history (7)

comment:1 Changed 9 years ago by Elwyn Davies

id: 30

This message has 0 attachment(s)

comment:2 Changed 9 years ago by harald@…

Description: modified (diff)
Priority: blocker
Type: request

I can confirm this for the middle of Convention3 too, at around 10:50:

hta@trd-hta-t60:~$ ping 129.241.1.99
PING 129.241.1.99 (129.241.1.99) 56(84) bytes of data.
64 bytes from 129.241.1.99: icmp_seq=1 ttl=243 time=8715 ms
64 bytes from 129.241.1.99: icmp_seq=2 ttl=243 time=8620 ms
64 bytes from 129.241.1.99: icmp_seq=4 ttl=243 time=8049 ms
64 bytes from 129.241.1.99: icmp_seq=5 ttl=243 time=7666 ms
64 bytes from 129.241.1.99: icmp_seq=6 ttl=243 time=7372 ms

Ping times varied all the way up to 30 seconds.

comment:3 Changed 9 years ago by llynch@…

Cc: harald@… added
Component: incomingwireless
Owner: changed from llynch@… to joelja@…
Priority: blockermajor
Status: newassigned

Gents -

The connections were bad in c2/3 earlier today (many folks associated with the center of the room ap) but we believe this problem has been fixed.

If you continue to see poor performance, please advice.

  • Lucy

comment:4 Changed 9 years ago by anonymous

We did some tuning in the ballrooms so we'll have to see in the afternoon

comment:5 Changed 9 years ago by llynch@…

Elwyn reports:

Date: Tue, 29 Jul 2008 15:53:43 +0100
From: Elwyn Davies <elwynd@googlemail.com>
To: trac@meeting.ietf.org
Cc: joelja@bogus.com, harald@alvestrand.no, llynch@civil-tongue.net
Subject: Re: [IETF Meeting/NOC] #30: Poor connectivity in Convention2 and 3
    - further report

    [ The following text is in the "UTF-8" character set. ]
    [ Your display is set for the "US-ASCII" character set.  ]
    [ Some characters may be displayed incorrectly. ]

Convention 1 back right was working well in 13.00 session.

Convention 2 middle right is rubbish currently (though better than thsi
morning).  Audio Channel 2 comes and goes with useful bursts of about 15
seconds followed by a dropout.

A friend from TCD just came by and fiddled with the AP but it hasn't fixed
the problem yet.

Regards,
Elwyn

Joel -

can you pull the number of associations for the APs in Con2?

  • Lucy

comment:6 Changed 9 years ago by llynch@…

Resolution: duplicate
Status: assignedclosed

rolling up to ticket:42

http://meeting.ietf.org/ticket/30

and closing as duplicate

  • Lucy

comment:7 Changed 8 years ago by (none)

Milestone: IETF Week ieft 72

Milestone IETF Week ieft 72 deleted

Note: See TracTickets for help on using tickets.