From: Michael Tremer <michael.tremer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: [PATCH] unbound: Update to 1.9.0
Date: Tue, 26 Feb 2019 09:54:00 +0000 [thread overview]
Message-ID: <389F1C8C-1ADE-48AE-91FD-A622C832EDEF@ipfire.org> (raw)
In-Reply-To: <d8be5cd8-0641-dd9d-979c-7420dfee8e7a@ipfire.org>
[-- Attachment #1: Type: text/plain, Size: 1560 bytes --]
Hi,
I have just merged this patch into next for c129.
-Michael
> On 15 Feb 2019, at 16:48, Matthias Fischer <matthias.fischer(a)ipfire.org> wrote:
>
> On 15.02.2019 12:34, Michael Tremer wrote:
>> On 14 Feb 2019, at 17:26, Matthias Fischer <matthias.fischer(a)ipfire.org> wrote:
>>>
>>> Hi Michael,
>>>
>>> On 14.02.2019 12:01, Michael Tremer wrote:
>>>>>> I did *not* merge this one, yet.
>>>>> No problem - I'm in touch with Erik trying to help testing TFO and DoT.
>>>> Please don’t forget to share what you are doing on this list
>>>
>>> Of course. ;-)
>>>
>>> So far, I got the same results as Erik. But my test environment is not
>>> as extensive as his.
>>>
>>> One important result for me: the iptables rules to prevent dns hijacking
>>> are still working.
>>
>> The ones for the captive portal? Or did you have any custom rules?
>
> I use custom rules in 'firewall.local'
> (Inspired by https://blog.ipfire.org/post/use-ipfire-to-protect-you-from-dnschanger):
>
> ***SNIP***
> sbin/iptables -t nat -A CUSTOMPREROUTING -i green0 -p udp --dport 53 -j DNAT --to 192.168.100.254:53
>
> /sbin/iptables -t nat -A CUSTOMPREROUTING -i green0 -p tcp --dport 53 -j DNAT --to 192.168.100.254:53
>
> /sbin/iptables -t nat -A CUSTOMPREROUTING -i blue0 -p udp --dport 53 -j DNAT --to 192.168.101.254:53
>
> /sbin/iptables -t nat -A CUSTOMPREROUTING -i blue0 -p tcp --dport 53 -j DNAT --to 192.168.101.254:53
> ***SNAP***
>
> I'm still testing testing under various conditions.
>
> Best,
> Matthias
next prev parent reply other threads:[~2019-02-26 9:54 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-09 9:40 Matthias Fischer
2019-02-13 17:32 ` Michael Tremer
2019-02-14 7:05 ` Matthias Fischer
2019-02-14 11:01 ` Michael Tremer
2019-02-14 17:26 ` Matthias Fischer
2019-02-15 11:34 ` Michael Tremer
2019-02-15 16:48 ` Matthias Fischer
2019-02-26 9:54 ` Michael Tremer [this message]
2019-02-15 13:12 ` ummeegge
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=389F1C8C-1ADE-48AE-91FD-A622C832EDEF@ipfire.org \
--to=michael.tremer@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