Assuming you're using chat to perform the login, change the chat
command from chat -f filename, to chat -v -f filename.  This will generate a
verbose log of chat's actions, logging them to /var/log/messages on RH 6.0.

        -----Original Message-----
        From:   Keith Morse [SMTP:[EMAIL PROTECTED]]
        Sent:   Tuesday, October 05, 1999 3:45 PM
        To:     [EMAIL PROTECTED]
        Subject:        Daild and RH 6.0, yet again


        Sorry for this.  I've been reading the messages pertaining to this
topic,
        but I'm still stumped and hoping somebody with RedHat experience can
show
        me the error of my ways.  I apologize for the long message.

        Specs: Standard RedHat install, used the default for custom.
External
        modem. /dev/ttyS0 linked to /dev/modem.  AMD K6-II 300 processor, 64
mb
        ram, 1.2 GB hard drive.

                diald-0.99.1-3 with diald-config-0_16_5a-1 installed (rpms)

        Using linuxconf's ppp setup correctly sets up the ppp link. I'll get
a
        ppp0 with the appropriate ip info.  Likewise netstat -rn shows the
proper
        route.  I can move traffic across the link.


        Using diald I cannot make a link.  I've built the tap* devices as
        specified in the ethertap documentation for the kernel.  I insmoded
the
        ethertap driver also.  I modified the connect script (the default
one from
        the rpm) to update the username/password combination.  Diald.conf
has not
        been modified except to put in debug commands.
         
        crw-r--r--   1 root     root      36,  16 Oct  5 10:43 /dev/tap0
        crw-r--r--   1 root     root      36,  17 Oct  5 10:43 /dev/tap1
        and so on. I created 16 devices


        Starting diald with /etc/rc.d/init.d/diald start I get the following
from 
        /var/log/messages:

        Oct  5 11:28:34 gateway diald[1921]: Unknown option 'up-delay'
        Oct  5 11:28:34 gateway diald: diald startup succeeded
        Oct  5 11:28:34 gateway diald[1922]: start tap0: SIOCSIFMETRIC:
Operation
        not supported 


        From following discussions Mike Jagdis has had with other persons,
the 
        "SIOCSIFMETRIC: Operation not supported" is trivial and not worth
worrying
        about.


        Oct  5 11:33:30 gateway diald[1922]: Trigger: udp
10.0.0.1/1034
                        192.203.230.10/53   
        Oct  5 11:33:30 gateway diald[1922]: Calling site 10.0.0.2 
        Oct  5 11:33:31 gateway connect: Initializing Modem
        Oct  5 11:33:32 gateway connect: Dialing 9,556-2194
        Oct  5 11:33:52 gateway connect: chat:  Oct 05 11:33:52 CONNECT
                        33600/ARQ/V34/LAPM/V42BIS
        Oct  5 11:33:52 gateway diald[1922]: Connected to site 10..0.0.2 
        Oct  5 11:33:52 gateway diald[1922]: Running pppd (pid = 1940).
        Oct  5 11:33:52 gateway connect: Protocol started
        Oct  5 11:33:52 gateway pppd[1940]: pppd 2.3.7 started by root, uid
0
        Oct  5 11:33:52 gateway pppd[1940]: Using interface ppp0
        Oct  5 11:33:52 gateway pppd[1940]: Connect: ppp0 <--> /dev/ttyS0
        Oct  5 11:34:51 gateway diald[1922]: pppd startup timed out. Check
your
                        pppd options. Killing pppd.
        Oct  5 11:34:51 gateway diald[1922]: start tap0: SIOCSIFMETRIC:
Operation
                        not supported 
        Oct  5 11:34:51 gateway diald[1922]: start tap0: SIOCADDRT: File
exists 
        Oct  5 11:34:51 gateway diald[1922]: start tap0: SIOCADDRT: File
exists 
        Oct  5 11:34:51 gateway diald[1922]: stop ppp0: SIOCDELRT: No such
process 
        Oct  5 11:34:51 gateway pppd[1940]: Terminating on signal 2.
        Oct  5 11:34:51 gateway pppd[1940]: Connection terminated.
        Oct  5 11:34:51 gateway pppd[1940]: Connect time 1.0 minutes.
        Oct  5 11:34:51 gateway pppd[1940]: Exit.
        Oct  5 11:34:51 gateway diald[1922]: start tap0: SIOCSIFMETRIC:
Operation
                        not supported 
        Oct  5 11:34:51 gateway diald[1922]: start tap0: SIOCADDRT: File
exists 
        Oct  5 11:34:51 gateway diald[1922]: start tap0: SIOCADDRT: File
exists 
        Oct  5 11:34:53 gateway diald[1922]: Delaying 10 seconds before
clear to
                        dial.
        Oct  5 11:35:04 gateway diald[1922]: Calling site 10.0.0.2 
        Oct  5 11:35:05 gateway connect: Initializing Modem
        Oct  5 11:35:05 gateway connect: Dialing 9,556-2194


        And it will keep cycling ad infinitum.

        Part of my problem is not being able to the see the output of the
connect
        script.  I believe it is logging in as I can actually login to the
        comminucation servers and see the username displayed on its session
list.

        Looking for any ideas. Thanks


        -
        To unsubscribe from this list: send the line "unsubscribe
linux-diald" in
        the body of a message to [EMAIL PROTECTED]

-
To unsubscribe from this list: send the line "unsubscribe linux-diald" in
the body of a message to [EMAIL PROTECTED]

Reply via email to