ddns is broken

[e9hack]

It looks like that it does work with wget-ssl. The second issue isn't gone. After reboot, it needs 5 minutes till IP's are update for the first time. I don't like to use wget-ssl, because the image size is increased by 128k if curl is replaced by wget-ssl.

I did use my configuration with the old ddns package since 5 years without any problem.

Regards,
Hartmut

Am 28.10.2020 um 15:04 schrieb Joel Johnson:
> In the meantime, would you also please try using wget-ssl to test. It provides better support for specifying origination by source address instead of just physical interface for curl.
> 
> Joel
> 
> On 2020-10-27 15:01, Joel Johnson wrote:
>> I have IPv4 and IPv6 native DDNS working with a couple of different
>> providers, thus the original commit. Would you be able to share a
>> sanitized version of your service configuration section? I'm not using
>> PPPoE which may be the related difference, "ifstatus wan | grep l3"
>> returns "br-wan" for me for both wan and wan6.
>>
>> Joel
>>
>> On 2020-10-25 15:49, e9hack wrote:
>>> Hi,
>>>
>>> ifstatus reports for wan
>>> "l3_device": "pppoe-wan"
>>> "device": "eth0.7"
>>>
>>> and for wan_6
>>> "l3_device": "pppoe-wan"
>>> "device": "pppoe-wan"
>>>
>>> I think, ddns is broken to extract the proper interface. For ipv4, I
>>> see with ps a running curl request with interface eth0.7.
>>>
>>> Regards,
>>> Hartmut
>>>
>>>
>>> Am 25.10.2020 um 22:20 schrieb Ansuel Smith:
>>>> Now I can't understand why for ipv6 works and is broken for ipv4. Any idea?
>>>>
>>>> Il giorno dom 25 ott 2020 alle ore 22:17 e9hack <e9hack at gmail.com> ha scritto:
>>>>>
>>>>> Hi,
>>>>>
>>>>> commit 5b362932a7df5ce44ca3a8f4cf1d2b225ca8d5ae
>>>>> ddns-scripts: use ip_source as bind_network default
>>>>>
>>>>> breaks ddns for ipv4, if pppoe is used for wan access. This commit sets eth0.7 as interface for curl in my case. The correct interface is pppoe-wan. For ipv6 the correct interface is set. Usually it isn't necessary to define an interface, because the correct interface is select automatically by the routing entry for the update ip address.
>>>>>
>>>>> It looks like there is more wrong after the last major update. After start of ddns, ddns waits for the check interval till the first update. Previously it was done immediately.
>>>>>
>>>>> Regards,
>>>>> Hartmut
>>>>>
>>>>> _______________________________________________
>>>>> openwrt-devel mailing list
>>>>> openwrt-devel at lists.openwrt.org
>>>>> https://lists.openwrt.org/mailman/listinfo/openwrt-devel