On Thu, 24 Jun 1999, Hoang Manh Hung wrote: |Here is my log: | |Jun 24 09:44:37 linux2 pppd[938]: Connect: ppp0 <--> /dev/ttyS0 |Jun 24 09:44:38 linux2 pppd[938]: sent [LCP ConfReq id=0x1 <asyncmap |0x0> <magic | 0xc62f6a9f>] |Jun 24 09:44:38 linux2 pppd[938]: rcvd [LCP ConfReq id=0x1 <asyncmap |0x0> <magic | 0xc62f6a9f>] Pppd is talking to itself, note that the sent and rcvd messages are identical throughout the log. A gross error in the dialer script could have caused a modem loopback. If it's the script I think then something as simple as an unescaped eol could do it - all lines except the last must have a `\' escape just before the eol. ... |Win95 client logon to Solaris PPP server OK. |My system: RH52, kernel 2.0.36, pppd 2.3.8 |My ppp-on script: |#!/bin/sh |LOCAL_IP=0.0.0.0 |REMOTE_IP=0.0.0.0 |DIALER_SCRIPT=/etc/ppp/ppp-on-dialer1 |exec /usr/sbin/pppd /dev/ttyS0 38400 $LOCAL_IP:$REMOTE_IP noaccomp |nobsdcomp noc |cp nodeflate nopcomp debug kdebug 25 connect $DIALER_SCRIPT & kdebug 25 is bogus, a RedHat mistake that seems to have taken on a life of it's own. The valid kdebug values are the integers 0 through 7, although the pppd manual pages could certainly be clearer about that. --- Clifford Kite Not a guru. (tm) - To unsubscribe from this list: send the line "unsubscribe linux-net" in the body of a message to [EMAIL PROTECTED]
