1
24.7 Production Series / Re: Failed upgrade to 24.7
« on: September 10, 2024, 12:58:06 pm »
Allright, that makes sense. In that way I can fix the broken raid as well..
Thanks!
/k
Thanks!
/k
This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.
Version number mismatch, aborting.
Kernel: 13.2
Base: 14
KLD nullfs.ko: depends on kernel - not available or version mismatch
linker_load_file: /boot/kernel/nullfs.ko - unsupported file type
KLD nullfs.ko: depends on kernel - not available or version mismatch
linker_load_file: /boot/kernel/nullfs.ko - unsupported file type
So CrowdSec is basically a bit like the good old fail2ban with extensible and modular sources? is that it or I'm misunderstanding something?
My understanding from reading the above is that i have all I need from CrowdSec. At the firewall level bad IPs will be blocked irregardless if they are attacking the WebGUI or not. Is this correct? or is there more I need to do?
If CrowdSec ever releases a block list I will build an alias and floating rule for that as well
I had heard CrowdSec was going to release an IP blocklist of their own that OpnSense users could build an Alias for (ie Spamhaus). Ran into this on the CrowdSec website:
sudo apt install crowdsec-blocklist-mirror
Was wondering if I could Somehow build an alias? Any suggestions? It appears CrowdSec is maintaining a blocklist.
klausagnoletti: I have it up and running. Now lets see how this functions.Yes of course. It will be part of the standard opnsense repo as soon as we release port officially (that's the plan, at least).
Would be great to have this implemented in the opnsense plugins and not having to go to the terminal.
p.s. just added the crowdsec WordPress plugin (wordpress running on synology nas) and used LAPI URL: http://192.168.1.1:8080
(opnsense with crowdsec running on 192.168.1.1)
I don't think this is working. Do I have to make a fw rule for it to run or something else, e.g. how to check if it works?
In opnsense crowdsec - wordpress-bouncer showing Last Api Pull 4 hours ago (the time after the Bouncer API key creation)
Are there any ports that need to be opened for the local parser/bouncer to talk to SaaS/Crowdsec?
It all looks very interesting and promising. The crowdsec console looks like it is running online and not locally on our opnsense box? Or is it possible to have this running only locally?
And when running a wordpress site on a machine behind open sense /reverse proxy, does crowdsec protects this wordpress site or must crowdsec also been installed on this separate wordpress website server behind opnense?