> > The problem I had was ezipupdate would use the dyndns detect my ip > > service only if you specified a ip of 0.0.0.0 and no interface. > > The problem with that was to run ezipupdate as a daemon it needs an > > interface specified. > > > > Worked great at commond line ( started to celebrate) > > as a daemon, failed due to no interface ( I gave up and wrote the > > script instead ) > > Bruce; > > I remember to have had the same problems and start ez-ipupdate > from /etc/ppp/ip-up script as a workaround (mimicing the working > command line). > I believe I have described that and a warning about the daemon in the > Bering-uClibc docs. > > Sorry for getting in too late > kp >
Yes that would work but for the fact as its behind a ADSL device with NAT, when the ADSL modem gets given a new IP which happens sometimes twice a day, the firewall would not sense that interface has changed. I've tried most combinations, I do welcome further imput though Regards Bruce ------------------------------------------------------- This SF.net email is sponsored by: IT Product Guide on ITManagersJournal Use IT products in your business? Tell us what you think of them. Give us Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out more http://productguide.itmanagersjournal.com/guidepromo.tmpl ------------------------------------------------------------------------ leaf-user mailing list: [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-user SR FAQ: http://leaf-project.org/pub/doc/docmanager/docid_1891.html
