Very Computer

I'm getting some kernel messages that lead me to think that for
some reason pppd can't transmit anything via my modem
(which is funny, because minicom works fine).  See below.

Here's the very short output on the system log:

   [ chat script to dial, etc. ]

Jan 20 18:45:48 sebastian chat[1221]: CONNECT -- got it
Jan 20 18:45:48 sebastian chat[1221]: send (^M)
Jan 20 18:45:48 sebastian pppd[1217]: Serial connection established.
Jan 20 18:45:49 sebastian pppd[1217]: Using interface ppp0
Jan 20 18:45:49 sebastian pppd[1217]: Connect: ppp0 <--> /dev/modem
Jan 20 18:45:58 sebastian pppd[1217]: Hangup (SIGHUP)
Jan 20 18:45:58 sebastian pppd[1217]: Modem hangup
Jan 20 18:45:58 sebastian pppd[1217]: Connection terminated.
Jan 20 18:45:58 sebastian pppd[1217]: Exit.

(where /dev/modem is a symlink to the appropriate serial device)

So, at 18:45:49 pppd "Conects" and appears ready to go, but
less than 10 seconds later it dies.

Here's the (still short!) syslog output, this time with kdebug 1:

Jan 20 18:45:48 sebastian chat[1221]: CONNECT -- got it
Jan 20 18:45:48 sebastian chat[1221]: send (^M)
Jan 20 18:45:48 sebastian pppd[1217]: Serial connection established.
Jan 20 18:45:49 sebastian kernel: ppp_tty_ioctl: set flags to 10000
Jan 20 18:45:49 sebastian kernel: ppp_tty_ioctl: set flags to 10000
Jan 20 18:45:49 sebastian kernel: ppp_tty_ioctl: set xasyncmap
Jan 20 18:45:49 sebastian kernel: ppp_tty_ioctl: set xmit asyncmap ffffffff
Jan 20 18:45:49 sebastian pppd[1217]: Using interface ppp0
Jan 20 18:45:49 sebastian pppd[1217]: Connect: ppp0 <--> /dev/modem
Jan 20 18:45:49 sebastian kernel: ppp_tty_ioctl: set flags to 10000
Jan 20 18:45:49 sebastian kernel: ppp_tty_ioctl: set mru to 5dc
Jan 20 18:45:49 sebastian kernel: ppp_tty_ioctl: set rcv asyncmap 0
Jan 20 18:45:49 sebastian kernel: ppp_tty_ioctl: set flags to 10010
Jan 20 18:45:56 sebastian kernel: ppp: successfully queued 26 bytes, flags = f010010
Jan 20 18:45:56 sebastian kernel: ppp: successfully queued 24 bytes, flags = f010010
Jan 20 18:45:56 sebastian last message repeated 4 times
Jan 20 18:45:56 sebastian kernel: ppp: successfully queued 6 bytes, flags = f010010
Jan 20 18:45:56 sebastian kernel: ppp: successfully queued 24 bytes, flags = f010010
Jan 20 18:45:58 sebastian kernel: ppp: channel ppp0 closing.
Jan 20 18:45:58 sebastian pppd[1217]: Hangup (SIGHUP)
Jan 20 18:45:58 sebastian pppd[1217]: Modem hangup
Jan 20 18:45:58 sebastian pppd[1217]: Connection terminated.
Jan 20 18:45:58 sebastian pppd[1217]: Exit.

Could anybody please help?    I don't know what's going on
here.

Some other details:

Distribution:           Slackware 3.5.0
Kernel version:         2.0.34
pppd version:           2.2.0
Modem:                  Cardinal MVPV34ILC

About the modem:   I don't know if this is a so-called
"Winmodem".  Calls and email to the company tech
support have failed (no answer on either).   Although the
front of the box says "Works with Windows 95", it also
says it works with "Windos 3.1 or higher / DOS 5.0 or higher".
And as I say, minicom works fine.

I'd be happy to provide more details if required.  I hope
someone out there has the answer!

TIA,

Richard

: My problem: after the modem connects and pppd starts up,
: it dies after 10 seconds, without having established
: a connection.

: Here's the very short output on the system log:

:    [ chat script to dial, etc. ]

