response 125 of 405:

Apr 23 22:17 UTC 2004

        Kung Foo Booting

response 127 of 405:

Apr 24 20:59 UTC 2004

Looks like the network connection went down again at 15:45 Saturday
afternoon, judging by party.

response 129 of 405:

Apr 25 07:00 UTC 2004

Still down....
  2:47am  up 5 days,  5:06,  2 users,  load average: 0.23, 0.20, 0.00
Login      Name               TTY  Idle  Login Time   Location   Work Phone
newuser  The Newuser Program   p0 11:26  Apr 24 13:51
rcurl    Rane Curl            *s5        Apr 25 02:47

Also, very s..l..o..w.

response 131 of 405:

Apr 25 17:56 UTC 2004

I'm all alone, except for newuser who has been here for 24 hours:
~r who
tpryan   ttypb    Apr 25 13:54 (216.93.104.37)
newuser  ttyp0    Apr 24 13:51 (1-m-108-cg.del.b)

response 133 of 405:

Apr 25 19:51 UTC 2004

I think we don't need this many dial-in lines.

response 135 of 405:

Apr 26 00:30 UTC 2004

  8:28pm  up 5 days, 22:47,  2 users,  load average: 0.34, 0.30, 0.01
Login      Name               TTY  Idle  Login Time   Location   Work Phone
newuser  The Newuser Program   p0    1d  Apr 24 13:51
rcurl    Rane Curl            *t4        Apr 25 20:28

Still down. Newuser process still running. Where are the staff when the
system needs them? 

response 139 of 405:

Apr 26 13:56 UTC 2004

734-761-3000.  If you run the 'phones' command from a shell prompt you
can get a full list of numbers, but of course that doesn't help you when
you can't get in to run it. ;>

response 141 of 405:

Apr 26 16:40 UTC 2004

  Any sense whether the outages are due to a dying DSL modem
  (easily fixable) or something less accessible (line problems,
  DSLAM link issues)?

  If it's just a DSL modem that's going bad I can probably scare
  up a replacement.

response 143 of 405:

Apr 26 17:41 UTC 2004

  You'd be surprised, really..  Someone does some work on the next
  line over at the demarc point for the building and messes up,
  or runs jumpers on the frame at the CO but messes up which pins
  and gets a split pair, or any of a dozen other things and suddenly
  you can have all kinds of problems..  Sometimes just plugging an
  extra phone or answering machine onto the line is enough to cause
  a capacitance issue that can complicate borderline DSL.

  Other possibilities include an equipment upgrade on the DSLAM side
  that doesn't like the Grex modem (for whatever reason) or, well,
  basically a whole long list of things.

  On the other hand, the modem is what I'd be looking at first.

  If I can ask Kip, do the modem LEDs indicate that it's losing link
  to the DSLAM?  And does it re-link after power cycling, but not
  do so automatically (without needing to be "kicked" as you put it)?

response 145 of 405:

Apr 26 18:57 UTC 2004

if its a DSL service issue, grex should be entitled to a discount on its next
ISP bill to account for the down time

response 147 of 405:

Apr 26 19:38 UTC 2004

  Obviously Grex doesn't have a randomly assigned IP address, but does the
  DSL provider give a DHCP lease for the address they have assigned or is it
  a permanent static?  Could this be a lease expiration issue?

  Is there a way to get through directly to a reasonably competent tech at
  the DSL provider?  It would be instructive, next time there's an outage,
  to have them try (a) sending an ATM "ping" packet to the modem, (b) sending
  an IP ping or traceroute to the Grex static IP.  With the connection
  currently working, the end of my traceroute to Grex looks like:

  > 18  rback0.flnt.mi.voyager.net (216.93.15.210)  
  > 19  cyberspacecomm.flnt.mi.voyager.net (216.93.107.238)  
  > 20  grex.cyberspace.org (216.93.104.34)  

  Based on the name, I'm presuming that hop 18 is a Redback used by Voyager
  to terminate the ATM connection from the modem and convert to IP.  I could
  be making a bad assumption, however, because then I'm not sure what the
  function would be of hop 19, cyberspacecomm.flnt.mi.voyager.net, unless
  that's a router that belongs to Grex and not Voyager.net.  I suppose it's
  also possible it's the modem, depending on how they configure things (at my
  ISP, we configure the DSL modems to just do bridging but there are all sorts
  of ways you might choose to set things up.)

  Anyway, it'd be worth getting some more information about what's going on
  with the modem when things freeze like this, but of course I understand
  that (a) getting things back up and running immediately makes the most
  people happy in the short term, and (b) you're doing this on your own
  volunteer time and might not necessarily have a whole lot of such time
  to devote to the troubleshooting.

response 149 of 405:

Apr 26 23:28 UTC 2004

        If you can't get into Grex, you can always go to
http://www.grex.org and read the phone number on the page.

(wink wink, nudge nudge)