On Tue, Jun 14, 2011 at 2:18 PM, James L. Lauser <james at jlauser dot net> wrote:

> I don't think this will work, as (at least the last time I looked), HE
> requires an IP address for the tunnel configuration.  The "right" way to do
> this would be to add support to m0n0wall to use HE's dynamic tunnel update
> API (really just a simple web request).  I've wanted this support as well,
> but work around it by having one of my other servers that's behind the
> m0n0wall device do it for me instead.
>

Ah, too bad. It seems so obvious to me to just put the FQDN into the tunnel
endpoint address and then use DynDNS to keep the address updated.


-- 
Brian Lloyd, WB6RQN/J79BPL
3191 Western Dr.
Cameron Park, CA 95682
brian at lloyd dot com
+1.767.617.1365 (Dominica)
+1.931.492.6776 (USA)
(+1.931.4.WB6RQN)