>How do you know?  These scripts are run with stdout directed to /dev/null,
>so you won't see any output.

I was able to determine this by having another PC, running windows,
connected to the internet not being able to ping the resolved name.  I had
originally though, since I can't ping the box, and I didn't see any output,
the program wasn't being executed properly.  Turned out to be in fact true.

In the ip-up and up-down scripts, I had to switch directories in order for
the program to see its config file in the same directory - it doesn't use
any path or environment variables !!!!! Unfortunately, it doesn't say that
anywhere in the directions, which I followed too literally apparently :(

So, in ip-down for example, I ended up with the following:

     ....
cd /usr/local/bin
dynipclient -k
cd /etc/ppp
     ....

And viola, I'm all set :)

Thanks for your help and support everyone!


Frederic Breitwieser
Bridgeport, CT 06606

Homebrew Automotive Website:
http://www.xephic.dynip.com/

1993 Supercharged Lincoln Continental
1989 HMMWV
1973 Lincoln Continental (460cid)
1975 Dodge D200 3/4 ton Club Cab
2000 Buick-Powered Mid-Engined Sports Car

-

Reply via email to