ddns-scripts: Updater services not started when PPPoE connection is established
Nobody has claimed this yet.
- Dominant language
- Makefile
- Stars
- 4.6k
- Forks
- 4k
- Avg merge
- 3d 12h
- Merged PRs (30d)
- 134
Description
On latest snapshot, ddns updaters are not started when PPPoE connection is established, regardless if I choose then pppoe-wan interface or the @wan or @wan6 aliases as event networks. I cannot make it work and have to restart ddns services by hand after PPPoE connects. I can see serveral notifications from netifd about wan and wan6 coming up, but nothing about ddns at all.
Looks like the hotplug.d scripts are not executed or do not behave as expected.
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 by tracing the ddns-scripts hotplug.d scripts and the netifd events emitted when the PPPoE connection brings wan or wan6 up. Reproduce the connection sequence with pppoe-wan and the @wan/@wan6 aliases, then verify that the relevant DDNS updater services start automatically without a manual restart.
Written by the indexing model from the issue text.
Assessment
- Domain
- networking
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100