From: Matthias Fischer <matthias.fischer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: Forcing all DNS traffic from the LAN to the firewall
Date: Sun, 15 Nov 2020 14:36:01 +0100 [thread overview]
Message-ID: <0bf6771a-5d03-762a-9244-1567dd500754@ipfire.org> (raw)
In-Reply-To: <79177e1f-7be3-f088-2313-eff26c78a328@ipfire.org>
[-- Attachment #1: Type: text/plain, Size: 1392 bytes --]
Hi,
On 13.11.2020 17:57, Matthias Fischer wrote:
> On 13.11.2020 15:23, Michael Tremer wrote:
[Slightly shortened, kept the relevant parts]
>> ...
>
>>> - Where (E.g: firewall init script, rules.pl, wirelessctrl.c, ...)
>>> should the necessary iptables rules be processed?
>>> [Some ideas how this could be done, but no "breakthrough". Current
>>> option-settings are processed in several scripts. Which one to use!?]
>>
>> This would probably go into /etc/init.d/firewall.
Sorry, but *which* line? I'm really not sure. I suppose somewhere after
line 179f which read:
...
iptables -t nat -N CUSTOMPREROUTING
iptables -t nat -A PREROUTING -j CUSTOMPREROUTING
...
I don't want to mess things up - especially in *this* script!
We need an "if"-query to check for ON/OFF there, ok.
But the more often I read this script the less sure I am where this code
can be inserted best. Where? Hints?
Besides, deactivating these rules would need a complete reboot!? Or do I
overlook something?
Because if this should be the case then on the firewall options page the
entries that require a restart should be *marked* to make things easier
and more clearly. Otherwise you switch ON <-> OFF or vice versa without
*really* realising that your changes "need a reboot". The notice "Some
options need a reboot to take effect" is not sufficiently meaningful.
"Some options..."!? Which?
Best,
Matthias
next prev parent reply other threads:[~2020-11-15 13:36 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-09 17:47 Matthias Fischer
2020-11-10 13:07 ` Tapani Tarvainen
2020-11-13 14:24 ` Michael Tremer
2020-11-13 14:35 ` Tapani Tarvainen
2020-11-11 15:02 ` Rainer Kemme
2020-11-13 14:23 ` Michael Tremer
2020-11-13 14:55 ` Tapani Tarvainen
2020-11-15 13:16 ` Matthias Fischer
2020-11-15 14:45 ` Michael Tremer
2020-11-15 15:33 ` Tapani Tarvainen
2020-11-16 10:32 ` Michael Tremer
2020-11-15 14:40 ` Michael Tremer
2020-11-13 16:57 ` Matthias Fischer
2020-11-13 17:08 ` Paul Simmons
2020-11-15 13:36 ` Matthias Fischer [this message]
2020-11-15 14:50 ` Michael Tremer
2020-11-15 15:44 ` Tapani Tarvainen
2020-11-16 10:34 ` Michael Tremer
2020-11-23 9:08 ` Matthias Fischer
2020-12-25 16:57 ` Matthias Fischer
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=0bf6771a-5d03-762a-9244-1567dd500754@ipfire.org \
--to=matthias.fischer@ipfire.org \
--cc=development@lists.ipfire.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox