Welcome, Guest. Please login or register.
Did you miss your activation email?
Friday 20 December 2024, 04:43:31 am

Login with username, password and session length

CLICK HERE for the The official Endian Roadmap and Issue tracker
14262 Posts in 4377 Topics by 6517 Members
Latest Member: Sandro
Search:     Advanced search
+  EFW Support
|-+  Support
| |-+  General Support
| | |-+  Dynamic DNS not working - no-ip and dyndns
0 Members and 1 Guest are viewing this topic. « previous next »
Pages: [1] Go Down Print
Author Topic: Dynamic DNS not working - no-ip and dyndns  (Read 16251 times)
ranger
Jr. Member
*
Offline Offline

Gender: Male
Posts: 3

Don't drop me


« 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.

Logged
anubisg1
Jr. Member
*
Offline Offline

Posts: 2


« Reply #1 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?
Logged
tadaog
Jr. Member
*
Offline Offline

Posts: 4


« Reply #2 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...

Logged
Pages: [1] Go Up Print 
« previous next »
Jump to:  

Page created in 0.078 seconds with 18 queries.
Powered by SMF 1.1 RC2 | SMF © 2001-2005, Lewis Media Design by 7dana.com