Posted by m00 on June 22, 2000 at 12:26:27:
The way to found out what is problem is
when CF appears to be down, can be done
this way:
# ping carrionfields.org
PING carrionfields.org (216.62.186.197): 56 data bytes
112 bytes from adsl-216-62-186-197.dsl.hstntx.swbell.net (216.62.186.197): Destination Port Unreachable
This means that the adsl connection from CF
to the rest of the world (including you) is
UP. Apparently some kind of packet filtering
is in use, which rejects forwarding of icmp_echo
packets (ping), but is humble enough to send back
a "Port unreachable" notice.
If you on the other hand recieves no answer,
the ping packets will time out, this means
there is a NETWORK problem, causing the packets
never to reach the CF firewall. You can
locate where on the net this problem is located
by using traceroute.
traceroute carrionfields.org
traceroute to carrionfields.org (216.62.186.197), 30 hops max, 40 byte packets
1 blah
2 blah
3 blah
eventually the last hop should appear as
21 adsl-216-62-186-197.dsl.hstntx.swbell.net (216.62.186.197) 502.821 ms (laggy) 283.390 ms 222.108 ms
You will see that when CF is down, these days
traceroute will time out at
20 rback1-fa2-0.hstntx.swbell.net
which is the UPLINK for CF. This means
that the problem is related to
adsl-216-62-186-197.dsl.hstntx.swbell.net (CF wan endpoint)
not being able to recieve traffic from it's
uplink. This can be caused a bad router,
misconfiguration, bad cobber thread, whatever
the problem is you can conclude that it is
not a system error on the cf box, but a problem
that the service provider (swbell) will have
to fix. A reboot of the router gear might fix
the problem here and now, but most likely only
for a short while, a solid solution will
have to involve swbell.