Skip Navigation
Site HomeSearch

On-Line Reference:
RedHat Linux Unleashed

Did this help?
... or
Donate at PayPal®...

 
Tux the Pengin

OK, here's a freebie: A simulation of the old text-based Star Trek game we used to play on HP 2100's using a Teletype ASR-33 as a console: StarTrek Game

Connecting With PPP

Linux without a Web connection is excruciatingly dreary. It took a bit of searching, but I finally got web-connected using a procedure supplied via the comp.os.linux.powerpc news group by John S Jacobs Anderson.

Here is an expanded version (log in as root):

Get your specific modem init string.

  1. At your command line, type xterm to begin a terminal session.
  2. When the new xterm window opens, type control-panel
  3. Click the Network Configurator icon (fifth from the top).
    • Alternatively you can type the command netcfg to go directly
      into the network configurator from the command line.
  4. Under "Names" enter your ISP???s domain and DNS numbers
  5. Under "Interfaces", click Add to edit a PPP-type session:
    • in the ppp editor, use hardware handshaking, and set the speed to 57600. Set the modem port to /dev/modem (or /dev/ttyS0 in R5).
    • under "Communication" set the modem information. For a factory G3 Global Village 56K internal I used AT&F1E0W2S95=44S0=0&D3S7=60 for the init.
    • enter your ISP's phone number
    • your chat dialog should look like this:
      EXPECT     SEND
      ogin:      id
      ord:       pw
      TIMEOUT    5
      ~--
      
    • If your ISP uses "passive" PPP (no "Login:" or "Password:), then use this chat setup (do not actually type "", just leave empty):
      EXPECT     SEND
      TIMEOUT    1
           id
      TIMEOUT    1
           pw
      TIMEOUT    5
      ~--
      
    • click "DONE" to exit the PPP editor
  6. Your PPP interface should appear in the list of interfaces.
  7. Save and Quit the Network Configurator.
  8. In LinuxPPC R4, create a symbolic link using
    ln -s /dev/ttyS0 /dev/modem (not required in R5, when device = /dev/ttyS0)
  9. To prevent inconsequential but annoying PPP errors when logging in, add the following to your /etc/conf.modules file (create it if it does not exist):
    alias ppp-compress-21 bsd_comp
    alias ppp-compress-24 ppp_deflate
    alias ppp-compress-26 ppp_deflate

To make a connection with netcfg:

Long version: at the shell command line, type netcfg &. Under "Interfaces", select your PPP interface and activate. It should dial up and connect by the time you can iconify the Network Configurator to get it out of the way and launch Netscape with netscape & (the "&" runs the application in the background, freeing the shell terminal for further use.)

Short version: at the command line, type ifup ppp0 or whatever you named your interface; to log off, type ifdown ppp0. (your $PATH must include an entry for /sbin)

Type "tail -f /var/log/messages &" to see a running account of your login in the shell terminal window.

PPP-related Files:

/etc/ppp/resolv.conf
IP addresses of your nameservers.
/etc/ppp/pap-secrets
This one has your on-line user id and password.
/etc/ppp/options
This one just has "lock" in it.
/etc/sysconfig/network-scripts/ifcfg-ppp0
Contains all the modem control settings, like the init string, etc.
/etc/wvdial.conf
Dialing and more modem control stuff.
Gnome "Modem Lights"
If you want to use the Gnome "modem lights" applet, set the login commands to /sbin/ifup ppp0 and /sbin/ifdown ppp0, and under the "Advanced" tab, set the lock file to /var/lock/LCK..modem (the default) or whatever corresponds to what you entered in the netcfg "modem device" block. I had to change this to /var/lock/LCK..ttyS0.
Modem init strings:
Most problems with setting up ppp can be traced to use of an inappropriate init string. Strings for a large number of modems can be found at http://www.west.net/~jay/modem/.
Slow PPP, Netscape "stalled.."
It is possible, if you have two ppp interfaces defined, to get them both going at once. That's so you can use two modems at once. Most of us only have one modem, though, and the poor little guy can not handle two ppps. When this happens, sometimes it may be impossible using the ifdown command to shut them both down. To find out if this is your problem, do # ifconfig to see if you have more thatn one interface "UP". If you do, first force them both down using # ifconfig ppp0 down and # ifconfig ppp1 down, for example for interfaces ppp0 and ppp1. Then you can use the normal ifup ppp0 to bring up the one you want to use.

Print plain