Re: PPP Connection through ISDN Line

From: Edouard Soriano (e_soriano@dapsys.ch)
Date: Mon Jan 31 2000 - 03:50:42 EST


That's what I get when using kdebug 7 or kdebug 9 on ppp.opt:

Jan 31 09:34:44 dap50 chat[16957]: CONNECT 38400^M
Jan 31 09:34:44 dap50 chat[16957]: ^M
Jan 31 09:34:44 dap50 chat[16957]: ~ -- got it
Jan 31 09:34:45 dap50 kernel: ppp_tty_ioctl: set flags to 90000
Jan 31 09:34:45 dap50 kernel: ppp_tty_ioctl: set flags to 90000
Jan 31 09:34:45 dap50 kernel: ppp_tty_ioctl: set xasyncmap
Jan 31 09:34:45 dap50 kernel: ppp_tty_ioctl: set xmit asyncmap
ffffffff
Jan 31 09:34:45 dap50 pppd[16955]: Using interface ppp0
Jan 31 09:34:45 dap50 pppd[16955]: Connect: ppp0 <--> /dev/ttyC0
Jan 31 09:34:45 dap50 kernel: ppp_tty_ioctl: set flags to 90000
Jan 31 09:34:45 dap50 kernel: ppp_tty_ioctl: set mru to 5dc
Jan 31 09:34:45 dap50 kernel: ppp_tty_ioctl: set rcv asyncmap 0
Jan 31 09:34:45 dap50 kernel: ppp_tty_ioctl: set flags to 90010
Jan 31 09:34:46 dap50 kernel: ppp: successfully queued 34 bytes, flags
= f090010
Jan 31 09:34:46 dap50 kernel: ppp: successfully queued 30 bytes, flags
= f090010
Jan 31 09:34:46 dap50 kernel: ppp: successfully queued 30 bytes, flags
= f090010
Jan 31 09:34:46 dap50 kernel: ppp: successfully queued 27 bytes, flags
= f090010
Jan 31 09:34:47 dap50 kernel: ppp: successfully queued 26 bytes, flags
= f090010
Jan 31 09:34:47 dap50 kernel: ppp: successfully queued 34 bytes, flags
= f090010
Jan 31 09:34:47 dap50 kernel: ppp: successfully queued 30 bytes, flags
= f090010
Jan 31 09:34:47 dap50 last message repeated 3 times
Jan 31 09:34:47 dap50 kernel: ppp: successfully queued 7 bytes, flags
= f090010
Jan 31 09:34:48 dap50 kernel: ppp: successfully queued 10 bytes, flags
= f090010
Jan 31 09:34:49 dap50 kernel: ppp: successfully queued 7 bytes, flags
= f090010
Jan 31 09:34:51 dap50 kernel: ppp: successfully queued 7 bytes, flags
= f090010
Jan 31 09:34:55 dap50 kernel: ppp: channel ppp0 closing.
Jan 31 09:34:55 dap50 pppd[16955]: Hangup (SIGHUP)
Jan 31 09:34:55 dap50 pppd[16955]: Modem hangup
Jan 31 09:34:55 dap50 pppd[16955]: Connection terminated.
Jan 31 09:34:55 dap50 pppd[16955]: Exit.
Jan 31 09:35:45 dap50 syslog: Exit.
Jan 31 09:35:56 dap50 kernel: PPP: ppp line discipline successfully
unregistered
Jan 31 09:36:17 dap50 syslog: Exit.

But still pas de connection (no connexion)

I checked the other side using Window$ PPP client connection. I am
sorry about. It worked,
so we can assume that this server configuration was in order at the
time the Linux
test was done.

According with pppd documentation, kdebug 7 means general information
as well as incoming and
outgoing packets to be printed. Having no packets out on the log file,
I assume this problem
occurs before the pp connection reach the IP level.

Furthermore, I started tcpdump listening on ppp0 device when the first
 successfully queued data
was sent over the log file. No messages were captured by tcpdump.

Any idea about next step ?

Regards

>>>>>>>>>>>>>>>>>> Message d'origine <<<<<<<<<<<<<<<<<<

Le 1/28/00, à 7:07:12 PM h, "Mikkel L. Ellertson" <mikkel@execpc.com>
vous a écrit sur le sujet suivant Re: PPP Connection through ISDN Line:

At 05:48 PM 1/28/00 GMT, you wrote: >>>>

Hello Mikkel,

Thanks for your help. I tried your suggestion, and I feel we are a
stepforward, but still unable to connect this @!!?^~&raquo;# server.

These is my documentation related with this question.

Is there a way to trace the trafic after Connect: ppp0 <-->
/dev/ttyC0???

pppu command

/usr/sbin/pppd file ppp.opt +chap +pap -d $Dvc $Spd

ppp.opt

connect /tmp/ppp.chat

debug

crtscts

modem

ipcp-accept-local

ipcp-accept-remote

lock

ppp.chat

/usr/sbin/chat -v ABORT BUSY ABORT 'NO ANSWER' ABORT 'NO CARRIER'\

'' 'ATZ' 'OK' 'AT&FZE0X8' 'OK' 'ATV1&D2&C1S0=0' 'OK' \

'AT&L1S38.3=1S48.2=1' 'OK' 'ATS84.4=1S118.3=1' 'OK' \

'ATCN<0>' 'OK' 'ATCI<00>' 'OK' \

'ATS7=60S50=0L4M1&K3*E0&K00&H3B0' 'OK' \

'ATDIxxxxxxxxxxxxx' '~'

/etc/ppp/pap-secrets and /etc/ppp/chap-secrets

# Secrets for authentication using PAP

# client server secret IP addresses

MyUserIdOnTheOtherSide * MyPasswordOnTheOtherSide

Add kdebug 7 to you options. It will give you a VERY detailedlog

of what is going on. It is probably an authorization problem.

You can also try adding the option papname=MyUserIdOnTheOtherSide

to your options file.

You can set the kdebug level lower to get less detail. Play with

it to get the amount of detail you want.

Mikkel

---

I Haven't Lost My Mind,

It's Backed Up On Disk Somewhere...

- To unsubscribe from this list: send the line "unsubscribe linux-net" in the body of a message to majordomo@vger.rutgers.edu



This archive was generated by hypermail 2b29 : Mon Jan 31 2000 - 21:00:34 EST