public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: Alexander Marx <alexander.marx@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: Firewall Fix
Date: Mon, 25 Jul 2016 14:16:38 +0200	[thread overview]
Message-ID: <67060118-8e0c-d3c2-4751-285dd0d227ca@ipfire.org> (raw)
In-Reply-To: <578FAE67.5010207@ipfire.org>

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

Patch under http://patchwork.ipfire.org/patch/693/

cheers

Alex


Am 20.07.2016 um 19:01 schrieb Alexander Marx:
> sure
>
> Am 20.07.2016 um 17:32 schrieb Michael Tremer:
>> @Alex: Could you have a look at this, please?
>>
>> On Tue, 2016-07-19 at 01:45 -0500, R. W. Rodolico wrote:
>>> I was working with the firewall today and noticed the following three
>>> ports are not in the default list of ports.
>>>
>>> SUBMISSION 587 (TCP AND UDP)
>>> SSMTP      465
>>>
>>> I suggest they be added. I did a quick look and did not see where they
>>> came from for sure, but maybe
>>> /var/ipfire/fwhosts/customservices.default? If so, it looks like the
>>> following three lines added to that file would work:
>>>
>>> 35,SUBMISSION (TCP),587,TCP,BLANK,0
>>> 36,SUBMISSION (UDP),587,UDP,BLANK,0
>>> 37,SSMTP,465,TCP,BLANK,0
>>>
>>> I do NOT know what the first number is, but since it is not duplicated
>>> and is 1-number of entries, I assume it is a unique index.
>>>
>>> NOTE: I tried modifying that file on my test router and it did not 
>>> work,
>>> so that may not be the correct place.
>>>
>>> Rod
>


      reply	other threads:[~2016-07-25 12:16 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-19  6:45 R. W. Rodolico
2016-07-20 15:32 ` Michael Tremer
2016-07-20 17:01   ` Alexander Marx
2016-07-25 12:16     ` Alexander Marx [this message]

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=67060118-8e0c-d3c2-4751-285dd0d227ca@ipfire.org \
    --to=alexander.marx@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