At 09:25 23/09/99 -0600, you wrote:
>When I dial up to the net via Network Configurator (netcfg), everything works
>great. I get on the net, and everything works perfectly. I did a "ps
--cols 1000
>ax | grep ppp" and noticed that Network Configurator starts pppd with many
>options:
>
>/usr/sbin/pppd -detach lock modem crtscts asyncmap 00000000 defaultroute
debug /dev/ttyS1 115200 remotename ppp0 ipparam ppp0 debug kdebug 2 connect
/usr/sbin/chat -v -f /etc/sysconfig/network-scripts/chat-ppp0
>
>However, when kppp dials up to the net and tries to start pppd, 'ps' tells me
>it's started this way:
>
>pppd 38400 -detach crtscts lock modem
>
>Subsequently, when I dial up using kppp, my /etc/ppp/ip-up script never gets
>run and pppd eventually times out and fails.
>
>It seems like kppp starts pppd with far too few options for anything to work.
>I'm running Mandrake 6.0, kdenetwork-1.1.1final-7mdk, ppp-2.3.8-1mdk, and
>kernel 2.2.12 SMP that I compiled myself (not from Mandrake).
>
>Any help appreciated! I'd sure like to dial up using kppp instead of Network
>Configurator.
Totally agree. :)
I found that I needed to use the scripting facility in kppp to get connected.
It works transparently after it's set up so you just have to click on the
kppp icon (or docked app) and then Connect to get on. My kppp setup is at
home, but I'll bring it in for tomorrow if you need it.
hih
nick@nexnix
