TCP_OUT: One colon too much

[e-it]

Hello,

If I configure TCP OUT as string = 20,21,22,25,53,80,110,143,443,465,587,993,995

the generated config is the following:

# Allow outgoing TCP ports
TCP_OUT = "20,21,22,25,53,80,110,143,443,465,587,993,995,"

Isn't there a colon too much?

[cleverlight]

Yes but it doesn't matter.

On Wed, 13 Apr 2016, 08:25 SPQRInc, notifications@github.com wrote:

Hello,

If I configure TCP OUT as string =
20,21,22,25,53,80,110,143,443,465,587,993,995

the generated config is the following:

Allow outgoing TCP ports

TCP_OUT = "20,21,22,25,53,80,110,143,443,465,587,993,995,"

Isn't there a colon too much?

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub
#4

[e-it]

Thanks for your reply.

Okay, good to know.

My problem is, that csf always closes port 22 after the first connection attempt.

root@updates:/# nmap example.com -p 22

Starting Nmap 6.00 ( http://nmap.org ) at 2016-04-13 10:24 CEST
Nmap scan report for example.com (xxx.xxx.xxx.xxx)
Host is up (0.00039s latency).
PORT   STATE SERVICE
22/tcp open  ssh
MAC Address: 32:32:39:34:62:39 (Unknown)

Nmap done: 1 IP address (1 host up) scanned in 0.11 seconds
root@updates:/# ssh example.com
^C
root@updates:/home/rlb# nmap example.com -p 22

Starting Nmap 6.00 ( http://nmap.org ) at 2016-04-13 10:25 CEST
Nmap scan report for example.com (xxx.xxx.xxx.xxx)
Host is up (0.00032s latency).
PORT   STATE    SERVICE
22/tcp filtered ssh
MAC Address: 32:32:39:34:62:39 (Unknown)

Nmap done: 1 IP address (1 host up) scanned in 0.30 seconds
root@updates:/# 

My first thought was that there is a configuration error - but if this is not the case this module seems not to be the problem.

[cleverlight]

You might have better luck posting to the CSF forums about that. I reckon
it's not within the scope of this puppet module.

On Wed, 13 Apr 2016, 09:26 SPQRInc, notifications@github.com wrote:

Thanks for your reply.

Okay, good to know.

My problem is, that csf always closes port 22 after the first connection
attempt.

root@updates:/# nmap example.com -p 22

Starting Nmap 6.00 ( http://nmap.org ) at 2016-04-13 10:24 CEST
Nmap scan report for example.com (xxx.xxx.xxx.xxx)
Host is up (0.00039s latency).
PORT STATE SERVICE
22/tcp open ssh
MAC Address: 32:32:39:34:62:39 (Unknown)

Nmap done: 1 IP address (1 host up) scanned in 0.11 seconds
root@updates:/# ssh example.com
^C
root@updates:/home/rlb# nmap example.com -p 22

Starting Nmap 6.00 ( http://nmap.org ) at 2016-04-13 10:25 CEST
Nmap scan report for example.com (xxx.xxx.xxx.xxx)
Host is up (0.00032s latency).
PORT STATE SERVICE
22/tcp filtered ssh
MAC Address: 32:32:39:34:62:39 (Unknown)

Nmap done: 1 IP address (1 host up) scanned in 0.30 seconds
root@updates:/#

My first thought was that there is a configuration error - but if this is
not the case this module seems not to be the problem.

—
You are receiving this because you commented.

Reply to this email directly or view it on GitHub
#4 (comment)