On Sat, Apr 24, 1999 at 09:42:24AM -0700, Dwight Johnson wrote:

Hello Dwight,

> I am a new user to ISDN, but I have had no trouble connecting to my
> ISP (uswest.net) at 57600KB using a bash script which I wrote and
> execute from my SuSE Linux 5.2 Pentium 133MHz box.
> 
> However, I don't seem to have mastered the technique of connecting at
> the faster speed of 115200KB using both the B channels.
> 
> I am using a 3ComImpactIQ ISDN modem and it is configured correctly
> because I have no trouble connecting at 115200KB when I boot Windows95
> on the same box.
> 
> The 3ComImpactIQ has an autobaud feature which is the default, but
> that does not succeed in connecting the second channel.
> 
> I conclude from this that there must be something required in the
> script to kick in the second channel.

I think the isdnctrl manpage explains it:

       addslave name slave
              Adds  a  slave  interface  named slave to interface
              name for raw channel-bundling. For bundling of more
              than  two  channels,  any  number  of slaves can be
              added to an interface by using this command repeat-
              edly.   name  must  refer  to  an existing "master"
              interface (not a slave). Slave interfaces  are  not
              visible  to the kernel, however all usual ISDN set-
              tings can be configured. Because  slave  interfaces
              are  not visible to the kernel, they are configured
              "through" their "master", so it is  important  that
              slave interfaces are added before the corresponding
              "master" is started by ifconfig.  If  the  "master"
              is  already up, it has to be shutdown with ifconfig
              down ...  otherwise the addslave  command  will  be
              rejected.

> Here is the relevent portion of the script I am trying:

I would recommend using the ipppd instead of the pppd. YaST will
configure this quite nicely for you.

> --
> exec /usr/sbin/pppd debug lock modem crtscts /dev/ttyS0 115200 \
>         asyncmap 0 kdebug 0 $LOCAL_IP:$REMOTE_IP \
>         noipdefault netmask $NETMASK defaultroute \
>   connect "/usr/sbin/chat -v                     \
>         TIMEOUT         3                       \
>         ABORT           '\nBUSY\r'              \
>         ABORT           '\nNO ANSWER\r'         \
>         ABORT           '\nRING\r\n\r\nRING\r'  \
>         ABORT           'NO CARRIER'            \
>         ''              \rAT$B115200            \
>         'OK-+++\c-OK'   ATZ                     \
>         TIMEOUT         30                      \
>         OK              ATDT$TELEPHONE          \
>         CONNECT         '' \
>   sername:    $ACCOUNT                        \
>   assword:    $PASSWORD
>   "
> --
> 
> This script does succeed in connecting to uswest.net, but only on one
> channel.

Maybe that's all you can do with AT-commands. In any case using the
isdn4linux utilities is recommended. They can be picked up at
ftp.suse.com (as well as the latest kernel patches as the ISDN stuff
in the vanilla kernel is pretty much obsolete).

If you need more information I recommend subscribing to
[EMAIL PROTECTED] (at [EMAIL PROTECTED]). The
vger ISDN List is very quiet and you might not get the help you need
here. The franken.de-List is crossmirrored with
de.alt.comm.isdn4linux. It's a German list but threads starting in
English will be continued in English.

Regards,
        Georg

-- 
Georg Wilckens <[EMAIL PROTECTED]>
http://home.t-online.de/home/durandal

Department of Redundancy Department

Reply via email to