PPP setup with RH5.2

[Christopher Twigg]

I'm not exactly sure what you're trying to do here -- are you just setting
your RedHat box up to do IP Masquerading?  But here are a couple of things
I noticed that might be a problem:

On Thu, 4 Mar 1999, M. Oesterwinter wrote:

> Installed Redhat as normal.
> Set up linux for my home network - NE2000 card - 192.168.1.100 I don't
> know what to do for the settings:
> Nameserver I used - 192.168.1.254 (default)
> Gateway I used - 192.168.1.100 (planning to use this as IP_masq sys, is
> this right?)

The default gateway is going to be the gateway on the remote network when
PPP is up.  AFAIK, Linux only allows a single default gateway, so this
might be a problem.  However, on all the _other_ machines on the network,
192.168.1.100 will be the default gateway if you're doing IP masquerading.

I would take the default gateway out of that machine altogether and let
ppp pick it for you (it does this automatically, right?  I haven't used
Linux for dial-up in ages...)

> Don't know what to put for domain name and all that.  Do I just make up
> one (such as marcus.com and host name linux.marcus.com?) 
> Added routed (I hope this doesn't affect anything)

I don't see how routed is going to be anything but trouble in your
situation, since I doubt you're using RIP.

> Install is done.
> Go into X and run linuxconf
> Add ppp0 and use PAP leave all defaults....
> Try and connect from linuxconf - doesn't do anything
> Save all and exit linuxconf
> Run usernet (as Redhat book says to do) Get green light for IO and eth0,
> red light for ppp0, click on ppp0 dials, and turns green.
> Try to telnet and run netscape.  No reponses.
> Leave x-win - download wvdial with minicom.  Install.  Setup.  Run.
> Doesn't work - default script doesn't work.
> Try configuring ppp-on script.  Doesn't use PPP.  Dial into uw and notice
> that script needs to look for Username: instead of ogin: and needs to send
> PPP after >>.  Try to confige script to do this.  I don't understand
> scripting language because it doesn't dial after I edit the script as I
> think it needs to be.     

PAP is an authentication protocol that bypasses the "login:" prompt all
together.  PAP sends a special authentication packet back to the server as
soon as you establish a connection; the "username:" prompt is provided for
backwards compatibility.  I know for a fact that some NAS devices these
days (Cisco AS5200, for example) don't even provide a "login:" prompt
any more since PAP is so widespread.  However, I don't know much about the
UW network, so perhaps someone else who has had luck with dialup could
fill me in...

Christopher Twigg
cdtwigg at u.washington.edu