Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
luci-mod-network: split dns and dhcp functionality
See original GitHub issueI would like to be able to split out the functionality for dns and dhcp for dnsmasq such that the dns UI could be independently installed. This would be useful in cases like Turris images that use a completely different dns resolver (knot-resolver).
I am happy to help in this effort. Is this something that would be welcome? I think the first obvious stel would be separating the config domain sections and any other dns configuration out of the /etc/config/dhcp so that they can be maintained as separate files. Of course, appropriate backward compatibility would need to be added to make this work smoothly. Is there a statement anywhere on backward compat requirements for OpenWrt that I could read up on?
Is this something that would be possible?
Issue Analytics
- State:
- Created 3 years ago
- Comments:5 (3 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
To provide a bit now context, dnsmasq is still used for DHCP on turris. I would like to make it so that dnsmasq’s luci config for DHCP stays around. Also, there are some options that probably make sense for most DNS servers. It would be ideal to separate those out so that different resolvers could use a single common config for those common things.
This looks like something that should be implemented in OpenWrt first to sort out the general configuration structure. LuCI can follow it then. I am not going to introduce LuCI specific deviations here.