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 > >Are your Bering 1.2 boxes external interfaces IP addresses real world ones > >or are your boxes behind a NAT device so the firewall boxes ext IP is not > >your actual one? > > > >How I use the firewall is: > > > >Internet > > | > >ADSL router (NAT) > >Ext IP: 203.44.55.12 > >Int IP: 192.168.42.1 > > | > >Bering V2.2 Firewall > >Ext IP: 192.168.42.7 > >Int IP: 192.168.1.1 > > > >So what happens is EZ-IPUDATE send an IP address of 192.168.42.7 to the > >DYNDNS servers for updates. > > Did you see trace this behaviour? I found my version of ez-ipupdate use > dyndns's detect ip service being used. > > cheers > Erich ------------------------------------------------------- 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
