mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Jeff V. Merkey" <jmerkey@vger.timpanogas.org>
To: J Sloan <jjs@pobox.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: setting up pppd dial-in on linux
Date: Sat, 25 Nov 2000 12:10:49 -0700	[thread overview]
Message-ID: <20001125121049.A29510@vger.timpanogas.org> (raw)
In-Reply-To: <20001125003600.A28207@vger.timpanogas.org> <3A1F6EB6.A5E47686@pobox.com>
In-Reply-To: <3A1F6EB6.A5E47686@pobox.com>; from jjs@pobox.com on Fri, Nov 24, 2000 at 11:48:06PM -0800

On Fri, Nov 24, 2000 at 11:48:06PM -0800, J Sloan wrote:
> "Jeff V. Merkey" wrote:
> 
> > Anyone out there a whiz at setting up a pppd dialin server?  I am
> > trying to put together an RPM for pppd dialin configurations
> > that will support default Windows NT and Linux dial in clients
> > without requiring the poor user to learn bash scripting, chat
> > scripting, mgetty and inittab configuration, etc.  The steps
> > in setting this up are about as easy as going on a U.N. relief
> > mission to equatorial Africa, and most customers who are
> > "mere mortals" would give up about an hour into it.
> 
> Red Hat's ppp client setup is about a 90 second job

I am using theirs as a base.   Setup's not the issue.  It's the 
chap MD5 authentication for NT clients and the constant 
crashing that's troublesome.  I have it working, just not
with NT clients.

> 
> > I am seeing massive problems with pppd dial-in and IP/IPX
> > routing with problems that range from constant Oops, to
> > the bug infested pppd daemon failing valid MD5 chap
> > authentication.  The HOW-TO's and man pages provide
> > wonderful commentary on all the things about pppd
> > that don't work, but it's not too helpful on getting
> > it to work reliably.  An NT dial-in server takes about
> > 5 minutes to configure on W2K.  Linux takes about 2 days, and
> > won't stay up reliably.
> 
> hmm, an awful lot of ISPs use Linux dialup servers...
> 
> I set up a linux ppp server back in 1996 - things might have
> changed, but it seemed fairly straightforward at the time -
> 
> can't imagine it's gotten worse since then...
> 
> > Who out there is an expert on Linux pppd that would like
> > to help put together some easy configs for standard
> > dial-in scenarios?
> 
> Crunch time for me right now, finals coming right up...

Thank's anyway.  I'll keep working on the bugs.

:-)

Jeff

> 
> I'll bet there's quite a few ISP-savvy admins who could
> lend a hand though -
> 
> jjs
> 
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

  reply	other threads:[~2000-11-25 18:44 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-11-25  7:36 Jeff V. Merkey
2000-11-25  7:48 ` J Sloan
2000-11-25 19:10   ` Jeff V. Merkey [this message]
2000-11-27 10:00     ` Raivis Bucis
2000-11-25 13:28 ` Pedro M. Rodrigues
2000-11-25 19:12   ` Jeff V. Merkey
2000-11-25 17:04 ` William Scott Lockwood III
2000-11-25 19:13   ` Jeff V. Merkey

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20001125121049.A29510@vger.timpanogas.org \
    --to=jmerkey@vger.timpanogas.org \
    --cc=jjs@pobox.com \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®