public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: "Peter Müller" <peter.mueller@ipfire.org>
To: development@lists.ipfire.org
Subject: Firewall rules with predefined service groups for both source and destination?
Date: Tue, 21 Jan 2020 18:22:00 +0000	[thread overview]
Message-ID: <0c2ca114-203e-a08f-3a75-b6fee134b8c9@ipfire.org> (raw)

[-- Attachment #1: Type: text/plain, Size: 1015 bytes --]

Hello *,

since I am not sure whether I am dealing with a bug, a missing feature
or my very own personal incompetence, asking the mailing list seemed
reasonable for this. :-)

For security purposes, dropping packets from source ports < 1024 is a good
idea as the latter indicates successful compromise of services running on
privileged ports. New connections are usually established from ports > 1023,
so there is little legitimate scope for this if in doubt.

When creating a firewall rule via the WebIF, it does not seem to be possible
to limit source _and_ destination ports if a predefined service (group) is
used - the latter one always refers to the destination port(s).

As soon as a single protocol such as TCP or UDP is selected, however, a field
"source port" is available.

Is this behaviour intentional? If yes, how do I limit firewall rules to
certain source ports then? Aren't the descriptions "service" and "service group"
misleading?

Thanks, and best regards,
Peter Müller

             reply	other threads:[~2020-01-21 18:22 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-21 18:22 Peter Müller [this message]
2020-01-24 11:43 ` Michael Tremer
2020-01-25 16:41   ` Peter Müller
2020-01-26 20:43     ` Michael Tremer
2020-01-27  7:53   ` Tapani Tarvainen
2020-01-27 10:01     ` 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=0c2ca114-203e-a08f-3a75-b6fee134b8c9@ipfire.org \
    --to=peter.mueller@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