NOTICE: IP: Fatal error (104) on interface ppp0, marking down.

NOTICE: IP: Fatal error (104) on interface ppp0, marking down.

Post by Tom Lindamo » Sat, 18 May 1996 04:00:00



What is 104?

TIA,
tom

 
 
 

NOTICE: IP: Fatal error (104) on interface ppp0, marking down.

Post by Peter Wol » Fri, 24 May 1996 04:00:00




>What is 104?

Errno 104 perhaps?  ... from /usr/include/sys/errno.h:

#define ENETDOWN        (TCPERR+14)      /* Network is down */

--

                        Telos Engineering  Ltd.

 
 
 

NOTICE: IP: Fatal error (104) on interface ppp0, marking down.

Post by Troy DeJon » Sat, 25 May 1996 04:00:00



>What is 104?
>TIA,
>tom

You'll see the "NOTICE: IP Fatal error (104) on interface ppp0, marking down"
message when IP gets a M_ERROR STREAMS message block from its data link
provider; in this case PPP  (the "NOTICE:" part of the string gives away
the fact that it's a kernel message :-).

My guess is that the PPP multiplexor encountered something and logged it
in /usr/adm/syslog.  Check that file for any clues.

--

 
 
 

NOTICE: IP: Fatal error (104) on interface ppp0, marking down.

Post by Tom Lindamo » Sat, 25 May 1996 04:00:00




>>What is 104?
>>TIA,
>>tom
>You'll see the "NOTICE: IP Fatal error (104) on interface ppp0, marking down"
>message when IP gets a M_ERROR STREAMS message block from its data link
>provider; in this case PPP  (the "NOTICE:" part of the string gives away
>the fact that it's a kernel message :-).
>My guess is that the PPP multiplexor encountered something and logged it
>in /usr/adm/syslog.  Check that file for any clues.

Yes, it is a kernal messsage - the network is down.  It occurs immediately
after the ifconfig ppp0 line in tcp start with the following conditions
ONLY:
1.      must be a restart from boot.
2.      resolv.conf must exist and nameserver is other end of ppp
3.      the error will only occure only for a given config. eg:
        setup resolv.conf, boot, get error, shutdown, boot,
        no error BUT no localhost either. ping will just sit there.

lines from syslog:
May 23 18:20:15 tclcsi syslogd: restart
May 23 18:20:15 tclcsi pppd[352]: restarted
May 23 18:20:16 tclcsi pppd[352]: PPCID_REQ
May 23 18:20:16 tclcsi pppd[352]: Dialing host 'netcomp'(0xa000203) -
        uucp system 'netcomp'
May 23 18:20:52 tclcsi pppd[352]: Connecting '/dev/ttyi1G' under PPP
May 23 18:20:52 tclcsi pppd[352]: bound to host 'localhost' port 911.
May 23 18:20:52 tclcsi pppd[352]: accept on socket 5
May 23 18:26:53 tclcsi pppd[352]: PPCID_CLOSE: muxid=57
May 23 18:26:53 tclcsi pppd[352]: ppp_rm_conn: I_UNLINK muxid=57
May 23 18:26:53 tclcsi pppd[352]: Outgoing call on '/dev/console' disconnected
May 23 18:26:55 tclcsi pppd[352]: accept on socket 5
----- REBOOT -----
May 23 18:27:13 tclcsi syslogd: exiting on signal 15
May 23 18:29:47 tclcsi syslogd: restart
May 23 18:29:47 195.1.1.1 pppd[354]: restarted
May 23 18:29:48 195.1.1.1 pppd[354]: PPCID_REQ
May 23 18:31:48 195.1.1.1 pppd[354]: unknown host localhost
May 23 18:32:03 195.1.1.1 lockd[502]: stat_mon(): Connection timed out
May 23 18:32:52 tclcsi routed[358]: deleting route to
        interface ppp0 (timed out)
May 23 18:34:31 tclcsi syslogd: exiting on signal 15

Yes, it is connected to port 7 of a pc8e.

Any ideas?
TIA
tom

 
 
 

1. IP: Fatal (104) error ppp0 <- Any Ideas?

This only appear as the system is comming up after a full
shutdown.

This message is followed by "ppp0 marked as down"
Then the modem dials.  I login to my system, ifconfig ppp0 up,
route add default <forign DNS machine>, start mosaic, all is well
as long as the modem doesn't hang up.  When the modem hangs up,
anything remotely related to TCP grinds to a halt.  The only way
to get ppp to redial is to shutdown and restart.  No, a tcp stop/start
won't do the job. It must be a full reboot.

Anybody got a idea of what is wrong and/or what to do to fix it?
SCO 3.2.4.2, TCP 1.2

thanx in advance,
tom

2. MEMORY MAPPING PROBLEM

3. XIO: fatal error 104

4. Help: Net installation bootdisk for 2940UW and SMC etherpower PCI card

5. X windows problem - XIO: fatal IO error 104

6. Batchmode Printing of Mime-Messages

7. fatal timeout; fatal error resetting interface

8. new linux user

9. Linux for PC/104 + GUI interface

10. pc/104 dual rs422 serial interface supporting linux (rtai)

11. 2.1.104 compilation error

12. What causes accept() error 104 ECONNRESET?

13. Socket Error: Accept Failed 32/104/111