i didn't upgrade or anything, it just started happening randomly.
i run slackware 3.2, kernel 2.0.33, pppd 2.3.5
hmm... i'm not sure about this, but maybe it could have started when i
upgraded to 2.0.33
this is what i found :)
May 10 23:15:00 trauma telnetd[187]: ttloop: peer died: Unknown error
May 16 02:24:39 trauma telnetd[1314]: ttloop: peer died: Unknown error
May 16 20:42:58 trauma telnetd[3659]: ttloop: peer died: Unknown error
May 29 20:08:03 trauma telnetd[281]: ttloop: peer died: Connection timed out
May 29 20:08:18 trauma telnetd[282]: ttloop: peer died: Connection timed out
May 29 20:09:07 trauma telnetd[284]: ttloop: peer died: Connection timed out
Jurgen.
At 11:48 PM 5/29/98 +0000, [EMAIL PROTECTED] wrote:
>Funny you mention this, I recently just had this problem again when I
>ran 4.2 rh now with 5.0 . It happens randomly. After many reboots
>did not fix it, but eventually fixed itself. I did notice though
>sendmail stalled a little when booting up, so maybe a sendmail
>problem? So if anyone has insight on this let me know :).
>
>/var/log/messages
>May 28 22:29:50 bird telnetd[526]: ttloop: peer died: No such file or
director$
>May 28 22:30:12 bird telnetd[527]: ttloop: peer died: No such file or
director$
>May 28 22:58:59 bird telnetd[537]: ttloop: peer died: No such fileor
>directory.
>
>
>> Date: Fri, 29 May 1998 19:29:26 +0200
>> To: [EMAIL PROTECTED]
>> From: Jurgen Philippaerts <[EMAIL PROTECTED]>
>> Subject: [masq] weird ip masq and telnet problem
>
>> hi,
>>
>> ip masquerading has been setup and working well for a couple of months now.
>> but recently i'm having some problems with telnetting to my own linux box
>> from my windows machines.
>> the weird thing is, i see that they connect in the /var/log/messages file,
>> but on the other machines, nothing happens.
>> this is not all the time, sometimes it all works for days, and then
>> suddenly it won't work again.
>> allthough, all machines still do have acces to the internet, they can surf
>> the web, send email, telnet to machines on the net. After a reboot of the
>> linux box, everything is fixed again. and goes well for days, or just some
>> hours.
>>
>> has anyone an idea of what's happening ?
>>
>> thanks,
>> Jurgen.
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: [EMAIL PROTECTED]
>> For additional commands, e-mail: [EMAIL PROTECTED]
>> For daily digest info, email [EMAIL PROTECTED]
>>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
For daily digest info, email [EMAIL PROTECTED]
