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
dwj@aaronsrod.com
On Sun, 15 Oct 2000, Shaji N V wrote:
> The scripts are here:
> I have changed my login/password
>
> /etc/chatscripts/provider
> ABORT BUSY
> ABORT "NO CARRIER"
> ABORT VOICE
> 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.
>
Reply to: