EFW Support

Support => General Support => Topic started by: ranger on Sunday 01 August 2010, 11:38:34 pm



Title: Dynamic DNS not working - no-ip and dyndns
Post by: ranger on Sunday 01 August 2010, 11:38:34 pm
I have been trying to get the dynamic DNS feature to work but it fails.  I have added 2 different DDNS providers and neither of them update.  The log file "dynupdate" is empty so reviewing that hasn't helped.  Any input on how to debug or track this down would be appreciated.  I have flipped all the switches for proxy, NAT, and wildcards just to try all web page configurable items but they have no impact.



Title: Re: Dynamic DNS not working - no-ip and dyndns
Post by: anubisg1 on Tuesday 14 December 2010, 08:35:10 pm
i also need help here...

i configured the dyndns, i added the flag NAT and wildcards, since i'm behind a router and i have a payed account that support wild cards,
even than, when my router disconnect and change ip, the dydns dns is NOT updated.. i need to do that manually

ideas?


Title: Re: Dynamic DNS not working - no-ip and dyndns
Post by: tadaog on Friday 17 December 2010, 12:39:10 am
There's several bugs in 2.4.1, notably in gateway assignment and routes in OpenVPN too.
In that case, there's a line in /usr/local/bin/setddns.pl that compares with an if statement using "=" as an operator, but in Perl the comparison operator is "eq", as you can see in all the others if statements.

Suffice only to change = to eq and everything works OK as in 2.4.0.

But I don't know how to correct the OpenVPN wrong operations, so I stopped updating efw 2.4.0 using efw-upgrade, because it brokes all of our EFW installations.

This bugs are present in the ISO too, I've installed a fresh one and tried all of the above features to check. So forget about using the ISO too, unless they come out with a RESPIN of that with all these corrections.

Unfortunately, I have to come to the conclusion that the developers (or whoever was assigned to test it) didn't tested at least these two essential features (for me, at least) or the Community Version is released to be tested "as is" without any major consideration, by us taking all the risks.

And to conclude, this bugs are there and there's nothing coming out to correct them, so...

Now, it's their turn...