I've made some specific comments below. This sounds to me like a problem at
the ISP end -- that they drop you from time to time. Follow the suggestions
below about reviewing your logs. Does the problem occur after some
particular amount of time connected, or at certain times of the day, or
something like that? I really sounds like the IDP is dropping the connection
and doing a poor job of tidy-exit handshaking. But that's just a guess.
One final thought -- after the connection hangs, run "ifconfig -a" to do two
things:
1. make sure interface ppp0 is still present.
2. note the TX traffic value.
Then ping something and run "ifconfig -a" again, and see if the TX value has
increased. This will confirm that your interface is still working and trying
to send packets to the other end of the static route.
At 01:29 PM 2/26/00 -0800, Ben Holm wrote:
>--- Ray Olszewski <[EMAIL PROTECTED]> wrote:
>> Sounds like you need to do a bit more work to see where in the system the
>> problem lies. When the modem "seems to stop responding" --
>>
>> do apps other than Netscape work successfully? E.g., from
>> an xterm or a vt, can you still ping the ISP's end
>> of the connection (by address? by hostname?)?
>
> Nope. When the modem stops working, all network traffic times out. ping
>still considers the network reachable, but no packets get through. Hmmm. . . I
>guess I should so no packets come back.
OK. That means the link is really dead. ping "considers the network
reachable" only because the route is still in the routing table (at least I
assume it is).
>
>> do any informative messages get written to your logs?
>
> Can you suggest which logs I could look at and how to turn them on?
No, because logging is system specific and I don't know what defaults
Caldera uses. Look in /var/log and see what is there. Look in
/etc/syslog.conf to see what logging pattern your system uses ("man syslogd"
for help in understanding this). You especially want to look for messages
posted by pppd, including what it says after it finally does disconnect.
>> is there any pattern to the failures beyond what you have
>> said? E.g., does Netscape get stuck at DNS lookups?
>> Is it always at the same URL (or within a set of
>> related URLs)?
>
> There is no pattern like that. If something is doing a lookup, that fails,
>if a page is in the middle of loading, it stalls and never resumes. I only
>visit a few web pages, but I can't think what they would have in common.
>(yahoo, google, slashdot, cnet, etc)
Me either. Anyway, the ping result you reported above pretty much indicates
this is a ppp link problem.
>> You say "this happens most often when I run netscape". When
>> else does it happen and what are the apps trying to
>> do when they seem to fail?
> That is the only thing I've been able to notice. I believe there have been a
>couple instances when I've not been running netscape and this has happened, but
>I cannot be sure.
[old message deleted]
------------------------------------"Never tell me the odds!"---
Ray Olszewski -- Han Solo
Palo Alto, CA [EMAIL PROTECTED]
----------------------------------------------------------------
-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at http://www.linux-learn.org/faqs
