-----Original Message----- From: Jorge Sousa <[EMAIL PROTECTED]> To: [EMAIL PROTECTED] <[EMAIL PROTECTED]> Date: Sexta-feira, 19 de Março de 1999 22:55 Subject: mgetty and Multitech problems again but with log files
>Hi all, > >I'm having problems with my Multitech modem while trying to setup a dialing >server with Debian Linux 2.0. >So far I was not able to configure this modem under linux to act as a >receiver. With NT+RAS works quite well. >I've tested my mgetty configuration against ZOOM and BOCA (both 28800 kbs >externals) without any problems. > >here are one of test done at my job using internal lines (so I don't have >to pay calls). > >Using the ZOOM as a caller and the Multitech as a receiver. > >Here is the ppp,log -------------------------- > >Mar 19 23:12:10 monga pppd[31289]: pppd 2.3.5 started by root, uid 0 >Mar 19 23:12:11 monga chat[31290]: abort on (BUSY) >Mar 19 23:12:11 monga chat[31290]: abort on (NO CARRIER) >Mar 19 23:12:11 monga chat[31290]: abort on (VOICE) >Mar 19 23:12:11 monga chat[31290]: abort on (NO DIALTONE) >Mar 19 23:12:11 monga chat[31290]: abort on (NO ANSWER) >Mar 19 23:12:11 monga chat[31290]: send (ATZ^M) >Mar 19 23:12:11 monga chat[31290]: expect (OK) >Mar 19 23:12:12 monga chat[31290]: ATZ^M^M >Mar 19 23:12:12 monga chat[31290]: OK >Mar 19 23:12:12 monga chat[31290]: -- got it >Mar 19 23:12:12 monga chat[31290]: send (ATDT1518^M) >Mar 19 23:12:12 monga chat[31290]: expect (CONNECT) >Mar 19 23:12:12 monga chat[31290]: ^M >Mar 19 23:12:57 monga chat[31290]: alarm >Mar 19 23:12:57 monga chat[31290]: Failed >Mar 19 23:12:57 monga pppd[31289]: Connect script failed >Mar 19 23:12:58 monga pppd[31289]: Exit. >--------------------------------------------------------------------------- - >--------------- > > >On the dial in server the mg_ttyS1.log got this: -------------------------- >The computer clock was not right > >03/19 22:30:53 yS1 mgetty: experimental test release 1.1.18-Sep11 >03/19 22:30:53 yS1 check for lockfiles >03/19 22:30:53 yS1 locking the line > >--- what does the following two lines mean??? > >03/19 22:30:53 yS1 WARNING: DSR is off - modem turned off or bad cable? >03/19 22:30:53 yS1 lowering DTR to reset Modem >03/19 22:30:54 yS1 send: ATZ[0d] >03/19 22:30:54 yS1 waiting for ``OK'' ** found ** >03/19 22:30:54 yS1 send: [0d] >03/19 22:30:55 yS1 waiting... >03/19 22:33:02 yS1 wfr: waiting for ``RING'' > >--- Here the modem start responding, after a while the modem starts >screaming and then... > >03/19 22:33:12 yS1 mdm_read_byte: read returned -1: Interrupted system call >03/19 22:33:12 yS1 wfr: timeout waiting for RING >03/19 22:33:12 yS1 huh? Junk on the line? >-- >----------------------------------------------------------------- > >As you can see the connection failed. > >I've tried this same Multitech modem with an NT with RAS and works >perfectly. > >Now going back to Linux again this time using the same machines and >configurations but exchanging the modems I got: > >Using the Multitech as a caller and the ZOOM as a receiver. > >I started the connection with: pon test > >Here is the ppp,log -------------------------- >Mar 19 23:15:46 monga pppd[31316]: pppd 2.3.5 started by root, uid 0 >Mar 19 23:15:47 monga chat[31317]: abort on (BUSY) >Mar 19 23:15:47 monga chat[31317]: abort on (NO CARRIER) >Mar 19 23:15:47 monga chat[31317]: abort on (VOICE) >Mar 19 23:15:47 monga chat[31317]: abort on (NO DIALTONE) >Mar 19 23:15:47 monga chat[31317]: abort on (NO ANSWER) >Mar 19 23:15:47 monga chat[31317]: send (ATZ^M) >Mar 19 23:15:47 monga chat[31317]: expect (OK) >Mar 19 23:15:48 monga chat[31317]: ATZ^M^M >Mar 19 23:15:48 monga chat[31317]: OK >Mar 19 23:15:48 monga chat[31317]: -- got it >Mar 19 23:15:48 monga chat[31317]: send (ATDT1518^M) >Mar 19 23:15:48 monga chat[31317]: expect (CONNECT) >Mar 19 23:15:48 monga chat[31317]: ^M >Mar 19 23:16:08 monga chat[31317]: ATDT1518^M^M >Mar 19 23:16:08 monga chat[31317]: CONNECT >Mar 19 23:16:08 monga chat[31317]: -- got it >Mar 19 23:16:08 monga chat[31317]: send (\d) >Mar 19 23:16:09 monga pppd[31316]: Serial connection established. >Mar 19 23:16:10 monga pppd[31316]: Using interface ppp0 >Mar 19 23:16:10 monga pppd[31316]: Connect: ppp0 <--> /dev/ttyS1 >Mar 19 23:16:10 monga pppd[31316]: sent [LCP ConfReq id=0x1 <asyncmap 0x0> ><magic 0x710334c7> <pcomp> <accomp>] >Mar 19 23:16:10 monga pppd[31316]: rcvd [LCP ConfReq id=0x1 <asyncmap 0x0> ><auth pap> <magic 0xffffbc8d> <pcomp> <accomp>] >Mar 19 23:16:10 monga pppd[31316]: sent [LCP ConfAck id=0x1 <asyncmap 0x0> ><auth pap> <magic 0xffffbc8d> <pcomp> <accomp>] >Mar 19 23:16:13 monga pppd[31316]: sent [LCP ConfReq id=0x1 <asyncmap 0x0> ><magic 0x710334c7> <pcomp> <accomp>] >Mar 19 23:16:13 monga pppd[31316]: rcvd [LCP ConfAck id=0x1 <asyncmap 0x0> ><magic 0x710334c7> <pcomp> <accomp>] >Mar 19 23:16:13 monga pppd[31316]: sent [PAP AuthReq id=0x1 user="User1" >password="User1_PWD"] >Mar 19 23:16:13 monga pppd[31316]: rcvd [PAP AuthAck id=0x1 "Success"] >Mar 19 23:16:13 monga pppd[31316]: Remote message: Success >Mar 19 23:16:13 monga pppd[31316]: sent [IPCP ConfReq id=0x1 <addr 0.0.0.0> ><compress VJ 0f 01>] >Mar 19 23:16:13 monga pppd[31316]: sent [CCP ConfReq id=0x1 <bsd v1 15>] >Mar 19 23:16:13 monga pppd[31316]: rcvd [IPCP ConfReq id=0x1 <addr >192.168.100.100> <compress VJ 0f 01>] >Mar 19 23:16:13 monga pppd[31316]: sent [IPCP ConfAck id=0x1 <addr >192.168.100.100> <compress VJ 0f 01>] >Mar 19 23:16:13 monga pppd[31316]: rcvd [CCP ConfReq id=0x1 <bsd v1 15>] >Mar 19 23:16:13 monga pppd[31316]: sent [CCP ConfAck id=0x1 <bsd v1 15>] >Mar 19 23:16:13 monga pppd[31316]: rcvd [IPCP ConfNak id=0x1 <addr >192.168.100.101>] >Mar 19 23:16:13 monga pppd[31316]: sent [IPCP ConfReq id=0x2 <addr >192.168.100.101> <compress VJ 0f 01>] >Mar 19 23:16:13 monga pppd[31316]: rcvd [CCP ConfAck id=0x1 <bsd v1 15>] >Mar 19 23:16:13 monga pppd[31316]: BSD-Compress (15) compression enabled >Mar 19 23:16:14 monga pppd[31316]: rcvd [IPCP ConfAck id=0x2 <addr >192.168.100.101> <compress VJ 0f 01>] >Mar 19 23:16:14 monga pppd[31316]: local IP address 192.168.100.101 >Mar 19 23:16:14 monga pppd[31316]: remote IP address 192.168.100.100 > >Here I finished the session with -> poff > >Mar 19 23:21:17 monga pppd[31316]: Terminating on signal 15. >Mar 19 23:21:17 monga pppd[31316]: sent [LCP TermReq id=0x2 "User request"] >Mar 19 23:21:18 monga pppd[31316]: rcvd [LCP TermAck id=0x2] >Mar 19 23:21:18 monga pppd[31316]: Connection terminated. >Mar 19 23:21:19 monga pppd[31316]: Exit. >----------------------------------------------------- > >On the dial in server the mg_ttyS1.log got this: -------------------------- >The computer clock was not right > >03/19 22:33:12 yS1 mgetty: experimental test release 1.1.18-Sep11 >03/19 22:33:12 yS1 check for lockfiles >03/19 22:33:12 yS1 locking the line >03/19 22:33:13 yS1 WARNING: DCD line still active, check modem settings >(AT&Dx) >03/19 22:33:13 yS1 lowering DTR to reset Modem >03/19 22:33:13 yS1 send: ATZ[0d] >03/19 22:33:13 yS1 waiting for ``OK'' ** found ** >03/19 22:33:14 yS1 send: [0d] >03/19 22:33:15 yS1 waiting... >03/19 22:34:21 yS1 wfr: waiting for ``RING'' >03/19 22:34:21 yS1 send: ATA[0d] >03/19 22:34:21 yS1 waiting for ``CONNECT'' ** found ** >03/19 22:34:35 yS1 send: >03/19 22:34:35 yS1 waiting for ``_'' ** found ** >03/19 22:34:37 ##### data dev=ttyS1, pid=268, caller='none', conn='57600', >name='', cmd='/usr/sbin/pppd', user='/AutoPPP/' >-------------------------------------------------------------------- > >So as you can see I've got a successful connection. > >The mgetty config files are these: >login.config -------- >/AutoPPP/ - a_ppp /usr/sbin/pppd auth -chap +pap login debug -detach >crtscts proxyarp >------------------------- >mgetty.config------------- >debug 4 >fax-id >speed 38400 > >port ttyS1 > data-only y > init-chat "" ATZ OK "" >----------------------------------- > >/etc/inittab ----------------- >T1:23respawn:/sbin/mgetty -D -x4 -s 57600 ttyS1 >---------------------------------------- > >/etc/ppp/options -------------- >asyncmap 0 >------------------------------------- > >/etc/ppp/options.ttyS1 -------------- >dial_server:dial_client # these are set in /etc/hosts as >192.168.100.100:192.168.100.101 >--------------------------------------------- > >Do you identify any problem with theses configurations?? What am I doing >wrong? >I think the Multitech must need aditional configuration parameters. > >Any hint??? > > >Thanks in advance. > > >Jorge Sousa > > > >
