Re: ppp, pmcia and isdn question

["Ulrike Schmidt" <ulrike@example.com>]

>usually you can treat a TA like a modem with the exception of the NEC
ones[1]. If you look at the >documentation of the NEC TA and go through the
list of AT commands you'll find a command called $N that >is for setting the
data port. To be able to do PPP you have to send $N1=1 when initializing the
TA.

I took the init string from the settings I use with windows but this did not
solve the problem.

>No, you _did_ get a connection.  Then _you_ terminated it.  (Well,
>your pppd did.)


>Evidently your PPP configuration is set up to authenticate the remote
>side.  Since GOL expects to do the authentication, and not vice versa,
>it doesn't have a password for you.
>
>Look in the configuration file for stuff that has to do with who
>authenticates who.  I forget whether the relevant thing is in PPP's
>config, or in pap-secrets.


I found the following
in /etc/ppp/options:

<quote>
# Require the peer to authenticate itself before allowing network
# packets to be sent or received.
# Please do not disable this setting. It is expected to be standard in
# future releases of pppd. Use the call option (see manpage) to disable
# authentication for specific peers.
auth
</quote>

in man pppd:

<quote>
              Read  options  from  the  file /etc/ppp/peers/name.
              This file may contain privileged options,  such  as
              noauth, even if pppd is not being run by root.
</quote>

in /etc/ppp/peers/GI (GOL-ISDN):

<quote>
noauth
</quote>

So I thought maybe the settings are correct like this? But still there seems
to be a problem. So I followed the instructions in the ppp-FAQ and logged
the output of the session:

<quote>
Sep 12 21:36:06 debian pppd[1045]: pppd 2.3.11 started by root, uid 0
Sep 12 21:36:07 debian chat[1046]: abort on (BUSY)
Sep 12 21:36:08 debian chat[1046]: abort on (NO CARRIER)
Sep 12 21:36:08 debian chat[1046]: abort on (VOICE)
Sep 12 21:36:08 debian chat[1046]: abort on (NO DIALTONE)
Sep 12 21:36:08 debian chat[1046]: abort on (NO DIAL TONE)
Sep 12 21:36:08 debian chat[1046]: abort on (NO ANSWER)
Sep 12 21:36:08 debian chat[1046]: send (ATZ^M)
Sep 12 21:36:08 debian chat[1046]: expect (OK)
Sep 12 21:36:08 debian chat[1046]: ^M
Sep 12 21:36:08 debian chat[1046]: OK
Sep 12 21:36:08 debian chat[1046]:  -- got it
Sep 12 21:36:08 debian chat[1046]: send (atq0v1x3$s9=10$n1=1&d1^M)
Sep 12 21:36:08 debian chat[1046]: expect (OK)
Sep 12 21:36:08 debian chat[1046]: ^M
Sep 12 21:36:08 debian chat[1046]: ^M
Sep 12 21:36:08 debian chat[1046]: OK
Sep 12 21:36:08 debian chat[1046]:  -- got it
Sep 12 21:36:08 debian chat[1046]: send (ATDT35990050^M)
Sep 12 21:36:09 debian chat[1046]: expect (CONNECT)
Sep 12 21:36:09 debian chat[1046]: ^M
Sep 12 21:36:11 debian chat[1046]: ^M
Sep 12 21:36:11 debian chat[1046]: CONNECT
Sep 12 21:36:11 debian chat[1046]:  -- got it
Sep 12 21:36:11 debian chat[1046]: send (\d)
Sep 12 21:36:12 debian pppd[1045]: Serial connection established.
Sep 12 21:36:12 debian pppd[1045]: Using interface ppp0
Sep 12 21:36:12 debian pppd[1045]: Connect: ppp0 <--> /dev/ttyS0
Sep 12 21:36:13 debian pppd[1045]: sent [LCP ConfReq id=0x1 <asyncmap 0x0>
<magic 0x89b56df7> <pcomp> <accomp>]
Sep 12 21:36:13 debian pppd[1045]: rcvd [LCP ConfReq id=0x1 <mru 1514> <auth
pap> <magic 0x78f6ad4> <pcomp> <accomp> < 11 04 05 ea> < 13 03 00> <asyncmap
0x0>]
Sep 12 21:36:13 debian pppd[1045]: sent [LCP ConfRej id=0x1 < 11 04 05 ea> <
13 03 00>]
Sep 12 21:36:13 debian pppd[1045]: rcvd [LCP ConfAck id=0x1 <asyncmap 0x0>
<magic 0x89b56df7> <pcomp> <accomp>]
Sep 12 21:36:16 debian pppd[1045]: sent [LCP ConfReq id=0x1 <asyncmap 0x0>
<magic 0x89b56df7> <pcomp> <accomp>]
Sep 12 21:36:43 debian last message repeated 9 times
Sep 12 21:36:45 debian pppd[1045]: Hangup (SIGHUP)
Sep 12 21:36:45 debian pppd[1045]: Modem hangup
Sep 12 21:36:45 debian pppd[1045]: Connection terminated.
Sep 12 21:36:46 debian pppd[1045]: Exit.
</quote>

... could someone enlighten me?

>    Ulrike> If cardinfo detects the pcmcia-card as a modem, why
>    Ulrike> doesn't pppconfig?
>
>Because cardinfo talks to the card directly via the PCMCIA bus.  The
>card responds to "hello, WTF are you?" with "hi, I'm a modem."
>pppconfig scans the serial "devices" (actually high level software
>abstractions) /dev/ttyS*.  For whatever reason, it doesn't recognize
>the response from /dev/ttyS2 as a modem.


Is there anything that can be done about this, or can I forget about using
this modem?

Uli