From mboxrd@z Thu Jan 1 00:00:00 1970 From: Matthias Fischer To: development@lists.ipfire.org Subject: Re: Forcing all DNS traffic from the LAN to the firewall Date: Fri, 25 Dec 2020 17:57:11 +0100 Message-ID: <26085997-9dcf-39b9-d065-2fb9fc435fe1@ipfire.org> In-Reply-To: MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============1116768072934656548==" List-Id: --===============1116768072934656548== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit On 23.11.2020 10:08, Matthias Fischer wrote: > Hi, > > to keep this discussion going, I'd like to publish ... A solution. Finally I got it working. Current discussion: => https://community.ipfire.org/t/testing-dns-redirect-code-snippet/3888 In the end, it was easier as I thought, having the missing link always in front of my eyes. But didn't see it. Until today. After I added 'optionsfwctrl.c' to the process, it was just one missing line in 'optionsfw.cgi'. But perhaps there are still some things left. 1. Having looked through the various options I can't see no option which needs a *complete* reboot of the machine anymore. Is this right? 2. If I'm right I would remove "$errormessage .= $Lang::tr{'new optionsfw later'};" after choosing "Save And Restart". For me, it seems that this message is no longer needed at this point. Am I right? 3. If we still need a reboot, I would mark the relevant options with a star ("* Changing this option requires a reboot"). 4. Otherwise the complete code is finally ready to be tested and tortured ( ;-) ) snd I'll prepare something for patchwork. As always: Hints and testers are welcome... ;-) Best, Matthias --===============1116768072934656548==--