🚀 go-pugleaf

In article <74g9qk$46r$1@lios.apana.org.au>, cdewick@lios.apana.org.au says...
>
>
>Hi,
>
>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.
>
>Is this a know problem with ppp-2.3.x, and if so, what's the fix?
>
>I already have two ms-dns lines in the main 'options' file that pppd reads.
>but it doesn't seem to change anything. I don't know if it's something
>broken in Win95 that's actually fixed in Win98, but that could be a
>possibility.
>

ms-dns lines defines _Domain Name Service servers_ for client, not client's 
IP-address.

You have to add line to options.ttySx, where names/ip-addresses of sever and 
client are defined:

servername:clientname

Put there instead of servername and clientname name of your server and name, 
reserved for client (without domain name).

Example:

My Linux box has name ns.tartu.customs.ee, for client is reserved name 
m155.tartu.customs.ee, so I have line

ns:m155

Of cource, these names must exist on domain name server.

Regards,
Valentin Abramov

In article <74g9qk$46r$1@lios.apana.org.au>,
Craig Dewick <cdewick@lios.apana.org.au> wrote:
>
>Hi,
>
>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.
>
>Is this a know problem with ppp-2.3.x, and if so, what's the fix?

It certainly doesn't happen under SunOS 4.1.4 for me! Are you sure
you've got both the modem "options" files and the Win95 TCP/IP setups correct?

>I already have two ms-dns lines in the main 'options' file that pppd reads.
>but it doesn't seem to change anything. I don't know if it's something
>broken in Win95 that's actually fixed in Win98, but that could be a
>possibility.

ms-dns merely picks the DNS server. You need an option such as 
":10.0.2.3" or ":hostname.local.net" to actually set the IP address
for the dial-up machine. Re-read the pppd manual page....



-- 

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?

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.
>>
>>Is this a know problem with ppp-2.3.x, and if so, what's the fix?

>It certainly doesn't happen under SunOS 4.1.4 for me! Are you sure
>you've got both the modem "options" files and the Win95 TCP/IP setups correct?

Yes, as far as I can tell.

>>I already have two ms-dns lines in the main 'options' file that pppd reads.
>>but it doesn't seem to change anything. I don't know if it's something
>>broken in Win95 that's actually fixed in Win98, but that could be a
>>possibility.

>ms-dns merely picks the DNS server. You need an option such as 
>":10.0.2.3" or ":hostname.local.net" to actually set the IP address
>for the dial-up machine. Re-read the pppd manual page....

I've already got that.

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.

Regards,

Craig.
-- 
            Craig Dewick. Send email to 'cdewick@lios.apana.org.au'
  Point a web browser at 'http://lios.apana.org.au/~cdewick/sun_shack.html' to
    access my archive of Sun information and links to other places. For info 
      about Sun Ripened Kernels, go to 'http://www.zeta.org.au/~craig/srk'