Conference nlfdc::linux-users

    pppd and x-windows/network configuration ?
    
    I'm running Red Hat Linux 4.0
    
    As a new linux user, I like x-windows. I would like to use the network
    configurator under X. Would like to setup ppp0 for eras connection to
    DEC and ppp1 to my local provider. I have not had ppp working yet at
    all. I'm I jumping in to far with X ? Should I get it working first
    with pppd and chat ?
    
    I have tried several offering from the LDP and other users with no luck
    yet. Best I can get is a LCP timeout reading config request.
    
    If I try ppp thru X just get an error connect script failed. I have 
    /etc/ppp/options set, but with no connect line(not sure what to put
    here). I know I have left out lots of info for anyone to try and help,
    but some sugestions would be greatly appreciated, and I will get
    details as required. I like the idea of Linux, but it sure is hard for
    a newbie to get moving.
    
    If any one has the time and patients to give me a call that would be 
    great too.
    
    Dave 621-4575

    re: .14
    
    I'm not really an expert in the ppp end of things, but after fiddling
    for quite a while, I managed to get the following to connect to our
    Digital terminal servers using pppd and chat under Red Hat 3.0.3:
    
    ######### /usr/local/bin/cppp
    pppd /dev/cua1 38400 connect \
       "chat -f /usr/local/bin/chatit < /dev/modem > /dev/modem" \
       debug crtscts modem defaultroute \
       netmask 255.255.255.0
    
    ######### /usr/local/bin/chatit
            TIMEOUT 5
            "" "ATZ"
            "OK" "AT&c1&k3"
            ABORT BUSY ABORT "NO CARRIER" ABORT ERROR ABORT "NO DIALTONE"
            "OK" "ATDT8509155" TIMEOUT 75 "CONNECT" "\c"
            TIMEOUT 4
            "#--#--#--#-\k\d-#--#-\k\d-#--#" "" "#" "latpasswordhere"
            "sername" "R" "ocal" "C PPP"
    
    Just typing "cppp" dials the phone and connects me via PPP to the
    office.
    
    It may not be exactly what you're looking for, but maybe it will get
    you started.  FWIW, getting this to work was one of the more time-
    consuming tasks I've had since I've switched to Linux.  But, even then,
    it wasn't that bad...
    
    -- Russ

    Ok, here comes my Linux ignorance !
    
    I tried the example listed in .15
    
    I keep getting "error in connect script"
    
    So I tried running chatit to see what would happen.
    
    Almost every line I get an error.
    
    First line says something like /usr/local/bin/chatit is a directory
    next line OK is not a recognized command
    every line in the chat script has an error of some sort.
    
    So, did I do something wrong when I created this file.
    
    I used Emac from X. Type in as per the example then saved the buffer 
    as /usr/local/bin/chatit. Should I do something to tell linux the
    difference between a file & a directory ?
    
    I now realize all my other attemps have given me a connect script
    error. 
    
    Dave

    re: .15
    
    What do you mean when you say:
    >I tried running chatit to see what would happen.
    
    Did you type:
    	chat -f /usr/local/bin/chatit < /dev/modem > /dev/modem
    
    'chatit' is a command sequence that is used by 'chat'.  It should only be
    executed in the command line above.
    
    Two experiments:
    
    1.  Does the command:
    
    		cat /usr/local/bin/chatit
    
        return a copy of the commands shown in .15, or does it say
    	"/usr/local/bin/chatit:  Is a directory"?
    
    2.  What does this look like:
    
    		ls -alF /dev/modem
    
    -- Russ

    cat/usr/local/bin/chait
    
    does show the commands in .15 starting at 
    TIMEOUT 5
    
    ls -alF /dev/modem shows
    
    lrwxrwxrwx root uucp date & time /dev/modem/cua1
    
    I tried a manual process as suggested in some of the doc's.
    
    I kept getting a LCP time out sending config requests.
    
    
    Dave
    

    re: .18
    
    Does it really show the modem as:
    
    	/dev/modem/cua1
    
    ?  My box shows it as:
    
    	/dev/modem -> /dev/cua1
    
    Or, an entry pointing to the device "/dev/cua1".  Try replacing each
    "/dev/modem" in the script with "/dev/cua1" and rerun the script.
    
    -- Russ