DAWN does not see other APs until umdns is restarted
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 7
- Forks
- 20
- PR merge metrics
- No merged PRs in 30d
Description
Good afternoon! Thanks for the fantastic software.
Related bug on DAWN:
https://github.com/berlin-open-wireless-lab/DAWN/issues/237
There seems to be a problem with umdns or DAWN that requires umdns to be restarted periodically. Specifically I was just hit with it on my two WAX218 APs running:
OpenWrt 23.05.5 r24106-10cc5fcd00 / LuCI openwrt-23.05 branch git-24.264.56413-c7a3562
umdns:
2024-03-04-7c675979-1
Upon reboot umdns shown running, but ubus call umdns update && ubus call umdns browse is an empty JSON file, returning only { }.
Restarting umdns fixes the issue shortly afterwards.
The issue linked suggested that when this situation happens to umdns it is no longer listening on any ports, I have not been able to run that as I restarted umdns so everything is currently working.
Contributor guide
No contributing guide indexed for this repository
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 reproducing the post-reboot state on OpenWrt 23.05.5 with the reported umdns version, then run ubus call umdns update and ubus call umdns browse while checking whether umdns is listening on its ports. Done means umdns continues discovering the other APs after reboot and does not require a manual restart.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c
- Domain
- networking
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100