Hi,
on 5/5/00 9:27 am, [EMAIL PROTECTED] at [EMAIL PROTECTED]
wrote:
> Another thing to watch out for: my ISDN TA by default does some automatic
> PAP/CHAP conversion magic, presumably to help a lesser OS that can't handle
> CHAP; as a result my linux box would fail to connect to BT Internet (a
> British ISP, which requires CHAP) until I disabled this feature.
>
> I have a ZyXel Omni.net Plus ISDN TA, I don't know if this feature is
> standard for other TAs?
I've been using an ISDN TA with my BT ISDN line for 2.5 years now and it
works pretty much the same as an ordinary modem. The TA is BT's badged
Motorola Bitsurfer Pro which does not (by default at least) do PAP/CHAP
authentication.
>
> -----Original Message-----
> From: Hoo Kok Mun [mailto:[EMAIL PROTECTED]]
> Sent: Thursday, May 04, 2000 5:34 PM
> To: [EMAIL PROTECTED]
> Subject: Upgrade to ISDN
>
... much snipped out here ...
> May 4 21:20:39 mail chat[600]: timeout set to 60 seconds
> May 4 21:20:39 mail chat[600]: abort on (ERROR)
> May 4 21:20:39 mail chat[600]: abort on (BUSY)
> May 4 21:20:39 mail chat[600]: abort on (NO CARRIER)
> May 4 21:20:39 mail chat[600]: abort on (NO DIALTONE)
> May 4 21:20:39 mail chat[600]: send (AT&FH0^M)
> May 4 21:20:39 mail chat[600]: expect (OK)
> May 4 21:20:39 mail chat[600]: AT&FH0^M^M
> May 4 21:20:39 mail chat[600]: OK
> May 4 21:20:39 mail chat[600]: -- got it
> May 4 21:20:39 mail chat[600]: send (atdtXXXXXXXX^M)
> May 4 21:20:39 mail chat[600]: timeout set to 75 seconds
> May 4 21:20:39 mail chat[600]: expect (CONNECT)
> May 4 21:20:39 mail chat[600]: ^M
> May 4 21:20:41 mail chat[600]: atdtxxxxxxxx^M^M
> May 4 21:20:41 mail chat[600]: CONNECT
> May 4 21:20:41 mail chat[600]: -- got it
> May 4 21:20:41 mail chat[600]: send (ogin:^M)
> May 4 21:20:41 mail chat[600]: expect (myusername)
> May 4 21:20:41 mail chat[600]: 115200^M
>
> Any clue?
>
> Thanks in advance...
>
Since chat is failing to connect I suggest that you try manually connecting
to the ISP using your favourite terminal emulator. With my TA, I originally
had a lot of problems with connection because, using dialstrings supplied by
the PC (actually a Mac) vendor the TA ended up in a mode that was
incompatible with the service. Resetting the TA with AT&F was all that was
needed.
Once you can log on manually diald should work.
Iain
-
To unsubscribe from this list: send the line "unsubscribe linux-diald" in
the body of a message to [EMAIL PROTECTED]
