OK, I have the engine and bouncer up and running.
According to the Post Installation guide, the following command should tell me what log sources are already detected,
cscli metrics show acquisition
The only output I get is
ATA[2025-01-19T03:39:27Z] accepts 0 arg(s), received 2
When I run, opkg install crowdsec, I get
Package crowdsec (1.6.0-1) installed in root is up to date.
But I get a message in the Console saying v1.6.4 available with a link !
Late reply, but sharing my experience for those who stumble upon this post in the future.
I have crowdsec up an running on my OpenWRT for a couple of months now, and it has been working great for me. But seeing OP emphasizing being a novice, I think I will start with some quick concepts that I have picked up since I started using crowdsec:
Two main components - the crowdsec engine and the crowdsec bouncer.
Crowdsec Engine - The component used to store blocklists from app.crowdsec.net, plus detection features to generate and store blocklists from intrusion attempts to your own services.
Crowdsec Bouncer - The component to actually block attempts to connect to your network based on blocklists stored in your engine.
For me, I ended up configuring only my bouncer on Openwrt. It works flawlessly and data gets fetched from my crowdsec engine running on my Synology NAS that runs a mail server.
So my Engine subscribes to four public blocklists from crowdsec, and it also generates 2 additional blocklists based on the log file from my mail server. These blocklists all go to my crowdsec bouncer running on my Openwrt gateway router to block malicious attempts to enter my network.
Simple as that (concept wise). As to how to set things up, it took me quite some time to configure and fine tune my engine, but bouncer setup on Openwrt was pretty straightforward.
When I run cscli metrics show acquisition on my engine, I get something like this: