ddns-scripts fails to autostart with Event Network set to "@wan". "wan" option is missing.
Nobody has claimed this yet.
- Dominant language
- Makefile
- Stars
- 4.6k
- Forks
- 4k
- Avg merge
- 3d 12h
- Merged PRs (30d)
- 134
Description
In LuCI DDns Service service > Edit > Advanced Settings, the Event Network option, once changed, does not include the 'wan' interface in the drop down list. Only the '@wan' alias is listed. dynamic_dns_updater.sh does not autostart on boot when Event Network is set to '@wan'.
The documentation does not explain the Event Network option and the implications of choosing 'eth0.2', 'wan' or '@wan'.
The setting is found in /etc/config/ddns.
config service 'myddns_ipv4'
...
option interface 'wan'
...
Using:
ddns-scripts 2.8.2-12
ddns-scripts-services 2.8.2-12
luci-app-ddns git-21.349.33342-b5a40b3
LuCI openwrt-21.02 branch (git-21.295.67054-13df80d) / OpenWrt 21.02.1 r16325-88151b8303
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the Event Network handling in dynamic_dns_updater.sh and the /etc/config/ddns setting, then inspect the LuCI DDns Service Advanced Settings dropdown. Done means the wan option is available, autostart works when Event Network is set to wan, and the documentation explains the implications of eth0.2, wan, and the @wan alias.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- shell
- Domain
- documentation, networking
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100