Just last night, I got kppp working with my modem.  The modem was the
biggest pain (pnp Boca SoundExpression combo sound/modem card -- had to
disable pnp OS setting from BIOS, and configure the modem to be on ttyS3).
Once I had the modem working (verified with minicom), kppp was a cinch!

The biggest problems I had with kppp were caused by Yast setting the
permissions on pppd incorrectly.  As a newbie, I didn't want to deal with
the low-level ppp crud right away.  Kppp did a nice job of hiding this from
me.

I feel that the biggest improvement that could be made to kppp is in the
area of diagnostics.  As a newbie, I had a tough time figuring out where the
output from pppd was getting dumped.  I also had a tough time figuring out
that my ISP might not be using the "default" ppp login method (mine uses
CHAP).  Give me a couple weeks and maybe I will attempt to add these
enhancements.

First I had to download and compile 2.2.4 to get the framebuffer device
working so I could use my S3 Trio3D graphics card.  Then I had to pound on
my crazy modem.  Sound is the next challenge!  Wish me luck.

-----Original Message-----
From: Benjamin A. Rosenberg [mailto:[EMAIL PROTECTED]]
Sent: Thursday, April 01, 1999 7:50 AM
To: Suse Mailing List
Subject: Re: [SuSE Linux] KPPP Configuration - What's wrong with this
picture?



nothing against kppp, but i seem to see everyone having lots of problems
with it and no one seems to be trying ezppp or xisp which work without
much of a headache...give either of those a try..I have used both. Right
now I am fond of ezppp :)


Jerry Lynn Kreps wrote:
> 
> Yatsen Ng wrote:
> >
> > I configured Kppp (in the KDE wm) and initially I get a connection but
> > then it dies (unexpectedly! - is this a joke? Was he shot? I imagine
> > that if he'd died after long term illness he died 'expectedly'). Why is
> > that? I didn't do anything out of the ordinary nor did I add any
> >
> 
> More than likely it is one or both of two possibilities:
> 1.  Your /etc/ppp/option file has a line starting with "Lock" in it.
> Empty that file.
> 2.  Your /usr/sbin/pppd file is lacking su permission.  As root issue
> "chmod a+s  /usr/sbin/pppd".  Unless you change /etc/permissions to tell
> YaST what you want on pppd it will strip suid off of pppd every time it
> is run.

-- 
Ben Rosenberg
----------------||---------------------
"Whatever separates you from the truth,
throw it away, it will vanish anyhow." 
----------------||---------------------
mailto:[EMAIL PROTECTED]
--
To get out of this list, please send email to [EMAIL PROTECTED] with
this text in its body: unsubscribe suse-linux-e
Check out the SuSE-FAQ at http://www.suse.com/Support/Doku/FAQ/ and the
archive at http://www.suse.com/Mailinglists/suse-linux-e/index.html
--
To get out of this list, please send email to [EMAIL PROTECTED] with
this text in its body: unsubscribe suse-linux-e
Check out the SuSE-FAQ at http://www.suse.com/Support/Doku/FAQ/ and the
archive at http://www.suse.com/Mailinglists/suse-linux-e/index.html

Reply via email to