Re: PPP session not established correctly
On Sun, 15 Oct 2000, Shaji N V wrote: I have a problem in establishing a PPP session with my ISP. The excerpts from the syslog is here: Oct 15 12:36:43 localhost pppd[364]: pppd 2.3.11 started by user, uid 0 Oct 15 12:36:44 localhost chat[365]: abort on (BUSY) Oct 15 12:36:44 localhost chat[365]: abort on (NO CARRIER) Oct 15 12:36:44 localhost chat[365]: abort on (VOICE) Oct 15 12:36:44 localhost chat[365]: abort on (NO DIALTONE) Oct 15 12:36:44 localhost chat[365]: timeout set to 120 seconds Oct 15 12:36:44 localhost chat[365]: send (ATDT2022508111^M) Oct 15 12:36:44 localhost chat[365]: expect (ogin) Oct 15 12:37:33 localhost chat[365]: ATDT2022508111^M^M Oct 15 12:37:33 localhost chat[365]: CONNECT 48000 V42bis^M Oct 15 12:37:43 localhost chat[365]: ^M Oct 15 12:37:43 localhost chat[365]: Oct 15 12:37:43 localhost last message repeated 23 times Oct 15 12:38:03 localhost chat[365]: ** Ascend TNT1.LNHDC.MD.RCN.NET Terminal Server **^M Oct 15 12:38:03 localhost chat[365]: ^M Oct 15 12:38:03 localhost chat[365]: ^M Oct 15 12:38:03 localhost chat[365]: Login Oct 15 12:38:03 localhost chat[365]: -- got it Oct 15 12:38:03 localhost chat[365]: send (x^M) Oct 15 12:38:03 localhost chat[365]: expect (word) Oct 15 12:38:23 localhost chat[365]: : x^M Oct 15 12:38:23 localhost chat[365]: Password Oct 15 12:38:23 localhost chat[365]: -- got it Oct 15 12:38:23 localhost chat[365]: send (??) Oct 15 12:38:23 localhost chat[365]: expect (1006) Oct 15 12:38:43 localhost chat[365]: : ^M Oct 15 12:38:53 localhost chat[365]: Entering PPP Session.^M Oct 15 12:39:03 localhost chat[365]: IP address is 208.58.212.82^M Oct 15 12:39:13 localhost chat[365]: MTU is 1006 Oct 15 12:39:13 localhost chat[365]: -- got it Oct 15 12:39:13 localhost chat[365]: send (^M) Oct 15 12:39:13 localhost pppd[364]: Serial connection established. Oct 15 12:39:23 localhost pppd[364]: Using interface ppp0 Oct 15 12:39:23 localhost pppd[364]: Connect: ppp0 -- /dev/ttyS4 Oct 15 12:39:24 localhost pppd[364]: sent [LCP ConfReq id=0x1 asyncmap 0x0 magic 0xc17ec9d3 pcomp accomp] Oct 15 12:39:51 localhost last message repeated 9 times Oct 15 12:39:54 localhost pppd[364]: LCP: timeout sending Config-Requests Oct 15 12:39:54 localhost pppd[364]: Connection terminated. Oct 15 12:40:09 localhost pppd[364]: Terminating on signal 2. Oct 15 12:40:09 localhost pppd[364]: Exit. Your ISP is not responding to your configuration requests and is not sending his own. It looks like your chat script is not set up correctly. What program exactly are you using to make your connection? Is it pon, wvdial or a homebrew bash script? Send the list the actual chat and ppp options lists that you are using. Most ISPs are using PAP authentication, but your chat session is sending the username and password. This method went out of favor several years ago. Try making a manual connection using minicom to learn the details of how your ISP authenticates and starts the ppp session. See the PPP HOWTO for details of how to do this. Dwight -- Dwight Johnson [EMAIL PROTECTED]
Re: PPP session not established correctly
From: Dwight Johnson [EMAIL PROTECTED] Reply-To: Dwight Johnson [EMAIL PROTECTED] To: Shaji N V [EMAIL PROTECTED] CC: debian-user@lists.debian.org Subject: Re: PPP session not established correctly Date: Sun, 15 Oct 2000 11:16:13 -0700 (PDT) On Sun, 15 Oct 2000, Shaji N V wrote: I have a problem in establishing a PPP session with my ISP. The excerpts from the syslog is here: Oct 15 12:36:43 localhost pppd[364]: pppd 2.3.11 started by user, uid 0 Oct 15 12:36:44 localhost chat[365]: abort on (BUSY) Oct 15 12:36:44 localhost chat[365]: abort on (NO CARRIER) Oct 15 12:36:44 localhost chat[365]: abort on (VOICE) Oct 15 12:36:44 localhost chat[365]: abort on (NO DIALTONE) Oct 15 12:36:44 localhost chat[365]: timeout set to 120 seconds Oct 15 12:36:44 localhost chat[365]: send (ATDT2022508111^M) Oct 15 12:36:44 localhost chat[365]: expect (ogin) Oct 15 12:37:33 localhost chat[365]: ATDT2022508111^M^M Oct 15 12:37:33 localhost chat[365]: CONNECT 48000 V42bis^M Oct 15 12:37:43 localhost chat[365]: ^M Oct 15 12:37:43 localhost chat[365]: Oct 15 12:37:43 localhost last message repeated 23 times Oct 15 12:38:03 localhost chat[365]: ** Ascend TNT1.LNHDC.MD.RCN.NET Terminal Server **^M Oct 15 12:38:03 localhost chat[365]: ^M Oct 15 12:38:03 localhost chat[365]: ^M Oct 15 12:38:03 localhost chat[365]: Login Oct 15 12:38:03 localhost chat[365]: -- got it Oct 15 12:38:03 localhost chat[365]: send (x^M) Oct 15 12:38:03 localhost chat[365]: expect (word) Oct 15 12:38:23 localhost chat[365]: : x^M Oct 15 12:38:23 localhost chat[365]: Password Oct 15 12:38:23 localhost chat[365]: -- got it Oct 15 12:38:23 localhost chat[365]: send (??) Oct 15 12:38:23 localhost chat[365]: expect (1006) Oct 15 12:38:43 localhost chat[365]: : ^M Oct 15 12:38:53 localhost chat[365]: Entering PPP Session.^M Oct 15 12:39:03 localhost chat[365]: IP address is 208.58.212.82^M Oct 15 12:39:13 localhost chat[365]: MTU is 1006 Oct 15 12:39:13 localhost chat[365]: -- got it Oct 15 12:39:13 localhost chat[365]: send (^M) Oct 15 12:39:13 localhost pppd[364]: Serial connection established. Oct 15 12:39:23 localhost pppd[364]: Using interface ppp0 Oct 15 12:39:23 localhost pppd[364]: Connect: ppp0 -- /dev/ttyS4 Oct 15 12:39:24 localhost pppd[364]: sent [LCP ConfReq id=0x1 asyncmap 0x0 magic 0xc17ec9d3 pcomp accomp] Oct 15 12:39:51 localhost last message repeated 9 times Oct 15 12:39:54 localhost pppd[364]: LCP: timeout sending Config-Requests Oct 15 12:39:54 localhost pppd[364]: Connection terminated. Oct 15 12:40:09 localhost pppd[364]: Terminating on signal 2. Oct 15 12:40:09 localhost pppd[364]: Exit. Your ISP is not responding to your configuration requests and is not sending his own. It looks like your chat script is not set up correctly. What program exactly are you using to make your connection? Is it pon, wvdial or a homebrew bash script? Send the list the actual chat and ppp options lists that you are using. Most ISPs are using PAP authentication, but your chat session is sending the username and password. This method went out of favor several years ago. Try making a manual connection using minicom to learn the details of how your ISP authenticates and starts the ppp session. See the PPP HOWTO for details of how to do this. Dwight -- Dwight Johnson [EMAIL PROTECTED] Hi, I am using Potato, and using the default scripts in /etc/chatscripts/provider and /etc/ppp/peers/provider with appropriate changes. The only addition to /etc/chatscripts/provider is the lastline 1006. The ISP is starpower.net and they say they are not using PAP/CHAP. Also if you observe the chat session, it says entering PPP session, and assigns an IP address. Is there anything which could be going wrong? Thanks -Shaji _ Get Your Private, Free E-mail from MSN Hotmail at http://www.hotmail.com. Share information about yourself, create your own public profile at http://profiles.msn.com.
Re: PPP session not established correctly
I am using Potato, and using the default scripts in /etc/chatscripts/provider and /etc/ppp/peers/provider with appropriate changes. Run pppconfig as root, answer the questions, and try using 'pon' to connect and 'poff' to disconnect. If you still have trouble post the output of the plog command and copies of /etc/chatscripts/provider and /etc/ppp/peers/provider. -- John Hasler [EMAIL PROTECTED] Dancing Horse Hill Elmwood, Wisconsin
Re: PPP session not established correctly
I suggest deleting the '1006' line from /etc/chatscripts/provider and commenting out 'mtu 1006' from /etc/ppp/peers/provider and then try connecting again. Send the log results to the list. Dwight -- Dwight Johnson [EMAIL PROTECTED] On Sun, 15 Oct 2000, Shaji N V wrote: The scripts are here: I have changed my login/password /etc/chatscripts/provider ABORTBUSY ABORTNO CARRIER ABORTVOICE ABORT NO DIALTONE TIMEOUT 120 ATDT2022508111 ogin mylogin word \qmypassword 1006 /etc/ppp/peers/provider ( I have tried with speeds 57600 and 115200) # These are the options to dial out to your default service provider. # Please customize them correctly. Only the provider file will be # handled by poff and pon (unless with extra command line arguments). # You usually need this if there is no PAP authentication noauth # The chat script (be sure to edit that file, too!) connect /usr/sbin/chat -v -f /etc/chatscripts/provider # Set up routing to go through this PPP link defaultroute # Default modem (you better replace this with /dev/ttySx!) /dev/ttyS4 # Speed 115200 # Keep modem up even if connection fails persist /etc/ppp/options - provided by ISP. # /etc/ppp/options # # Prevent pppd from forking into the background -detach # # use the modem control lines modem # use uucp style locks to ensure exclusive access to the serial device lock # use hardware flow control crtscts # create a default route for this connection in the routing table defaultroute # do NOT set up any escaped control sequences asyncmap 0 # use a maximum transmission packet size of 552 bytes mtu 1006 # use a maximum receive packet size of 552 bytes #mru 552 # # force pppd to use your ISP user name as your 'host name' during the # authentication process #name # # If you are running a PPP *server* and need to force PAP or CHAP # uncomment the appropriate one of the following lines. Do NOT use # these is you are a client connecting to a PPP server (even if it uses PAP # or CHAP) as this tells the SERVER to authenticate itself to your # machine (which almost certainly can't do - and the link will fail). #+chap #+pap # # If you are using ENCRYPTED secrets in the /etc/ppp/pap-secrets # file, then uncomment the following line. # Note: this is NOT the same as using MS encrypted passwords as can be # set up in MS RAS on Windows NT. #+papcrypt # Increase debugging level (same as -d). If this option is given, pppd # will log the contents of all control packets sent or received in a # readable form. The packets are logged through syslog with facility # daemon and level debug. This information can be directed to a file by # setting up /etc/syslog.conf appropriately (see syslog.conf(5)). (If # pppd is compiled with extra debugging enabled, it will log messages # using facility local2 instead of daemon). debug Thanks for your time and help, Shaji _ Get Your Private, Free E-mail from MSN Hotmail at http://www.hotmail.com. Share information about yourself, create your own public profile at http://profiles.msn.com.
Re: PPP session not established correctly
Hi, The problem is resolved, thanks to the FAQ page of the modem manufacturer (Actiontec - well they should have specified that in the printed manual). I had to set some serial parameters to the device using setserial, namely spd_vhi skip_test auto_irq autoconfig. Now the problem is that it occasionally gets disconnected. I will try to figure this out. -Thanks, Shaji From: Dwight Johnson [EMAIL PROTECTED] Reply-To: Dwight Johnson [EMAIL PROTECTED] To: Shaji N V [EMAIL PROTECTED] CC: debian-user@lists.debian.org Subject: Re: PPP session not established correctly Date: Sun, 15 Oct 2000 13:42:31 -0700 (PDT) I suggest deleting the '1006' line from /etc/chatscripts/provider and commenting out 'mtu 1006' from /etc/ppp/peers/provider and then try connecting again. Send the log results to the list. Dwight -- Dwight Johnson [EMAIL PROTECTED] _ Get Your Private, Free E-mail from MSN Hotmail at http://www.hotmail.com. Share information about yourself, create your own public profile at http://profiles.msn.com.
Re: PPP session not established correctly
Shaji N V writes: ...spd_vhi... That FAQ must be pretty old. spd_vhi has been useless for a long time. -- John Hasler [EMAIL PROTECTED] Dancing Horse Hill Elmwood, Wisconsin
Re: PPP session not established correctly
On 15 Oct 2000, John Hasler wrote: Shaji N V writes: ...spd_vhi... That FAQ must be pretty old. spd_vhi has been useless for a long time. Yes, the option '115200' takes care of this setserial in my ppp connection. Dwight -- Dwight Johnson [EMAIL PROTECTED]
