Re: ip-up & ip-down

1998-12-31 Thread Frederic Breitwieser
>Why are you rewriting ip-up and ip-down? The standard Debian ip-up and Honestly? I didn't read the man pages, and it seemed logical at the time :) Frederic Breitwieser Bridgeport, CT 06606 Homebrew Automotive Website: http://www.xephic.dynip.com/ 1993 Supercharged Lincoln Continental 1989 H

Re: ip-up & ip-down

1998-12-31 Thread john
Martin Bialasinski writes: > There is also another problem. When ppp is updated, it will update poff, > and all changes would be lost. I thought it was fairly obvious that one would need to take measures to deal with this. The simplest is to just put the edited poff in /usr/local/bin. You could

Re: ip-up & ip-down

1998-12-30 Thread Martin Bialasinski
>> "j" == john <[EMAIL PROTECTED]> writes: j> Just edit poff. It's a pretty simple script. The problem with this j> is that poff isn't the only thing that can cause pppd to take down j> the connection. There is also another problem. When ppp is updated, it will update poff, and all changes wou

Re: ip-up & ip-down

1998-12-30 Thread john
Jim Foltz writes: > You could have poff call some program and waits for it to exit before it > takes the link down. I think this technique is called a wrapper. So you > move poff to poff.real and create a new poff that tells your service you > are going offline, then calls poff.real Just edit poff

Re: ip-up & ip-down

1998-12-30 Thread Jim Foltz
On Wed, Dec 30, 1998 at 12:11:49PM -0600, [EMAIL PROTECTED] wrote: > Martin Bialasinski writes: > > When ip-down is run, the ip-layer is already down, so there is no way to > > make contact to hosts over the link. So some programm like "contact the > > dynip service to tell them I am going offline"

Re: ip-up & ip-down

1998-12-30 Thread john
Martin Bialasinski writes: > When ip-down is run, the ip-layer is already down, so there is no way to > make contact to hosts over the link. So some programm like "contact the > dynip service to tell them I am going offline" doesn't work. A while back someone suggested hacking pppd to run "ip-abou

Re: ip-up & ip-down

1998-12-30 Thread Martin Bialasinski
>> "j" == john <[EMAIL PROTECTED]> writes: j> #!/bin/bash j> dynipclient -k j> ... j> ... j> and put a similar script in ip-up.d. Just a thought: When ip-down is run, the ip-layer is already down, so there is no way to make contact to hosts over the link. So some programm like "contact the d

Re: ip-up & ip-down

1998-12-30 Thread john
Frederic Breitwieser writes: > 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 ! This documented in the pppd man page. It is done for security reasons. The st

Re: ip-up & ip-down

1998-12-29 Thread Frederic Breitwieser
>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, an

Re: ip-up & ip-down

1998-12-29 Thread Frederic Breitwieser
>May I ask what dynipclient does? I'm setting up a tiny network at home and >am going to network a Linux box (running slink) with a Windows 95 machine >(my son's) and I get a dynamic IP address from my ISP. I use a PPP >connection. head over to www.dynip.com, they give a better explaination than

Re: ip-up & ip-down

1998-12-25 Thread David Natkins
May I ask what dynipclient does? I'm setting up a tiny network at home and am going to network a Linux box (running slink) with a Windows 95 machine (my son's) and I get a dynamic IP address from my ISP. I use a PPP connection. David Natkins email: [EMAIL PROTECTE

Re: ip-up & ip-down

1998-12-25 Thread john
> In the ip-up file, I need to execute: > /usr/local/bin/dynipclient -p > In the ip-down file, I need to execute > /usr/local/bin/dynipclient -k > When I add the lines, it doesn't work. How do you know? These scripts are run with stdout directed to /dev/null, so you won't see any