From: "Peter Müller" <peter.mueller@link38.eu>
To: development@lists.ipfire.org
Subject: Re: Forward default "DROP" is not applied to ORANGE traffic?!
Date: Fri, 04 Jan 2019 22:12:31 +0100 [thread overview]
Message-ID: <5f24d29f-b012-4926-875d-8cf8bfbadc65@link38.eu> (raw)
In-Reply-To: <6e465ff2-a0e2-2a9c-8d49-82524459724b@link38.eu>
[-- Attachment #1: Type: text/plain, Size: 2843 bytes --]
Hello Michael,
just a quick reminder on this. :-) I know it's still the very beginning
of the year...
If there are any questions, please drop me a line.
Thanks, and best regards,
Peter Müller
> Hello Michael,
>
> sorry for the late reply.
>
> I will send you the output of "iptables -L -n -v" directly.
>
> So far, I am able to reproduce this issue on two machines
> (both with default policy set to DROP). In both cases, adding
> a rule with source = ORANGE, destination = RED and action = DROP
> to the end of the firewall ruleset in the WebUI solved the
> problem.
>
> So far, it seems like ORANGE is affected by this only.
>
> Thanks, and best regards,
> Peter Müller
>
>> Hey,
>>
>> Could you dump the generated iptables ruleset?
>>
>> I do not see anything that could potentially be a problem here that is causing your behaviour:
>>
>> https://git.ipfire.org/?p=ipfire-2.x.git;a=blob;f=config/firewall/firewall-policy;h=078c3c515c31f1f385a2159f83fb5c6c52f5e89f;hb=HEAD
>>
>> -Michael
>>
>>> On 15 Dec 2018, at 16:36, Peter Müller <peter.mueller(a)link38.eu> wrote:
>>>
>>> Hello list,
>>>
>>> I recently stumbled across a strange behaviour of IPFire 2.x, which
>>> seems to be quite critical in my eyes, but I am not sure whether it is
>>> intentional or not.
>>>
>>> Default settings of IPFire allow traffic from internal networks
>>> (GREEN, BLUE, ORANGE) to the internet (RED), as documented here:
>>> https://wiki.ipfire.org/configuration/firewall/default-policy
>>>
>>> For several reasons, no direct internet access is desired on most
>>> firewall installations I administer, so setting the "default firewall
>>> behaviour" to DROP for both FORWARD and OUTGOING usually is one of
>>> the first steps after installation.
>>>
>>> Speaking about GREEN and BLUE, this seems to work: No direct connection
>>> is possible except it has been explicitly allowed.
>>>
>>> It turns out this setting does not apply to traffic from ORANGE: Even
>>> default is set to DROP, and no firewall rules allowing anything are
>>> in place, a server located in DMZ is able to reach full internet -
>>> every port on every IP in every country.
>>>
>>> This is not my expectation of "default policy" = DROP after all!
>>>
>>> Could somebody of the core developers urgently have a look at this, please?
>>>
>>> Thanks, and best regards,
>>> Peter Müller
>>> --
>>> Microsoft DNS service terminates abnormally when it recieves a response
>>> to a DNS query that was never made. Fix Information: Run your DNS
>>> service on a different platform.
>>> -- bugtraq
>>
>
--
Microsoft DNS service terminates abnormally when it recieves a response
to a DNS query that was never made. Fix Information: Run your DNS
service on a different platform.
-- bugtraq
next prev parent reply other threads:[~2019-01-04 21:12 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-15 16:36 Peter Müller
2018-12-16 13:53 ` Michael Tremer
2018-12-16 17:07 ` oliver.fuhrer
2018-12-23 15:31 ` Peter Müller
2019-01-04 21:12 ` Peter Müller [this message]
2019-01-05 12:51 ` Michael Tremer
2019-01-06 10:41 ` Peter Müller
2019-01-07 12:57 ` Michael Tremer
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=5f24d29f-b012-4926-875d-8cf8bfbadc65@link38.eu \
--to=peter.mueller@link38.eu \
--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