From: Jerome M Berkman (jerry@uclink.berkeley.edu)
Date: Fri Dec 14 2001 - 16:55:11 PST
I did a quick check on UCLink, and today by hour the results were:
1: 3233 tries, 43% succeeded
2: 2854 tries, 51% succeeded
3: 2498 tries, 81% succeeded
4: 2517 tries, 82% succeeded
5: 2211 tries, 82% succeeded
6: 2118 tries, 81% succeeded
7: 2189 tries, 84% succeeded
8: 2497 tries, 82% succeeded
9: 2721 tries, 76% succeeded
10: 2994 tries, 70% succeeded
11: 3374 tries, 66% succeeded
12: 3509 tries, 65% succeeded
13: 3692 tries, 66% succeeded
14: 3986 tries, 80% succeeded
I.e. from 2pm to 3pm, 80% of the log lines concerning client.attbi.com
showed a successful connection.
The varying percentages could be due to changes by AT&T or by changes
in who is trying to connect or ...
Yesterday morning, the success rate was 0%, so there has been
improvement. However, this is small comfort if you are one of the
people who can not connect.
- Jerry
On Fri, 14 Dec 2001, Eileen Pinto wrote:
> Has anyone had any further update/information from ATTBI on this issue?
>
> From my own experience (not being able to connect to campus hosts running
> TCP_WRAPPERS), polling other ATTBI users who ARE able to connect, and
> having the ongoing problem of losing
> connectivity to other campus servers periodically and sometimes being able
> to regain a connection
> by releasing and renewing the IP addresses, but often not being able to do
> so, it seems that these problems really are ATTBI hub-specific and are due
> to DHCP server capacity issues in allocating IP addresses for that
> hub. For instance, folks on the (former?) Pinole hub can connect and can
> maintain their connections (obtain/renew an ip when it expires) just fine;
> those on the Pleasanton and other very crowded (SF? Berkeley? not sure
> where these map) hubs have had the ip renewal problem, plus now the problem
> that ATTBI caused starting Tuesday 12/11 when they tried to "fix" this
> bottleneck.
>
> Just my take on it.
>
> Sending email regarding the problem has only resulted in a canned response
> from the Online Customer Support Center which had absolutely nothing to do
> with the actual problem itself, so for campus connectivity from home, it's
> been back to Earthlink for now.
...
------------------------------------------------------------------------
The following was automatically added to this message by the list server:
For information about Micronet, its meetings and events, and its
mailing list, including information on subscribing and unsubscribing,
see the Micronet Web site at <http://wss.berkeley.edu/micronet/>.
This archive was generated by hypermail 2b29 : Fri Dec 14 2001 - 16:56:56 PST