On 2024-04-28 12:59, Frank Bures wrote:
On 2024-04-28 11:39, Barry wrote:
On 28 Apr 2024, at 16:31, Frank Bures <buresf@xxxxxxxxx> wrote:
The problem is that there are no connection attempts in /var/log/secure
or /var/log/messages so obviously f2b has nothing to do.
Maybe the logs are in the journal and nothing is updating the legacy
/var/log files?
What does journalctl report?
Barry
That was it!
How do I make sshd to log to secure as before?
OK, here's the deal.
The problem has nothing to do with f2b and everything to do with EERO
update that coincided with my F40 upgrade.
The previous version of EERO firmware apparently quietly ignored its
firewall settings and let anything through. The new firmware
re-established the proper functioning firewall, hence only my pre-defined
sshd ports were left open. As no attacker hit them, there was nothing for
f2b to do.
I tested the hypothesis by opening port 22 on EERO and bang, f2b is as busy
as before.
I apologize for my hasty posting.
Cheers
Frank
--
<listfrank1@xxxxxxxxx>
--
_______________________________________________
users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx
Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
