luci-app-wireguard: dns ignored in generated config
Nobody has claimed this yet.
- Dominant language
- Makefile
- Stars
- 4.6k
- Forks
- 4k
- Avg merge
- 3d 12h
- Merged PRs (30d)
- 134
Description
Package Name
luci-app-wireguard
Maintainer
@EricLuehrsen
OpenWrt Version
25.12.5
OpenWrt Target/Subtarget
ipq40xx/generic
Steps to Reproduce
- start from existing wgserver configuration
- add peer
- enter name
- generate key pair
- generate preshared key
- enter allowed IPs, hitting "plus" after each one
- tick "route" if appropriate
- enter keepalive, if appropriate
- save
- re-enter peer definition, check all in order
- click "configuration export"
- add dns server, hitting "plus" after each one
- note that the desired dns IS indeed displayed in the generated config
- click to download the config
Actual Behaviour
the saved config does NOT have the dns entry, which is however visible in the onscreen config AND correctly present in the QR code
on a whim, I redid all the steps entering the DNS as /32 at the end, no changes: still no dns entry in the saved config.
saving the new peer and applying changes also does not fix the behaviour
Confirmation Checklist
- The package is maintained in this repository.
- I understand that issues related to the base OpenWrt repository or LuCI repository will be closed.
- I am reporting an issue for OpenWrt, not an unsupported fork.
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 in the luci-app-wireguard package and reproduce the configuration export/download flow described in the issue. Compare the onscreen configuration, QR code, and downloaded file after adding DNS servers; done means the downloaded configuration includes the same DNS entry shown in the other outputs.
Written by the indexing model from the issue text.
Assessment
- Domain
- networking
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 52/100