- INDEX
- HP-UX Index
- Solaris
- Linux Index
- Other Unix types
- General Unix
- Unix Networking
- Unix Scripts
- Unix Databases

Associated Information

- Rebuilding the Kernel

Useful Links

PPP-Client

1. kernel: PPP is best set up as a kernel module. If you haven't got PPP loaded as a module, check Rebuilding the kernel for details of adding a kernel module.

2. As of the 2.2 version of the kernel, the kernel automatically loads modules using the /sbin/modprobe command. If it doesn't load , /sbin/insmod> can be used to manually load the module. (lsmod lists the modules loaded).

3. FOR LAPTOPS ONLY: Problems with modems can be due due to pcmcia not being installed or configured correctly. See the PCMCIA-HOWTO in /usr/doc/HOWTOS for details. A daemon called cardmgr should be running. This is controlled by /etc/sysconfig/pcmcia which should have the parameter PCMCIA=yes set. Various config files are found in /etc/pcmcia. If you have trouble with settings, do the following:
   1. Devices are defined as follows:

      -	input	output
      com1	/dev/ttyS0	/dev/cua0
      com2	/dev/ttyS1	/dev/cua1
      com3	/dev/ttyS2	/dev/cua2
      com4	/dev/ttyS3	/dev/cua3

   2. Check device using command setserial -a /dev/ttySx . This will show settings.
   3. to exclude an IRQ if you suspect an IRQ clash, edit /etc/pcmcia/config.opts and add line
      exclude irq "number"
   4. To limit the range to IRQs selectable, edit /etc/pcmcia/config ad follows:
      device "serail_cs"
      class "serial" module "serial_cs" opts "irq_list=5,7,9"
      
   5. The following modules should be loaded (check with lsmod)
      serial_cs 1 0
      ds 2 [serial_cs] 3
      i82365(*) 4 2
      pcmcia-core 8 [serial_cs ds i82365] 4
      *i82365 can be replaced by a different pcmcia controller depending on the hardware.See PCMCIA-HOWTO and SERIAL-HOWTO for details.

4. PPP configuration follows:
   1. Edit /etc/group and add a ppp group with a unique gid number. Add any users to the group that may be required.
   2. ensure /sbin/pped is owned by root, group ppp and the suid bit is on as follows:
      1. chown root /usr/sbin/ppd
      2. ghgrp ppp /usr/sbin/ppd
      3. chmod u+s /usr/sbin/pppd
   3. copy ppp-on and ppp-off from /usr/doc/ppp-version/scripts to /usr/sbin
   4. chown root /usr/sbin/ppp-on (and ppp-off)
      chgrp ppp /usr/sbin/ppp-on (and ppp-off)
      chmod 550 /usr/sbin/ppp-on (and ppp-off)
      
   5. copy ppp-on-dialer script from /usr/doc/ppp-version/scripts to /etc/ppp and set the permissions the same as ppp-on
   6. Edit the ppp-on script setting:
      TELEPHONE=telephone number
      ACCOUNT=ppp-account
      PASSWORD=current password
      on the exec /usr/sbin/ppd line, set the device to the correct dial out device
   7. Edit /etc/ppp/options file so that it contains:
      lock
      modem
      -detach
      crtscts
      defaultroute
      asyncmap 0
      mtu 552
      mru 552
      (some of these aren't required as they are specofoed on the command line ppp-on script. However, if this line is cahnged, the correct options will still be picked up).
   8. Add any local & remote IP addresses in /etc/hosts (This isn't required for connecting to an ISP)

   The client should now be configured.

   NOTE: modem testing can be done via the minicom program.

   For more details on the above, see the PPP-HOWTO

PPP Server

1. Set up the kernel as per the client.

2. Configure PPP as follows:
   1. Add a user called ppp (or whatever desired) into /etc/passwd as follows:

      ppp:password:uid:gid:PPP Client login:/home/ppp:/isr/sbin/pppd

   2. Create a ppp group as per client (ppp user should be in this group)
   3. Create the home directory, owned by ppp, group ppp
   4. Create .ppprc in this home directory with contents as follows:
      -detach
      modem
      crtscts
      lock
      :ipaddress-assigned-to-remote-user
   5. Set permissions for this file to root:ppp 444
   6. Ensure pppd is owned by root, group ppp, setuid bit on (as per client)

   See /usr/doc/ppp-version/README_linux for details

3. configure getty as follows:
   1. vi /etc/conf.uugetty and ensure the following is included:
      ATLOCK=cuax (where x is the correct output device the modem is attached to)
      TIMEOUT=60
      INIT="" \d+++\dAT\r OK etc....
      WAITFOR=RING
      CONNECT="" ATA \r CONNECT\s\A
      DELAY=1

      This can be copied from template file /usr/doc/getty-version/Examples/default/uugetty.autoanswer and edited to add WAITFOR and CONNECT statements.

   2. edit /etc/inittab to add statement:

      s1:2345:respawn:/sbin/uugetty -d /etc/conf.uugetty ttySx F115200 vt100

   3. run init q and check uugetty is running with ps ax command. (See Serial-HOWTO for details).

4. To get connection up:
   1. On the client execute ppp-on &
   2. Once the connection is made, check with ifconfig -a a ppp0 entry should be present
   3. can now connect using telnet, ftp, etc...
   4. To stop the connection, run ppp-off