blacklistd not blocking addresses

Clash Royale CLAN TAG#URR8PPP
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty margin-bottom:0;
I've enabled the PF(4) firewall and blacklistd(8). Although IP addresses are being added to to blacklist, I can still see multiple failed attempts from a single IP address. Yet when I test it myself, my IP address gets blacklisted properly: it's added to the blacklist and I can't initiate any more connections from it.
/etc/rc.conf:
blacklistd_enable="YES"
pf_enable="YES"
/etc/blacklistd.conf:
# adr/mask:port type proto owner name nfail disable
[local]
ssh stream * * * 1 365d
# Extra lines removed
/etc/ssh/sshd_config:
...
UseBlacklist Yes
...
/etc/pf.conf:
intf="wlan0"
set skip on lo0, em0
# Packet normalization
scrub in
# Integrate blacklistd to protect sshd
anchor "blacklistd/*" in on $intf
### FIREWALL RULES
# Default firewall rules
block in
pass out
# Allow inbound SSH on the default port (22)
pass in on $intf proto tcp to ($intf) port 22
# Allow basic ICMP functionality
pass in on $intf inet proto icmp to ($intf) icmp-type unreach, redir, timex, echoreq
grep sshd /var/log/messages | tail -20
Mar 2 00:21:11 [...] illegal user admin from 120.92.147.56
Mar 2 00:21:30 [...] illegal user alix from 120.92.147.56
Mar 2 00:21:51 [...] illegal user gotubego from 120.92.147.56
Mar 2 00:23:35 [...] illegal user tsbot from 120.92.147.56
Mar 2 00:23:40 [...] illegal user spravce from 120.92.147.56
Mar 2 00:25:34 [...] root from 120.92.147.56
Mar 2 00:25:57 [...] illegal user admin from 120.92.147.56
Mar 2 00:27:29 [...] illegal user admin from 120.92.147.56
Mar 2 00:29:13 [...] root from 120.92.147.56
Mar 2 00:30:06 [...] root from 120.92.147.56
Mar 2 00:33:09 [...] illegal user admin from 120.92.147.56
Mar 2 00:33:23 [...] illegal user admin from 120.92.147.56
Mar 2 00:34:15 [...] illegal user bogalfb from 120.92.147.56
Mar 2 00:35:34 [...] root from 120.92.147.56
Mar 2 00:35:59 [...] illegal user admin from 120.92.147.56
Mar 3 13:35:35 [...] illegal user user from 103.200.23.124
Mar 4 19:47:59 [...] root from 111.207.23.140
Mar 5 02:09:39 [...] illegal user user from host2.awolphoto.com
Mar 5 16:02:33 [...] illegal user user from 103.221.221.189
Mar 7 04:43:38 [...] illegal user user from server28.pixeled.net
I've truncated the lines for readability. The entire first lines reads as:
Mar 2 00:21:11 phoenix sshd[94473]: error: PAM: authentication error for illegal user admin from 120.92.147.56
I've deleted the unuseful bits.
sudo blacklistctl dump -br
150.95.156.167/32:22 OK 2/1 1y3d22h45m57s
27.79.178.252/32:22 OK 2/1 1y3d29h16m55s
194.61.24.162/32:22 OK 40/1 20d2h19m32s
76.242.160.219/32:22 OK 2/1 22d42h8m58s
91.121.173.184/32:22 OK 2/1 2d12h1m40s
116.127.174.152/32:22 OK 2/1 7d34h39m45s
88.214.26.49/32:22 OK 62/1 9d11h56m22s
...
The list contains 1069 entries but not the IP address 120.92.147.56.
Questions
- Some IP addresses time out in (more) a year (as they should) while others time out in only a couple of days (e.g. 2 days).
- Some IP addresses (e.g.
120.92.147.56) are not added to the list while they clearly should be. - Some addresses could execute as much as 62 attempts before being blocked in the list.
What am I missing in my configuration to make it work as desired?
freebsd bsd pf
add a comment |
I've enabled the PF(4) firewall and blacklistd(8). Although IP addresses are being added to to blacklist, I can still see multiple failed attempts from a single IP address. Yet when I test it myself, my IP address gets blacklisted properly: it's added to the blacklist and I can't initiate any more connections from it.
/etc/rc.conf:
blacklistd_enable="YES"
pf_enable="YES"
/etc/blacklistd.conf:
# adr/mask:port type proto owner name nfail disable
[local]
ssh stream * * * 1 365d
# Extra lines removed
/etc/ssh/sshd_config:
...
UseBlacklist Yes
...
/etc/pf.conf:
intf="wlan0"
set skip on lo0, em0
# Packet normalization
scrub in
# Integrate blacklistd to protect sshd
anchor "blacklistd/*" in on $intf
### FIREWALL RULES
# Default firewall rules
block in
pass out
# Allow inbound SSH on the default port (22)
pass in on $intf proto tcp to ($intf) port 22
# Allow basic ICMP functionality
pass in on $intf inet proto icmp to ($intf) icmp-type unreach, redir, timex, echoreq
grep sshd /var/log/messages | tail -20
Mar 2 00:21:11 [...] illegal user admin from 120.92.147.56
Mar 2 00:21:30 [...] illegal user alix from 120.92.147.56
Mar 2 00:21:51 [...] illegal user gotubego from 120.92.147.56
Mar 2 00:23:35 [...] illegal user tsbot from 120.92.147.56
Mar 2 00:23:40 [...] illegal user spravce from 120.92.147.56
Mar 2 00:25:34 [...] root from 120.92.147.56
Mar 2 00:25:57 [...] illegal user admin from 120.92.147.56
Mar 2 00:27:29 [...] illegal user admin from 120.92.147.56
Mar 2 00:29:13 [...] root from 120.92.147.56
Mar 2 00:30:06 [...] root from 120.92.147.56
Mar 2 00:33:09 [...] illegal user admin from 120.92.147.56
Mar 2 00:33:23 [...] illegal user admin from 120.92.147.56
Mar 2 00:34:15 [...] illegal user bogalfb from 120.92.147.56
Mar 2 00:35:34 [...] root from 120.92.147.56
Mar 2 00:35:59 [...] illegal user admin from 120.92.147.56
Mar 3 13:35:35 [...] illegal user user from 103.200.23.124
Mar 4 19:47:59 [...] root from 111.207.23.140
Mar 5 02:09:39 [...] illegal user user from host2.awolphoto.com
Mar 5 16:02:33 [...] illegal user user from 103.221.221.189
Mar 7 04:43:38 [...] illegal user user from server28.pixeled.net
I've truncated the lines for readability. The entire first lines reads as:
Mar 2 00:21:11 phoenix sshd[94473]: error: PAM: authentication error for illegal user admin from 120.92.147.56
I've deleted the unuseful bits.
sudo blacklistctl dump -br
150.95.156.167/32:22 OK 2/1 1y3d22h45m57s
27.79.178.252/32:22 OK 2/1 1y3d29h16m55s
194.61.24.162/32:22 OK 40/1 20d2h19m32s
76.242.160.219/32:22 OK 2/1 22d42h8m58s
91.121.173.184/32:22 OK 2/1 2d12h1m40s
116.127.174.152/32:22 OK 2/1 7d34h39m45s
88.214.26.49/32:22 OK 62/1 9d11h56m22s
...
The list contains 1069 entries but not the IP address 120.92.147.56.
Questions
- Some IP addresses time out in (more) a year (as they should) while others time out in only a couple of days (e.g. 2 days).
- Some IP addresses (e.g.
120.92.147.56) are not added to the list while they clearly should be. - Some addresses could execute as much as 62 attempts before being blocked in the list.
What am I missing in my configuration to make it work as desired?
freebsd bsd pf
From readingblacklistd.conf(5), it looks like the first field on the line in theblacklistd.conffile should be prefixed by:if it's to be taken as a port. I'm not on FreeBSD so I can't test this though. You may want to test with:sshorwlan0:ssh.
– Kusalananda♦
Mar 8 at 10:32
I could give that a try. I copied it from Absolute FreeBSD, 3rd edition without the colon and it appears to work most of the time. It's adding IP addresses to the blocked list and when I test it, it blocks me correctly.
– Tommiie
Mar 8 at 11:07
Yeah, it's the only thing that stood out for me. I can't say anything more really.
– Kusalananda♦
Mar 8 at 11:20
add a comment |
I've enabled the PF(4) firewall and blacklistd(8). Although IP addresses are being added to to blacklist, I can still see multiple failed attempts from a single IP address. Yet when I test it myself, my IP address gets blacklisted properly: it's added to the blacklist and I can't initiate any more connections from it.
/etc/rc.conf:
blacklistd_enable="YES"
pf_enable="YES"
/etc/blacklistd.conf:
# adr/mask:port type proto owner name nfail disable
[local]
ssh stream * * * 1 365d
# Extra lines removed
/etc/ssh/sshd_config:
...
UseBlacklist Yes
...
/etc/pf.conf:
intf="wlan0"
set skip on lo0, em0
# Packet normalization
scrub in
# Integrate blacklistd to protect sshd
anchor "blacklistd/*" in on $intf
### FIREWALL RULES
# Default firewall rules
block in
pass out
# Allow inbound SSH on the default port (22)
pass in on $intf proto tcp to ($intf) port 22
# Allow basic ICMP functionality
pass in on $intf inet proto icmp to ($intf) icmp-type unreach, redir, timex, echoreq
grep sshd /var/log/messages | tail -20
Mar 2 00:21:11 [...] illegal user admin from 120.92.147.56
Mar 2 00:21:30 [...] illegal user alix from 120.92.147.56
Mar 2 00:21:51 [...] illegal user gotubego from 120.92.147.56
Mar 2 00:23:35 [...] illegal user tsbot from 120.92.147.56
Mar 2 00:23:40 [...] illegal user spravce from 120.92.147.56
Mar 2 00:25:34 [...] root from 120.92.147.56
Mar 2 00:25:57 [...] illegal user admin from 120.92.147.56
Mar 2 00:27:29 [...] illegal user admin from 120.92.147.56
Mar 2 00:29:13 [...] root from 120.92.147.56
Mar 2 00:30:06 [...] root from 120.92.147.56
Mar 2 00:33:09 [...] illegal user admin from 120.92.147.56
Mar 2 00:33:23 [...] illegal user admin from 120.92.147.56
Mar 2 00:34:15 [...] illegal user bogalfb from 120.92.147.56
Mar 2 00:35:34 [...] root from 120.92.147.56
Mar 2 00:35:59 [...] illegal user admin from 120.92.147.56
Mar 3 13:35:35 [...] illegal user user from 103.200.23.124
Mar 4 19:47:59 [...] root from 111.207.23.140
Mar 5 02:09:39 [...] illegal user user from host2.awolphoto.com
Mar 5 16:02:33 [...] illegal user user from 103.221.221.189
Mar 7 04:43:38 [...] illegal user user from server28.pixeled.net
I've truncated the lines for readability. The entire first lines reads as:
Mar 2 00:21:11 phoenix sshd[94473]: error: PAM: authentication error for illegal user admin from 120.92.147.56
I've deleted the unuseful bits.
sudo blacklistctl dump -br
150.95.156.167/32:22 OK 2/1 1y3d22h45m57s
27.79.178.252/32:22 OK 2/1 1y3d29h16m55s
194.61.24.162/32:22 OK 40/1 20d2h19m32s
76.242.160.219/32:22 OK 2/1 22d42h8m58s
91.121.173.184/32:22 OK 2/1 2d12h1m40s
116.127.174.152/32:22 OK 2/1 7d34h39m45s
88.214.26.49/32:22 OK 62/1 9d11h56m22s
...
The list contains 1069 entries but not the IP address 120.92.147.56.
Questions
- Some IP addresses time out in (more) a year (as they should) while others time out in only a couple of days (e.g. 2 days).
- Some IP addresses (e.g.
120.92.147.56) are not added to the list while they clearly should be. - Some addresses could execute as much as 62 attempts before being blocked in the list.
What am I missing in my configuration to make it work as desired?
freebsd bsd pf
I've enabled the PF(4) firewall and blacklistd(8). Although IP addresses are being added to to blacklist, I can still see multiple failed attempts from a single IP address. Yet when I test it myself, my IP address gets blacklisted properly: it's added to the blacklist and I can't initiate any more connections from it.
/etc/rc.conf:
blacklistd_enable="YES"
pf_enable="YES"
/etc/blacklistd.conf:
# adr/mask:port type proto owner name nfail disable
[local]
ssh stream * * * 1 365d
# Extra lines removed
/etc/ssh/sshd_config:
...
UseBlacklist Yes
...
/etc/pf.conf:
intf="wlan0"
set skip on lo0, em0
# Packet normalization
scrub in
# Integrate blacklistd to protect sshd
anchor "blacklistd/*" in on $intf
### FIREWALL RULES
# Default firewall rules
block in
pass out
# Allow inbound SSH on the default port (22)
pass in on $intf proto tcp to ($intf) port 22
# Allow basic ICMP functionality
pass in on $intf inet proto icmp to ($intf) icmp-type unreach, redir, timex, echoreq
grep sshd /var/log/messages | tail -20
Mar 2 00:21:11 [...] illegal user admin from 120.92.147.56
Mar 2 00:21:30 [...] illegal user alix from 120.92.147.56
Mar 2 00:21:51 [...] illegal user gotubego from 120.92.147.56
Mar 2 00:23:35 [...] illegal user tsbot from 120.92.147.56
Mar 2 00:23:40 [...] illegal user spravce from 120.92.147.56
Mar 2 00:25:34 [...] root from 120.92.147.56
Mar 2 00:25:57 [...] illegal user admin from 120.92.147.56
Mar 2 00:27:29 [...] illegal user admin from 120.92.147.56
Mar 2 00:29:13 [...] root from 120.92.147.56
Mar 2 00:30:06 [...] root from 120.92.147.56
Mar 2 00:33:09 [...] illegal user admin from 120.92.147.56
Mar 2 00:33:23 [...] illegal user admin from 120.92.147.56
Mar 2 00:34:15 [...] illegal user bogalfb from 120.92.147.56
Mar 2 00:35:34 [...] root from 120.92.147.56
Mar 2 00:35:59 [...] illegal user admin from 120.92.147.56
Mar 3 13:35:35 [...] illegal user user from 103.200.23.124
Mar 4 19:47:59 [...] root from 111.207.23.140
Mar 5 02:09:39 [...] illegal user user from host2.awolphoto.com
Mar 5 16:02:33 [...] illegal user user from 103.221.221.189
Mar 7 04:43:38 [...] illegal user user from server28.pixeled.net
I've truncated the lines for readability. The entire first lines reads as:
Mar 2 00:21:11 phoenix sshd[94473]: error: PAM: authentication error for illegal user admin from 120.92.147.56
I've deleted the unuseful bits.
sudo blacklistctl dump -br
150.95.156.167/32:22 OK 2/1 1y3d22h45m57s
27.79.178.252/32:22 OK 2/1 1y3d29h16m55s
194.61.24.162/32:22 OK 40/1 20d2h19m32s
76.242.160.219/32:22 OK 2/1 22d42h8m58s
91.121.173.184/32:22 OK 2/1 2d12h1m40s
116.127.174.152/32:22 OK 2/1 7d34h39m45s
88.214.26.49/32:22 OK 62/1 9d11h56m22s
...
The list contains 1069 entries but not the IP address 120.92.147.56.
Questions
- Some IP addresses time out in (more) a year (as they should) while others time out in only a couple of days (e.g. 2 days).
- Some IP addresses (e.g.
120.92.147.56) are not added to the list while they clearly should be. - Some addresses could execute as much as 62 attempts before being blocked in the list.
What am I missing in my configuration to make it work as desired?
freebsd bsd pf
freebsd bsd pf
edited Mar 8 at 10:13
Tommiie
asked Mar 8 at 10:00
TommiieTommiie
148110
148110
From readingblacklistd.conf(5), it looks like the first field on the line in theblacklistd.conffile should be prefixed by:if it's to be taken as a port. I'm not on FreeBSD so I can't test this though. You may want to test with:sshorwlan0:ssh.
– Kusalananda♦
Mar 8 at 10:32
I could give that a try. I copied it from Absolute FreeBSD, 3rd edition without the colon and it appears to work most of the time. It's adding IP addresses to the blocked list and when I test it, it blocks me correctly.
– Tommiie
Mar 8 at 11:07
Yeah, it's the only thing that stood out for me. I can't say anything more really.
– Kusalananda♦
Mar 8 at 11:20
add a comment |
From readingblacklistd.conf(5), it looks like the first field on the line in theblacklistd.conffile should be prefixed by:if it's to be taken as a port. I'm not on FreeBSD so I can't test this though. You may want to test with:sshorwlan0:ssh.
– Kusalananda♦
Mar 8 at 10:32
I could give that a try. I copied it from Absolute FreeBSD, 3rd edition without the colon and it appears to work most of the time. It's adding IP addresses to the blocked list and when I test it, it blocks me correctly.
– Tommiie
Mar 8 at 11:07
Yeah, it's the only thing that stood out for me. I can't say anything more really.
– Kusalananda♦
Mar 8 at 11:20
From reading
blacklistd.conf(5), it looks like the first field on the line in the blacklistd.conf file should be prefixed by : if it's to be taken as a port. I'm not on FreeBSD so I can't test this though. You may want to test with :ssh or wlan0:ssh.– Kusalananda♦
Mar 8 at 10:32
From reading
blacklistd.conf(5), it looks like the first field on the line in the blacklistd.conf file should be prefixed by : if it's to be taken as a port. I'm not on FreeBSD so I can't test this though. You may want to test with :ssh or wlan0:ssh.– Kusalananda♦
Mar 8 at 10:32
I could give that a try. I copied it from Absolute FreeBSD, 3rd edition without the colon and it appears to work most of the time. It's adding IP addresses to the blocked list and when I test it, it blocks me correctly.
– Tommiie
Mar 8 at 11:07
I could give that a try. I copied it from Absolute FreeBSD, 3rd edition without the colon and it appears to work most of the time. It's adding IP addresses to the blocked list and when I test it, it blocks me correctly.
– Tommiie
Mar 8 at 11:07
Yeah, it's the only thing that stood out for me. I can't say anything more really.
– Kusalananda♦
Mar 8 at 11:20
Yeah, it's the only thing that stood out for me. I can't say anything more really.
– Kusalananda♦
Mar 8 at 11:20
add a comment |
1 Answer
1
active
oldest
votes
My configuration is pretty much the same and I can't see any sshd "... illegal user ..." in /var/log/messages
The only differences are in my rc.conf
blacklistd_flags="-r"
and in pf.conf. Instead of
pass in on $intf proto tcp to ($intf) port 22
you might consider this one
pass in on $intf proto tcp from any to any port ssh flags S/SA synproxy state
FWIW. To make the configuration reproducible I use my Ansible role
Notes
Entry "88.214.26.49/32:22 OK 62/1 9d11h56m22s" looks suspicious. Should have been blacklisted after 1st failure. How did it manage to fail 62 times?
Entry "194.61.24.162/32:22 OK 40/1 20d2h19m32s" dtto
You configured to disable for "365d", but the entries above show remaining times in couple of days. Have these entries really been blacklisted over 11 months?
add a comment |
Your Answer
StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "106"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);
else
createEditor();
);
function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader:
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
,
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);
);
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f505096%2fblacklistd-not-blocking-addresses%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
My configuration is pretty much the same and I can't see any sshd "... illegal user ..." in /var/log/messages
The only differences are in my rc.conf
blacklistd_flags="-r"
and in pf.conf. Instead of
pass in on $intf proto tcp to ($intf) port 22
you might consider this one
pass in on $intf proto tcp from any to any port ssh flags S/SA synproxy state
FWIW. To make the configuration reproducible I use my Ansible role
Notes
Entry "88.214.26.49/32:22 OK 62/1 9d11h56m22s" looks suspicious. Should have been blacklisted after 1st failure. How did it manage to fail 62 times?
Entry "194.61.24.162/32:22 OK 40/1 20d2h19m32s" dtto
You configured to disable for "365d", but the entries above show remaining times in couple of days. Have these entries really been blacklisted over 11 months?
add a comment |
My configuration is pretty much the same and I can't see any sshd "... illegal user ..." in /var/log/messages
The only differences are in my rc.conf
blacklistd_flags="-r"
and in pf.conf. Instead of
pass in on $intf proto tcp to ($intf) port 22
you might consider this one
pass in on $intf proto tcp from any to any port ssh flags S/SA synproxy state
FWIW. To make the configuration reproducible I use my Ansible role
Notes
Entry "88.214.26.49/32:22 OK 62/1 9d11h56m22s" looks suspicious. Should have been blacklisted after 1st failure. How did it manage to fail 62 times?
Entry "194.61.24.162/32:22 OK 40/1 20d2h19m32s" dtto
You configured to disable for "365d", but the entries above show remaining times in couple of days. Have these entries really been blacklisted over 11 months?
add a comment |
My configuration is pretty much the same and I can't see any sshd "... illegal user ..." in /var/log/messages
The only differences are in my rc.conf
blacklistd_flags="-r"
and in pf.conf. Instead of
pass in on $intf proto tcp to ($intf) port 22
you might consider this one
pass in on $intf proto tcp from any to any port ssh flags S/SA synproxy state
FWIW. To make the configuration reproducible I use my Ansible role
Notes
Entry "88.214.26.49/32:22 OK 62/1 9d11h56m22s" looks suspicious. Should have been blacklisted after 1st failure. How did it manage to fail 62 times?
Entry "194.61.24.162/32:22 OK 40/1 20d2h19m32s" dtto
You configured to disable for "365d", but the entries above show remaining times in couple of days. Have these entries really been blacklisted over 11 months?
My configuration is pretty much the same and I can't see any sshd "... illegal user ..." in /var/log/messages
The only differences are in my rc.conf
blacklistd_flags="-r"
and in pf.conf. Instead of
pass in on $intf proto tcp to ($intf) port 22
you might consider this one
pass in on $intf proto tcp from any to any port ssh flags S/SA synproxy state
FWIW. To make the configuration reproducible I use my Ansible role
Notes
Entry "88.214.26.49/32:22 OK 62/1 9d11h56m22s" looks suspicious. Should have been blacklisted after 1st failure. How did it manage to fail 62 times?
Entry "194.61.24.162/32:22 OK 40/1 20d2h19m32s" dtto
You configured to disable for "365d", but the entries above show remaining times in couple of days. Have these entries really been blacklisted over 11 months?
edited Mar 8 at 15:33
answered Mar 8 at 15:06
Vladimir BotkaVladimir Botka
26818
26818
add a comment |
add a comment |
Thanks for contributing an answer to Unix & Linux Stack Exchange!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f505096%2fblacklistd-not-blocking-addresses%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
From reading
blacklistd.conf(5), it looks like the first field on the line in theblacklistd.conffile should be prefixed by:if it's to be taken as a port. I'm not on FreeBSD so I can't test this though. You may want to test with:sshorwlan0:ssh.– Kusalananda♦
Mar 8 at 10:32
I could give that a try. I copied it from Absolute FreeBSD, 3rd edition without the colon and it appears to work most of the time. It's adding IP addresses to the blocked list and when I test it, it blocks me correctly.
– Tommiie
Mar 8 at 11:07
Yeah, it's the only thing that stood out for me. I can't say anything more really.
– Kusalananda♦
Mar 8 at 11:20