Hi Dan, Thanks for the feedback...
I personally use the new dyndns-host-open plugin, for all the reasons you describe. The developers here eat our own cooking. :-) Lonnie On May 23, 2011, at 7:59 AM, Dan Ryson wrote: > While I've always been delighted to see the progress shown in a new release, > I was particularly tickled about this gem in the ChangeLog: > > -- AIF, dyndns-host-open plugin, re-written for AstLinux. Provides > EXT->Local firewall 'host-open' > rules using hostnames (via periodic DNS lookups) rather than static IP > addresses. Should the > hostname resolve to multiple IPv4 addresses, a rule for each address will > be opened. IPv4 only. > Note: If users had made the previous dyndns-host-open plugin work by > adding a CRON, etc., there > is no CRON necessary with the new dyndns-host-open plugin. > > All of my off-site users have dyndns-equipped routers and domain names. > Until now, because these dynamic IP addresses seldom change, I've been > manually permitting access whenever new IP addresses were assigned. > However, Murphy's-Law has a hand in this process: It seems IP address were > only changing when I was on travel or otherwise unavailable. > > As always, thanks for your hard work and dedication to this project. > > Dan ------------------------------------------------------------------------------ What Every C/C++ and Fortran developer Should Know! Read this article and learn how Intel has extended the reach of its next-generation tools to help Windows* and Linux* C/C++ and Fortran developers boost performance applications - including clusters. http://p.sf.net/sfu/intel-dev2devmay _______________________________________________ Astlinux-users mailing list Astlinux-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/astlinux-users Donations to support AstLinux are graciously accepted via PayPal to pay...@krisk.org.
