Hi list :-)
I recently installed IPCOP on my gateway machine - it used to run debian 
stable, but I fancied a play around with IPCOP. Anyhow, there are a couple of 
small issues I have yet to sort out:

Firstly; dial on demand. When the machine first boots, it's in a mode called 
"waiting for dial on demand" or some such. It works correctly, as soon as 
someone requests an external address it brings up the link, yay. This is 
great for people like my father, who could never get the hang on logging into 
the debian machine to type 'pon' ;-)

However - if someone picks up the phone, and the modem gets disconnected, it 
goes into "modem idle" mode. doh! It seems to think that the RED interface is 
still active (when it's damn well been disconnected), and won't go back to 
the "waiting for dial on demand" state until you first issue a 'disconnect' 
(so it thinks the RED interface is down) and then 'connect' from the web 
interface. This is most annoying, as it means every time we go to use it 
someone needs to manually put it into "waiting for dial on demand" mode 
before it can be used as "dial on demand" again - kinda defeats the purose, 
no?

I think I'll solve this with some sort of cheap hack - maybe a little script 
that sits running in the background and manually changes things back when it 
sees the modem connection got dropped. But if anyone knows "The Right 
Way"(tm) to do this, or at least a semi-graceful way... I'd appreciate any 
pointers :-)

Secondly, I use dyndns. On my debian machine I had a little python script that 
ran when the ppp link came up, to notify the dyndns servers of my new IP. I'm 
not sure if IPCOP even comes with python, being a cut down firewall distro I 
suspect it probably won't (sorry, I haven't checked yet). Is there a good / 
easy / simple way of dealing with updating dyndns on IPCOP machines? Or 
should I cobble something together myself? Some others out there must be 
using dyndns and IPCOP...

Any help appreciated :-)

Cheers,
  Gareth




Reply via email to