Bryan Hoover

struct EXP_MAPPING { DYN_DNS_CLIENT *p_dyndns; int server_index; int alias_index; char *p_exp_url; int is_username; int is_password; int is_alias; int is_ip_addr; } EXP_MAPPING; struct EXP_MAPPING { DYN_DNS_CLIENT *p_dyndns; int server_index; int alias_index; char *p_exp_url; int is_username; int is_password; int is_alias; int is_ip_addr; } ; Note the diference - removed the EXP_MAPPING on the last line, and kept the semicolon. Cheers!

In src/dyndns.h at line 660, comment out (remove) the offending variable declaration, EXP_MAPPING. Looks like new gcc compiler is the difference. Send a patch!

Thanks for the catch. Much appreciated. Will apply.

Thanks! I've uploaded a new servers_additional.cfg - https://sourceforge.net/projects/inadyn-mt/files/servers_add/ Token in --username parameter is good for a workaround what appears to be a dynv6.com parsing error - it fails to parse past an empty parameter, so I'm guessing &token=&token=xxxxxx gets parsed with the first parameter getting the value '&token' instead of the empty string. You might want to report this to dynv6.com. In the meantime, if you prefer to use --password for token, you can...

Thanks for your questions! I think the modularity of an ssl adaptor is a more robust solution.

Right, seems to be https related. Take a look at: https://sourceforge.net/p/inadyn-mt/discussion/751470/thread/3f7c4a6c00/

some examples.conf clarification

errata