BT Speedway - it's driving me barmy - Thread - go-pugleaf

Thread View: demon.tech.unix

4 messages

[T] Back to Threads [V] Tree View [G] Group Articles

4 total messages Started by Tom Bird Wed, 03 May 2000 00:00

BT Speedway - it's driving me barmy

#393

Author: Tom Bird
Date: Wed, 03 May 2000 00:00

26 lines
1675 bytes

I bought a BT Speedway PCI ISDN card to run with Home Highway because I
knew it was Linux compatible.

Having got the beast home and compiled the appropriate bits into my
kernel (2.2.14 as supplied with Red Hat 6.2), the card was recognised
and it logs in /var/log/messages whenever there is an incoming call.  I
compiled it as "Fritz PCI/PnP" IIRC.  I also compiled in synchronous PPP
and the other stuff it told me to.

I can't get the bloody thing to negotiate properly with an ISP, I tested
it in windoze and it works perfectly, very fast and nice.  When I try it
in minicom (pointing to /dev/ttyI0) and set it up with at&e0 for the MSN
(as BT recommend for Home Highway) and then do atdxxx where xxx is the
number of an ISP (I have tried several) it just comes up "NO CARRIER".
I set it to HDLC for the layer 2 protocol and "trans" for the layer 3
protocol (IIRC again) and this time it goes "CONNECT 64000/HDLC" but
within a few seconds it disconnects with "NO CARRIER".

I have tested all the features of the card in windoze on the same
machine with it in the same slot and there is nothing wrong with either
the card or the machine.

In other words - HELP!

TIA,
TB               Busby the Cat 1984 - 22.9.1999

Re: BT Speedway - it's driving me barmy

#426

Author: Paul Civati
Date: Sun, 14 May 2000 00:00

11 lines
899 bytes

In article <wUlFOCAP82D5EwiX@btinternet.com>,
	Tom Bird <hamster@nospam.demon.co.uk> writes:

> I set it to HDLC for the layer 2 protocol and "trans" for the layer 3
> protocol (IIRC again) and this time it goes "CONNECT 64000/HDLC" but
> within a few seconds it disconnects with "NO CARRIER".

I can't solve your problem but I do know that HDLC encapsulation is
NOT what you want to be using, it needs to be PPP.

-Paul-

Re: BT Speedway - it's driving me barmy

#427

Author: Paul Black
Date: Sun, 14 May 2000 00:00

33 lines
1803 bytes

paul@xciv.org (Paul Civati) wrote:
> 
> In article <wUlFOCAP82D5EwiX@btinternet.com>,
>         Tom Bird <hamster@nospam.demon.co.uk> writes:
> 
> > I set it to HDLC for the layer 2 protocol and "trans" for the layer 3
> > protocol (IIRC again) and this time it goes "CONNECT 64000/HDLC" but
> > within a few seconds it disconnects with "NO CARRIER".
> 
> I can't solve your problem but I do know that HDLC encapsulation is
> NOT what you want to be using, it needs to be PPP.

Why not? It works for me.

Tom, you might want to try the following:
isdnctrl verbose 3 
isdnctrl system on
isdnctrl addif ippp0
isdnctrl addphone ippp0 out 08450798667
isdnctrl eaz ippp0 <your number>
isdnctrl huptimeout ippp0 360
isdnctrl l2_prot ippp0 hdlc
isdnctrl l3_prot ippp0 trans
isdnctrl encap ippp0 syncppp
isdnctrl secure ippp0 on
isdnctrl pppbind ippp0 0

and use "isdnctrl dial ippp0" for connecting and "isdnctrl hangup
ippp0" for disconnecting.

Let me know if you need any help with the ipppd side of things.

Paul

Re: BT Speedway - it's driving me barmy

#432

Author: Tom Bird
Date: Mon, 15 May 2000 00:00

19 lines
1259 bytes

In article <8fm4mt$llt$1@vantage.xciv.org>, Paul Civati <paul@xciv.org>
writes
>In article <wUlFOCAP82D5EwiX@btinternet.com>,
>       Tom Bird <hamster@nospam.demon.co.uk> writes:
>
>> I set it to HDLC for the layer 2 protocol and "trans" for the layer 3
>> protocol (IIRC again) and this time it goes "CONNECT 64000/HDLC" but
>> within a few seconds it disconnects with "NO CARRIER".
>
>I can't solve your problem but I do know that HDLC encapsulation is
>NOT what you want to be using, it needs to be PPP.

Nah, I sorted it manually thanks - there was a dodgy defaults file
messing with my settings.

Re HDLC - it is needed - TCP/IP over SyncPPP over HDLC over ISDN is how
it goes.

TB               Busby the Cat 1984 - 22.9.1999

Thread Navigation

This is a paginated view of messages in the thread with full content displayed inline.

Messages are displayed in chronological order, with the original post highlighted in green.

Use pagination controls to navigate through all messages in large threads.

Back to All Threads