I'm sure this is not caused because of incorrect modem init strings or modem
config, because if I dial to another ISP I have no problems at all.
I tryied changing the authentication from PAP to CHAP and it didn't work; with
CHAP it refused to connect every time.
Here is what appears in /var/log/messages
Jul 2 09:59:35 localhost pppd[332]: pppd 2.3.10 started by root, uid 0
Jul 2 09:59:59 localhost pppd[332]: Terminating on signal 15.
Jul 2 10:00:00 localhost pppd[332]: Exit.
Jul 2 10:00:35 localhost modprobe: can't locate module char-major-108
Jul 2 10:00:36 localhost pppd[341]: pppd 2.3.10 started by root, uid 0
Jul 2 10:00:36 localhost pppd[341]: Using interface ppp0
Jul 2 10:00:36 localhost pppd[341]: Connect: ppp0 <--> /dev/ttyS3
Jul 2 10:00:36 localhost pppd[341]: Hangup (SIGHUP)
Jul 2 10:00:36 localhost pppd[341]: Modem hangup
Jul 2 10:00:36 localhost pppd[341]: Connection terminated.
Jul 2 10:00:36 localhost pppd[341]: Exit.
Jul 2 10:01:08 localhost modprobe: can't locate module char-major-108
Jul 2 10:01:08 localhost pppd[344]: pppd 2.3.10 started by root, uid 0
Jul 2 10:01:08 localhost pppd[344]: Using interface ppp0
Jul 2 10:01:08 localhost pppd[344]: Connect: ppp0 <--> /dev/ttyS3
Jul 2 10:01:15 localhost pppd[344]: Remote message: Login Succeeded
Jul 2 10:01:19 localhost kernel: PPP BSD Compression module registered
Jul 2 10:01:23 localhost kernel: PPP Deflate Compression module registered
Jul 2 10:01:24 localhost pppd[344]: local IP address 200.12.228.47
Jul 2 10:01:24 localhost pppd[344]: remote IP address 200.12.228.7
Jul 2 10:01:37 localhost pppd[344]: Terminating on signal 15.
Jul 2 10:01:38 localhost pppd[344]: Connection terminated.
Jul 2 10:01:38 localhost pppd[344]: Connect time 0.5 minutes.
Jul 2 10:01:38 localhost pppd[344]: Sent 372 bytes, received 501 bytes.
Jul 2 10:01:38 localhost pppd[344]: Hangup (SIGHUP)
Jul 2 10:01:39 localhost pppd[344]: Exit.
Jul 2 10:03:20 localhost modprobe: can't locate module char-major-108
Jul 2 10:03:20 localhost pppd[367]: pppd 2.3.10 started by root, uid 0
Jul 2 10:03:20 localhost pppd[367]: Using interface ppp0
Jul 2 10:03:20 localhost pppd[367]: Connect: ppp0 <--> /dev/ttyS3
Jul 2 10:03:26 localhost pppd[367]: Remote message: Login Succeeded
Jul 2 10:03:27 localhost pppd[367]: local IP address 200.12.228.40
Jul 2 10:03:27 localhost pppd[367]: remote IP address 200.12.228.7
I just added "noauth" and "debug" to /etc/ppp/options.... and I'm using MDK
7.0 with a self compiled kernel 2.2.14
Civileme, escribi�:
> Guillermo Belli wrote:
> >
> > Every time I dial my ISP and the modem makes those horrible noises, the pppd
> > daemon dies for no apparent reason. Then, if I try again, it connects without
> > problems. Im' using MDK 7.0, and my ISP's servers use Cobalt Linux.
> >
>
> Such an event could occur if the hardware in front of the cobalts
> require one authentication protocol but can optionally use
> another.
>
> See what happens if you switch either from Chat scripts to PAP or
> vice-versa.
>
> If it occurs before the logon, then it isn't in the software but
> may be in the modem configuration (CRTSCTS vs ... ) or in the
> hardware of the respective modems (OR in the codec used by the
> phone company and the T-1 multiplex/demultiplex circuitry if it
> is 56K stuff)
>
> Can you get any sort of data dump at all?
>
> Civileme
>
> > --
> > ****************************************************
> > *Guillermo Belli - Linux User #121340*
> > * ICQ #38321312 *
> > *http://sites.netscape.net/memo81 (en construccion)*
> > ****************************************************
--
****************************************************
*Guillermo Belli - Linux User #121340*
* ICQ #38321312 *
*http://sites.netscape.net/memo81 (en construccion)*
****************************************************
