Search found 14 matches
- 07 Sep 2017, 11:24
- Forum: Suggestions (csf)
- Topic: feature request - csf.deny comma separated ports?
- Replies: 1
- Views: 3305
feature request - csf.deny comma separated ports?
I want to be able to include command separated port numbers in the csf.deny file For example I have the following: tcp|in|d=80|s=89.248.160.0/21 scannerbots googlemapsexploit QUASINETWORKS SEYCHELLES - do not delete - Tue Apr 11 14:49:02 2017 And I want to block port 443 too tcp|in|d=80,443|s=89.248...
- 07 Sep 2017, 11:22
- Forum: General Discussion (csf)
- Topic: block IP range but allow individual IPs within range
- Replies: 1
- Views: 2131
block IP range but allow individual IPs within range
On a normal web server where ports 80,443 are normally open to normal web traffic, we want to block a particularly nuisance IP range (for example 46.229.160.0/20) but allow access from an individual IP within that range (for example 46.229.160.1). Is this possible? It doesn't seem to be during my te...
- 17 Jul 2017, 02:05
- Forum: General Discussion (csf)
- Topic: custom blocklist file
- Replies: 1
- Views: 2146
custom blocklist file
We want to have our own custom blocklist file at http://xxxxxxx/blocklist.txt and include it in csf.blocklists on all our servers. Is the following an acceptable format for csf.blocklists? tcp|in|d=80|s=46.229.160.0/20 # flooding ADVANCEDHOSTERS-AS NETHERLANDS - do not delete - Sat Apr 22 03:54:23 2...
- 17 Jul 2017, 02:03
- Forum: General Discussion (csf)
- Topic: csf.deny comma separated ports?
- Replies: 1
- Views: 2290
csf.deny comma separated ports?
Can I include command separated port numbers in the csf.deny file? For example I have the following: tcp|in|d=80|s=89.248.160.0/21 scannerbots googlemapsexploit QUASINETWORKS SEYCHELLES - do not delete - Tue Apr 11 14:49:02 2017 And I want to block port 443 too tcp|in|d=80,443|s=89.248.160.0/21 scan...