🚀 go-pugleaf

Craig Dewick wrote in message <74h13m$4ll$1@lios.apana.org.au>...
>In <F3LJzv.Erv@world.std.com> raoul@world.std.com writes:
>
>>>I'm running a small dial-in server (Sparc LC running SunOS 5.6) here, and
I
>>>use Paul Mackerras' ppp-2.3.5 package to provide PPP support. Every
person
>>>calling in who's using Win95 for PPP has to manually start PPP after
logging
>>>in, rather than using automatic start up because their machines are
unable
>>>to automatically retrieve the IP address they're allocated during the
>>>startup phase of their PPP sessions.
>
<snip>
>
>The main 'options' file is:
>
>lock
>crtscts
>203.14.152.51:
>netmask 255.255.255.240
>ms-dns 203.14.152.51
>ms-dns 202.12.88.44
>name jedi
>
>and 'options.term.0' is:
>
>debug
>idle 1800
>maxconnect 21600
>proxyarp
>:203.14.152.60
>
>The last line is different for all four dial-in lines.
>
>So I don't see why it's not working, but apparently (I don't have any PC's
>so I don't use Windows) everyone using Win95 has to manually start their
PPP
>sessions because it can't automatically pick up the allocated IP address.
>
<snip>
>

How about options like 'auth' and 'login' to force pap authentication?