Gargoyle Forum

You're welcome, and thank you for looking into this.

Thank you for your additional testing. I have read the source code. I did not read it as closely as you apparently. Gargoyle doesn't support IPv6 no. When building a lot of modules for IPv6 actually get disabled. So even if this doesn't make it in for that reason, it's still interesting to other us...

i'll let Eric decide if this is a good idea or not. I think it's kind of a niche case because of the 6in4 thing. He's actively developing at the moment so i'll make sure it is at least looked at before the next major release. Cheers mate. Does this mean that Gargoyle has no IPv6 support, even thoug...

I'm concerned that it can't find the remote ip. See this post for the output I expected to see: https://www.gargoyle-router.com/phpbb/viewtopic.php?f=13&t=3623&p=30878#p30877 Don't be concerned about it. ;) It simply means that ddns_gargoyle has not yet cached the IP. If you've been using d...

Hi, I wish to propose an update to the hotplug script that works on both the default Gargoyle setup (uclibc), and my custom OpenWRT trunk dual-WAN setup (musl) . The problem with the default script under my custom compile is that whenever the hotplug system reaches 25-ddns, it suspends the execution...

Sure, here it is, after invoking /etc/init.d/ddns_gargoyle restart ed Aug 19 11:52:46 2015 daemon.info ddns_gargoyle[8636]: Forcing update: Wed Aug 19 11:52:46 2015 daemon.info ddns_gargoyle[8636]: service provider=he.net Wed Aug 19 11:52:46 2015 daemon.info ddns_gargoyle[8636]: domain=<TUNNELID> We...

I'm using 6in4 IPv6 Tunneling via Hurricane Electric. I have added a /etc/ddns_providers.conf section for he.net in ddns-gargoyle , so that the service can be used to periodically check for IP address changes, and update the endpoint accordingly, to maintain the IPv6 tunnel connection. service he.ne...

This issue is SOLVED in Gargoyle 1.7.0. Thanks.

In case any other is affected by this bug, as a workaround, changing the /etc/ddns_providers.conf for duckdns as follows: service duckdns.org url_template http://www.duckdns.org/update?domains=[[DOMAIN]]&token=[[TOKEN]]&ip=[[IP]] required_variables domain token required_variable_names DyDNS....

Hey thanks for chiming in.

So it would seem that duckdns made changes to its web pages that became incompatible with ewget, thereby causing a segfault and the update never finishes.

This is a confirmed bug. I hope one of the devs would give advice on how to proceed from here.