On 28 Apr 98 at 14:19, [EMAIL PROTECTED] wrote:

> >I would like to have my RH5 box configured to use PPP in a 
> >system-friendly (for RH anyway) way.

> Ah, you want the documentation at
> http://www.redhat.com/support/docs/rhl/sysconfig.html

I have read this documentation, but it leaves a bit unsaid, which was 
why I was (and still am) hoping someone would send me suitably 
sanitised copies of the files in /etc/ppp/ and 
/etc/sysconfig/network-scripts/.

For example, my ISP uses CHAP after a scripted login.  I have a
suitable chap-secrets file and also have a suitable chat script. 
These are currently setup as per the ppp-howto (i.e. pretty much the
whole lot in /etc/ppp) which is not how RH does it.

Working from the above URL I  presume I will need a file 
/etc/sysconfig/network-scripts/ifcfg-ppp0 that looks something like 
this:

-----8<-----
DEVICE=ppp0
IPADDR=[static ip of my ppp connection]
NETMASK=255.255.255.0
NETWORK=[ip of my isp's terminal server but with .0 at the end]
BROADCAST=[ip of my isp's terminal server but with .255 at the end]
GATEWAY=[ip of my isp's terminal server?]
ONBOOT=no
USERCTL=no
BOOTPROTO=none
PERSIST=yes
MODEMPORT=/dev/ttys0
LINESPEED=115200
DEFABORT=yes
DEFROUTE=yes
ESCAPECHARS=yes
HARDFLOWCTL=yes
PPPOPTIONS=
PAPNAME=
REMIP=[ip of my isp's terminal server]
MTU= 
MRU= 
DISCONNECTTIMEOUT=5
RETRYTIMEOUT=60
-----8<-----

So, stuff left unsaid... if I want an option set by pppd do I leave 
the option out of this config or give it some sort of default value 
(like 0.0.0.0 for remote ip)?

Are my assumptions about IP addresses above correct?

Should this interface be set to 'no' for ONBOOT and USERCTL?  If set 
to 'yes' for ONBOOT will that initiate a dialup during boot?

What PPPOPTIONS are suitable to be added here?  My working slackware 
copied ppp setup uses the following command line:

/usr/bin/pppd debug crtscts defaultroute lock modem persist  \
              /dev/ttys0 115200 0.0.0.0/0.0.0.0 connect \
              /etc/ppp/ppp-on-dialer

If I choose to use default values for MTU/MRU should I leave blank 
entries in my config file or just remove the entries from the config 
file completely?

In addition, I need a chat script for the scripted part of my login.  
This is currently in my /etc/ppp/ppp-on-dialer script and consists of 
some thirteen lines.  The URL above refers to the chat script in 
these terms:

> /etc/sysconfig/network-scripts/chat-
>
> chat script for PPP or SLIP connection intended to establish the
> connection. For SLIP devices, a DIP script is written from the chat
> script; for PPP devices, the chat script is used directly. 

from which I assume that I will need a 
/etc/sysconfig/network-scripts/chat-ppp0 to contain my chat script 
but I have no idea of the accepted format.  Is it in the same form as 
the chat script in my /etc/ppp/ppp-on-dialer (which includes the 
actual call to /usr/sbin/chat) or is it simply in the form of 
expect/send pairs?  There's nothing there to tell me how this file 
should be laid out.

Lastly, having been through the scripted login my ISP then runs a 
CHAP authentication on the connection so I also need a chap-secrets 
file.  This is currently in /etc/ppp/ and is working.  Where does the 
chap-secrets file live in a RH5 ppp setup?  Should it also be moved 
to /etc/sysconfig/network-scripts?

In summary, I am assuming that I need the following files:

/etc/sysconfig/ifcfg-ppp0
/etc/sysconfig/chat-ppp0
/etc/ppp/chap-secrets

in order to have a RH5-standard ppp connection working.  Is this 
correct?  Or are there other files that I will also need?

I currently have a working connection but am using:

/etc/ppp/ppp-on
/etc/ppp/ppp-on-dialer
/etc/ppp/ppp-off
/etc/ppp/chap-secrets

these files being largely gleaned from my slackware box and various 
how-to's relating to ppp.

> It's not in tutorial format, but I'm pretty sure it has everything
> you need to know to set up a PPP interface the way netcfg does.

Subject to the above questions.  :)

> The good news is that in the future sometime there will exist a
> text-mode tool capable of setting up network devices using our
> standard /etc/sysconfig way.  :-)

Yep, that _IS_ good news.  For those of us that choose, for whatever 
reason, to not install X it's currently a pain to get things done in 
the way that RH5 is doing it.  Particularly when the included man 
pages don't refer to config files that RH5 is using for stuff as 
seems the case with 'man pppd' and the how-to's don't do anything but 
tell you how to drive netcfg to do this stuff.

Thanks for your response though, at least I _think_ I'm heading in 
the right direction with this stuff.

Cheers, Dave.

-------------------------------------------------------------------------
Dave Freeman               System Administrator      Outback Qld Internet
Longreach                   Outback Queensland                  Australia
mailto:[EMAIL PROTECTED]            http://www.longreach.net.au/
Member                  Int Webmasters Association     http://iwanet.org/
-------------------------------------------------------------------------


-- 
  PLEASE read the Red Hat FAQ, Tips, Errata and the MAILING LIST ARCHIVES!
http://www.redhat.com/RedHat-FAQ /RedHat-Errata /RedHat-Tips /mailing-lists
         To unsubscribe: mail [EMAIL PROTECTED] with 
                       "unsubscribe" as the Subject.

Reply via email to