: Jan 20 18:45:48 sebastian chat[1221]: CONNECT -- got it
: Jan 20 18:45:48 sebastian chat[1221]: send (^M)
: Jan 20 18:45:48 sebastian pppd[1217]: Serial connection established.
: Jan 20 18:45:49 sebastian pppd[1217]: Using interface ppp0
: Jan 20 18:45:49 sebastian pppd[1217]: Connect: ppp0 <--> /dev/modem
: Jan 20 18:45:58 sebastian pppd[1217]: Hangup (SIGHUP)
: Jan 20 18:45:58 sebastian pppd[1217]: Modem hangup
: Jan 20 18:45:58 sebastian pppd[1217]: Connection terminated.
: Jan 20 18:45:58 sebastian pppd[1217]: Exit.

Best guess at this point would be to replace the chat expect/send
<CONNECT ''> (or <CONNECT ""> with <CONNECT \\c>.  This might have
to be <CONNECT "\\c"> depending on how the script is implemented and
read.  Instead of the <send (^M) above you should get <send ()> since
the carriage return is suppressed.

If this doen't do it, then change teh pppd option "kdebug 1" to "debug"
and post the appropriate log messages if need be.

: Distribution:         Slackware 3.5.0
: Kernel version:               2.0.34
: pppd version:         2.2.0
: Modem:                        Cardinal MVPV34ILC

: About the modem:   I don't know if this is a so-called
: "Winmodem".  Calls and email to the company tech
: support have failed (no answer on either).   Although the
: front of the box says "Works with Windows 95", it also
: says it works with "Windos 3.1 or higher / DOS 5.0 or higher".
: And as I say, minicom works fine.

If minicom works, then it's not of family winmodem.

--

/* Better is the enemy of good enough. */

Then go to the chat script (I believe it is ppp-on-dialer)
and verify that the chat uses the correct strings.

Then you ought to be okelly-dokelly.

Make sure resolv.conf is set also.

Quote:>If minicom works, then it's not of family winmodem.

--
Dave Blake

My problem: after the modem connects and pppd starts up,
it dies after 10 seconds, without having established
a connection.

I'm getting some kernel messages that lead me to think that for
some reason pppd can't transmit anything via my modem
(which is funny, because minicom works fine).  See below.

Here's the very short output on the system log:

   [ chat script to dial, etc. ]

Jan 20 18:45:48 sebastian chat[1221]: CONNECT -- got it
Jan 20 18:45:48 sebastian chat[1221]: send (^M)
Jan 20 18:45:48 sebastian pppd[1217]: Serial connection established.
Jan 20 18:45:49 sebastian pppd[1217]: Using interface ppp0
Jan 20 18:45:49 sebastian pppd[1217]: Connect: ppp0 <--> /dev/modem
Jan 20 18:45:58 sebastian pppd[1217]: Hangup (SIGHUP)
Jan 20 18:45:58 sebastian pppd[1217]: Modem hangup
Jan 20 18:45:58 sebastian pppd[1217]: Connection terminated.
Jan 20 18:45:58 sebastian pppd[1217]: Exit.

(where /dev/modem is a symlink to the appropriate serial device)

So, at 18:45:49 pppd "Conects" and appears ready to go, but
less than 10 seconds later it dies.

Here's the (still short!) syslog output, this time with kdebug 1:

Jan 20 18:45:48 sebastian chat[1221]: CONNECT -- got it
Jan 20 18:45:48 sebastian chat[1221]: send (^M)
Jan 20 18:45:48 sebastian pppd[1217]: Serial connection established.
Jan 20 18:45:49 sebastian kernel: ppp_tty_ioctl: set flags to 10000
Jan 20 18:45:49 sebastian kernel: ppp_tty_ioctl: set flags to 10000
Jan 20 18:45:49 sebastian kernel: ppp_tty_ioctl: set xasyncmap
Jan 20 18:45:49 sebastian kernel: ppp_tty_ioctl: set xmit asyncmap ffffffff
Jan 20 18:45:49 sebastian pppd[1217]: Using interface ppp0
Jan 20 18:45:49 sebastian pppd[1217]: Connect: ppp0 <--> /dev/modem
Jan 20 18:45:49 sebastian kernel: ppp_tty_ioctl: set flags to 10000
Jan 20 18:45:49 sebastian kernel: ppp_tty_ioctl: set mru to 5dc
Jan 20 18:45:49 sebastian kernel: ppp_tty_ioctl: set rcv asyncmap 0
Jan 20 18:45:49 sebastian kernel: ppp_tty_ioctl: set flags to 10010
Jan 20 18:45:56 sebastian kernel: ppp: successfully queued 26 bytes, flags
= f010010
Jan 20 18:45:56 sebastian kernel: ppp: successfully queued 24 bytes, flags
= f010010
Jan 20 18:45:56 sebastian last message repeated 4 times
Jan 20 18:45:56 sebastian kernel: ppp: successfully queued 6 bytes, flags
= f010010
Jan 20 18:45:56 sebastian kernel: ppp: successfully queued 24 bytes, flags
= f010010
Jan 20 18:45:58 sebastian kernel: ppp: channel ppp0 closing.
Jan 20 18:45:58 sebastian pppd[1217]: Hangup (SIGHUP)
Jan 20 18:45:58 sebastian pppd[1217]: Modem hangup
Jan 20 18:45:58 sebastian pppd[1217]: Connection terminated.
Jan 20 18:45:58 sebastian pppd[1217]: Exit.

Could anybody please help?    I don't know what's going on
here.

Some other details:

Distribution:           Slackware 3.5.0
Kernel version:         2.0.34
pppd version:           2.2.0
Modem:                  Cardinal MVPV34ILC

About the modem:   I don't know if this is a so-called
"Winmodem".  Calls and email to the company tech
support have failed (no answer on either).   Although the
front of the box says "Works with Windows 95", it also
says it works with "Windos 3.1 or higher / DOS 5.0 or higher".
And as I say, minicom works fine.

I'd be happy to provide more details if required.  I hope
someone out there has the answer!

TIA,

Richard

-----------------------------------------------------

Richard,

There seems something wrong either with your soft link or your ppp dialup
scripts, if you can put your ppp-on and ppp-on-dialer scripts here, I will
be able to help you out! You may try to use the minicom -s first to setup
your modem, when you get the prompt, something like  tip> or whatever, just
type ppp default, you will see the garbage. That means you are able to connect.
(did you link /dev/modem to /dev/ttyS1 first?) You may also give me the
scripts of /etc/ppp/options, /etc/ppp/hosts if you think you are NOT sure about
them. Good luck!

Edmon

--
--
Edmon
Is Cao Cao a wicked man? That is only a novel, don't believe it.

: Could anybody please help?    I don't know what's going on
: here.

Do you have "defaultroute" and "passive" in /etc/ppp/options?
Also put "debug" in there to increase your message output until
you get the problem ironed out, and "lock".

: About the modem:   I don't know if this is a so-called
: "Winmodem".

You don't have a Winmodem. Else you would't even be able to dial out.

:
: I'd be happy to provide more details if required.  I hope
: someone out there has the answer!

There's a lot of answers in /usr/doc/HOWTO/ISP-Hookup-HOWTO. You'll have
to gunzip -d the file or read it with 'most'. You did install the
documentation I hope? Heavy reading is the only way to survive Linux.

--
Suggestion Box:
 To make Usenet more efficient and easier to read,  
 PLEASE trim irrelevant quoted material from replies.

exec /usr/sbin/pppd /dev/modem 115200 \
    asyncmap 200a0000 connect $DIALER_SCRIPT crtscts defaultroute \
    lock netmask $NETMASK noipdefault ipcp-accept-local \
    ipcp-accept-remote -ac debug \
    modem user $ACCOUNT -vj

(several things added in desperation, like ipcp-accept, etc.;
also -vj was added later, something about the university
not liking compressed headers).

Quote:>There's a lot of answers in /usr/doc/HOWTO/ISP-Hookup-HOWTO. You'll have
>to gunzip -d the file or read it with 'most'. You did install the
>documentation I hope? Heavy reading is the only way to survive Linux.

Rich

Quote:>If this doen't do it, then change teh pppd option "kdebug 1" to "debug"
>and post the appropriate log messages if need be.

What could this be?  Kernel problem???

: (Thanks to all who replied; still no luck)  

: >Best guess at this point would be to replace the chat expect/send
: ><CONNECT ''> (or <CONNECT ""> with <CONNECT \\c>.  This might have
: >to be <CONNECT "\\c"> depending on how the script is implemented and
: >read.  Instead of the <send (^M) above you should get <send ()> since
: >the carriage return is suppressed.

: I did it and the problem remains.

: >If this doen't do it, then change teh pppd option "kdebug 1" to "debug"
: >and post the appropriate log messages if need be.

: The log output is identical (except of course for the send() in the
: appropriate place).

There are three logs in my /var/log directoryr: syslog, messages and debug.
The debug file has the ppp negotiation messages, but they may be elsewhere
for your system since /etc/syslog.conf defines where they go.  Look around
in /var/log and if you still can't find them, then add

*.=debug                                        /usr/adm/debug

to /etc/syslog.conf to get the debug messages send to /var/log/debug.

--

/* Better is the enemy of good enough. */