No Subject

> It doesnt matter what remote IP you give it since it will just change it
> when it gets the new settings from the PPP server when it connects.
> Basically you can make up any old IP number. (Try one from the 10.x.x.x
> block)
>
> Here are the settings from one of my ppp options files..
>
> demand
> idle 60
> lock
> noauth
> defaultroute
> user myaccount
> remotename myisp
> modem 57600 crtscts
> connect '/usr/sbin/chat -v -f /etc/ppp/myisp'
>
> To run it just use
>
> pppd :10.9.9.9 /dev/modem

This sets the remote ip address, both params could be in options I assume.

> or any other IP.

I would definitely recommend the very latest pppd, _compiled_ against you're
kernel, with the correct kernel headers, ppp changed loads recently and
things that are userspace daemons talking to kernelspace are vital that they
work together properly (compiling always best), things like diald hadn't
worked for several years cos pppd went demand dial, but with more and more
people needing dynamic ip, and nobody figuring how to do it with pppd, diald
was overhawled, I believe it's started getting updates again after 2 years.

I used to use kerneld which spawed /sbin/request-route on any requested route
off a box. This meant I could simply place my dialup code in this area.

Let me know how this all goes. The closest I've ever needed to get with my
own pppd was setting up a masq. firewall about 4 years ago while in Blackpool
working for ICL. I've never used a connection slower than ISDN ever since
Uni. (Cept on my 9110 :-p)

My dads' efforts are keeping me going, last I heard the 0.0.0.0:0.0.0.0 with
demand and the ipcp-* stuff worked for him.

Damion

--
Damion Yates - Senior Internet Operations Engineer - Internet Services
email: Damion.Yates [at] bbc.co.uk - phone: +44 1737 839510

Start your own FREE mailing list at

© 2000 Microsoft Corporation. All Rights Reserved