Add debug to your /etc/ppp/options file and post the ppp negociation stuff
from your debug syslog file. It will help a lot.
I have a 3com HyperArc and may be able to help you.
At 11:02 PM 1/29/99 , Upshot (link) Mail Relay wrote:
>
>Return-Path: <root>
>Received: (from root@localhost)
> by landreau.ruffe.edu (8.8.7/8.8.7) id XAA01308;
> Fri, 29 Jan 1999 23:22:11 -0500
>Date: Fri, 29 Jan 1999 23:22:11 -0500
>Message-Id: <[EMAIL PROTECTED]>
>From: root <[EMAIL PROTECTED]>
>To: [EMAIL PROTECTED]
>Subject: Intermittant diald connect problems
>X-Mozilla-Status2: 00000000
>
>
>*** Relay-to: [EMAIL PROTECTED] ***
>
>Maybe someone could offer us a little help here. We've been using diald to
>establish a PPP connection to our ISP for the past 2 years. It has worked
>remarkably well. Recently, our ISP made some changes, and now , when we
>dialup our ISP, the dialup server is hooking us up via a different network.
> Along with this we are suddenly having some intermittant problems. Namely
>we have no problem dialing up, we establish a connection, we are
>dynamically assigned an IP #, but we are not always able to send or receive
>anything over the network. Sometimes diald will wind up having to hang up
>and redial one, two three, four, perhaps even an indefinate number of
>times before we can establish a working connection. Other times we can
>successivly establish a working connection with no problem time and time
>again. At first we thought this was due to a problem on the remote end
untill
>last night we found that when we shut down diald, and brought the connection
>up manually using our old ppp-on, ppp-off scripts, we establish a succesfull
>working connection every time. To make it even more confusing I haven't yet
>been able to find any difference as I am using the same options to connect
>manually that I am using to connect via diald.
>
>Below are the logs showing a typical attempt to connect via diald. I did
>notice something interesting that may have to do with the problem. See the
>logs below, I marked off the messages in question with asterisks...
>
>
>
>So far we have dialed in and established a connection to the remote dialup
>server. Now we login and try to make a ppp connection:
>
>Jan 29 22:42:36 landreau chat[1018]: Welcome to 3Com Total Control HiPer
ARC (TM)^M
>Jan 29 22:42:36 landreau chat[1018]: Networks That Go The Distance (TM)^M
>Jan 29 22:42:36 landreau chat[1018]: ^M
>Jan 29 22:42:36 landreau chat[1018]: login:
>Jan 29 22:42:36 landreau chat[1018]: -- got it
>Jan 29 22:42:36 landreau chat[1018]: send (this-guy^M)
>Jan 29 22:42:36 landreau chat[1018]: timeout set to 5 seconds
>Jan 29 22:42:36 landreau chat[1018]: expect (ssword:)
>Jan 29 22:42:36 landreau chat[1018]: this-guy^M
>Jan 29 22:42:36 landreau chat[1018]: Password:
>Jan 29 22:42:36 landreau chat[1018]: -- got it
>Jan 29 22:42:36 landreau chat[1018]: send (this-password^M)
>Jan 29 22:42:36 landreau chat[1018]: timeout set to 25 seconds
>Jan 29 22:42:36 landreau diald[330]: Running pppd (pid = 1019).
>Jan 29 22:42:36 landreau pppd[1019]: pppd 2.3.3 started by root, uid 0
>Jan 29 22:42:36 landreau pppd[1019]: Using interface ppp0
>Jan 29 22:42:36 landreau pppd[1019]: Connect: ppp0 <--> /dev/ttyS1
>Jan 29 22:42:40 landreau pppd[1019]: local IP address 140.186.252.46
>Jan 29 22:42:40 landreau pppd[1019]: remote IP address 140.186.252.3
>
>*************
>
>Jan 29 22:42:40 landreau diald[330]: New addresses: local 140.186.252.46,
remote 140.186.252.3.
>Jan 29 22:42:43 landreau diald[330]: PPP network layer died, but link did
not. Probable configuration error.
>
>***************
>
>** Here it is saying that the network layer died. How/why might this
happen?? It appears that it is trying to tell me that the problem is most
likely due
>to some sort of config error. Yet this does not always happen and I do not
>always get this message. What configuaration boo boo could cause this to
>happen?? In the end this connection wound up working. Such is not always the
>case.
>
>The remaining messages follow...
>
>*******
>
>Jan 29 22:42:43 landreau pppd[1019]: local IP address 140.186.252.46
>Jan 29 22:42:43 landreau pppd[1019]: remote IP address 140.186.252.3
>Jan 29 22:42:43 landreau diald[330]: New addresses: local 140.186.252.46,
remote 140.186.252.3.
>Jan 29 22:43:01 landreau identd[1085]: from: 127.0.0.1 (
landreau.ruffe.edu ) for: 1051, 25
>
>
>Any possible hints, ideas, etc would be really apreciated. In addition, I
list
>my config settings that I am using in /etc/diald.conf below. All other
>diald files are standard and unmodified.
>
>Sincerely,
>
>/Al. Dokes <[EMAIL PROTECTED]>
>
>-----------------------------------------------------
>
>#mode option, tells diald which protocol to use
>mode ppp
># connect option.
>connect /usr/sbin/connecter
># Specify the device used for the remote connection
>device /dev/ttyS1
># Specify the speed at which the modem should be connected
>speed 38400
># Specifies the type of device that is on the serial line
># i.e. modem
>modem
># lock option
># Tells diald to perform locking to prevent other programs from
># using the modem
>lock
># crtscts option
># tells diald that it should use the hardware flow control lines for the
># serial device.
>crtscts
># local option
># Specifies the local ip adress
># Note - An initial local address must still be supplied, even if you
># are using dynamic IP addressing. This is required in order for diald to
># be able to fake a connection before one has actually been made.
># In this case the initial local address should be picked from one of the
># unroutable sbnets that have been set aside for use as private IP numbers.
>local 192.168.0.1
># remote option
># Specifies the address for the machine at the remote end of your link
>remote 140.186.252.3
># dynamic option
># Tells diald that dynamic ip addressing is being used
>dynamic
># defaultroute option
># Tells diald to install a default route in the routing table that goes
># through the link that it is controlling.
>defaultroute
># Tells diald where to find the filter file which specifies the rule to use
># in bringing the link up or down
>include /usr/lib/diald/standard.filter
># path-bootpc option
># Tells diald the path to find bootpc
>#path-bootpc /sbin/bootpc
># Accounting Log.
># Tells diald where to store the accounting log
>accounting-log /mnt/temp/acct.log
>
>
>
>
>
>
>
>
>
------------------------------------------------------------------
Stan A. Rogge (Systems Analyst) mailto:[EMAIL PROTECTED]
Harmonic Systems Incorporated
701 Fourth Avenue South, Suite 320,Minneapolis MN 55415
Telephone:(612)321-4060 Fax:(612)672-3549
http://www.telsarpc.harmonic.com
ftp://telsarpc.harmonic.com
-
To unsubscribe from this list: send the line "unsubscribe linux-diald" in
the body of a message to [EMAIL PROTECTED]
