Crowdsec packages for OpenWrt

plikmuny · 2022-01-18T22:42:09.413Z

here you go

src/gz openwrt_core http://downloads.openwrt.org/releases/21.02-SNAPSHOT/targets/bcm27xx/bcm2711/packages
src/gz openwrt_base http://downloads.openwrt.org/releases/21.02-SNAPSHOT/packages/aarch64_cortex-a72/base
src/gz openwrt_kmods http://downloads.openwrt.org/releases/21.02-SNAPSHOT/targets/bcm27xx/bcm2711/kmods/5.4.171-1-0788d83a1525da40e4d0f7b1f5d6ee0e
src/gz openwrt_packages http://downloads.openwrt.org/releases/21.02-SNAPSHOT/packages/aarch64_cortex-a72/packages
src/gz openwrt_luci http://downloads.openwrt.org/releases/21.02-SNAPSHOT/packages/aarch64_cortex-a72/luci
src/gz openwrt_routing http://downloads.openwrt.org/releases/21.02-SNAPSHOT/packages/aarch64_cortex-a72/routing
src/gz openwrt_telephony http://downloads.openwrt.org/releases/21.02-SNAPSHOT/packages/aarch64_cortex-a72/telephony
src/gz openwrt_core http://downloads.openwrt.org/releases/21.02-SNAPSHOT/targets/bcm27xx/bcm2711/packages
src/gz openwrt_base http://downloads.openwrt.org/releases/21.02-SNAPSHOT/packages/aarch64_cortex-a72/base
src/gz openwrt_kmods http://downloads.openwrt.org/releases/21.02-SNAPSHOT/targets/bcm27xx/bcm2711/kmods/5.4.171-1-0788d83a1525da40e4d0f7b1f5d6ee0e
src/gz openwrt_packages http://downloads.openwrt.org/releases/21.02-SNAPSHOT/packages/aarch64_cortex-a72/packages
src/gz openwrt_luci http://downloads.openwrt.org/releases/21.02-SNAPSHOT/packages/aarch64_cortex-a72/luci
src/gz openwrt_routing http://downloads.openwrt.org/releases/21.02-SNAPSHOT/packages/aarch64_cortex-a72/routing
src/gz openwrt_telephony http://downloads.openwrt.org/releases/21.02-SNAPSHOT/packages/aarch64_cortex-a72/telephony

i feel my cs-firewall-bouncer is not working. i dont see a sign that its working. can you tell me how to check whether it is working or not ? if not how can i install cs-nginx-bouncer ???

erdoukki · 2022-01-18T22:48:34.149Z

plikmuny:

i feel my cs-firewall-bouncer is not working. i dont see a sign that its working. can you tell me how to check whether it is working or not ? if not how can i install cs-nginx-bouncer ???

There is a package fix pending for approval.
You may, wait for approval being effective, or reproducing the fix locally.
Look at: https://github.com/openwrt/packages/pull/17614/files# and reproduce the modification at line 7 of initd.
All the rest are just cosmetics fixes.

Then do a service restart with:

service crowdsec-firewall-bouncer restart

Then do a check on the /var/log/crowdsec-firewall-bouncer.log
Or, better, look at the bouncers status with:

cscli bouncers list

Or look at the crowdsec wiki page with the check about firewall bouncer at openwrt wiki.

OpenWrt Wiki – 7 Jan 22

CrowdSec

CrowdSec This wiki page is currently a work in progress and information is currently in the process of being transferred from the community forum. Main Website: Documentation : Release info: OpenWrt Forum thread: CrowdSec Forum thread:

plikmuny:

if not how can i install cs-nginx-bouncer ???

I do not have made any package for nginx bouncer for now.
I will, soon, if needed.

plikmuny · 2022-01-18T22:59:39.245Z

its very strange that i dont have any output when i type ipset list !!!

root@rpi4-e45f01048a ~41# ipset list
root@rpi4-e45f01048a ~41#

plikmuny · 2022-01-18T23:01:21.924Z

few log files from the commands which i tried to check whether firewall-bouncer is working or not... does it say anything to you ? i mean whether my setup is complete and functioning properly ???

root@rpi4-e45f01048a ~41# cscli bouncers list

NAME IP ADDRESS VALID LAST API PULL TYPE VERSION

crowdsec-firewall-bouncer-yNsKPLaO 2022-01-18T22:05:17Z
myBouncer 2022-01-18T22:12:12Z
crowdsec-nginx-bouncer-qOZcHzrL 2022-01-18T22:48:02Z
MyBouncerName 2022-01-18T22:54:39Z

root@rpi4-e45f01048a ~41# cscli metrics
INFO[18-01-2022 10:56:16 PM] Local Api Metrics:
+--------------------+--------+------+
| ROUTE | METHOD | HITS |
+--------------------+--------+------+
| /v1/alerts | GET | 2 |
| /v1/watchers/login | POST | 4 |
+--------------------+--------+------+
INFO[18-01-2022 10:56:16 PM] Local Api Machines Metrics:
+--------------------------------------------------+------------+--------+------+
| MACHINE | ROUTE | METHOD | HITS |
+--------------------------------------------------+------------+--------+------+
| 1e13711506834337890b76ea8f69d734y4eu4sozLJGym7rk | /v1/alerts | GET | 2 |
+--------------------------------------------------+------------+--------+------+
root@rpi4-e45f01048a ~42# ps | grep crowdsec
4351 root 1220 RN grep crowdsec
32362 root 783m S /usr/bin/crowdsec -c /var/etc/crowdsec/config.yaml
root@rpi4-e45f01048a ~40# service crowdsec-firewall-bouncer restart
iptables found
nftables found
Found nftables(default) and iptables...
root@rpi4-e45f01048a ~40# ipset list
root@rpi4-e45f01048a ~40# cscli decisions list
No active decisions
root@rpi4-e45f01048a ~41# cscli decision
Error: unknown command "decision" for "cscli"

Did you mean this?
decisions

Run 'cscli --help' for usage.
FATA[0000] While executing root command : unknown command "decision" for "cscli"

Did you mean this?
decisions
root@rpi4-e45f01048a ~42# cscli decisions
Add/List/Delete/Import decisions from LAPI

Usage:
cscli decisions [command]

Examples:
cscli decisions [action] [filter]

Available Commands:
add Add decision to LAPI
delete Delete decisions
import Import decisions from json or csv file
list List decisions from LAPI

Flags:
-h, --help help for decisions

Global Flags:
-c, --config string path to crowdsec config file (default "/etc/crowdsec/config.yaml")
--debug Set logging to debug.
--error Set logging to error.
--info Set logging to info.
-o, --output string Output format : human, json, raw.
--trace Set logging to trace.
--warning Set logging to warning.

Use "cscli decisions [command] --help" for more information about a command.
root@rpi4-e45f01048a ~41# cscli decisions list
No active decisions
root@rpi4-e45f01048a ~41# ipset list
root@rpi4-e45f01048a ~41# nft list tables
root@rpi4-e45f01048a ~41# cscli alerts list
+----+------------------------------+-----------------------+---------+----+-----------+-------------------------------+
| ID | VALUE | REASON | COUNTRY | AS | DECISIONS | CREATED AT |
+----+------------------------------+-----------------------+---------+----+-----------+-------------------------------+
| 1 | crowdsec/community-blocklist | update : +2115/-0 IPs | | | ban:2115 | 2022-01-18 22:14:04 +0000 UTC |
+----+------------------------------+-----------------------+---------+----+-----------+-------------------------------+
root@rpi4-e45f01048a ~41# ipset list
root@rpi4-e45f01048a ~41# ^C
root@rpi4-e45f01048a ~41#

erdoukki · 2022-01-18T23:05:42.368Z

You have nftables and iptables installed.
Your firewall default for crowdsec became then nftables.
You have to use nft specific command to check config and effect of crowdsec firewall bouncer on your firewall.
Or remove nftables package from your config and use iptables.

erdoukki:

There is a package fix pending for approval.
You may, wait for approval being effective, or reproducing the fix locally.
Look at: https://github.com/openwrt/packages/pull/17614/files# and reproduce the modification at line 7 of initd.
All the rest are just cosmetics fixes.

Have you apply this fix ?

Can you check ps | grep crowdsec after the service crowdsec-firewall-bouncer restart

plikmuny:

root@rpi4-e45f01048a ~41# cscli alerts list
+----+------------------------------+-----------------------+---------+----+-----------+-------------------------------+
| ID | VALUE | REASON | COUNTRY | AS | DECISIONS | CREATED AT |
+----+------------------------------+-----------------------+---------+----+-----------+-------------------------------+
| 1 | crowdsec/community-blocklist | update : +2115/-0 IPs | | | ban:2115 | 2022-01-18 22:14:04 +0000 UTC |
+----+------------------------------+-----------------------+---------+----+-----------+-------------------------------+

You have community rules correctly applied.
So crowdsec is already working.
I think firewall also gets the ips to ban when alerts are feeded.
But you may use the nft commands, when using nftables, or ipset commands if using only iptables, to check the statis of your system firewall bans and to be sure.

plikmuny · 2022-01-18T23:13:48.965Z

root@rpi4-e45f01048a /41# ps | grep crowdsec
5175 root 1220 RN grep crowdsec
32362 root 784m S /usr/bin/crowdsec -c /var/etc/crowdsec/config.yaml

erdoukki · 2022-01-18T23:17:51.107Z

Apologize, this check only crowdsec, not cs !

If you have already modified your /etc/initd/crowdsec-firewall-bouncer, with nano or vi, and replaced, at line 7;
PROG=/usr/bin/crowdsec-firewall-bouncer
by;
PROG=/usr/bin/cs-firewall-bouncer

Then do service crowdsec-firewall-bouncer restart and ps | grep cs

If okay, then both works fine…

plikmuny · 2022-01-19T10:50:43.567Z

I will try to do it today after I come home. Sorry for yesterday, I slept off before replying to you. I also deleted nftables and see if only with iptables I can get crowdsec working...
I will get back to you today evening... Thanks die you're reply

plikmuny · 2022-01-19T20:43:46.621Z

plikmuny:

cscli metrics

Thank you Erdoukki, now it is working fine. i have one request though, could you make this installation lot more easier for the end user with updates ??? so that we dont have to struggle a lot in making this wonderful software work on Openwrt please ???

Thanks once again for your hard work and keep it up.

erdoukki · 2022-01-21T09:24:00.735Z

plikmuny:

Thanks once again for your hard work and keep it up.

Thanks...

plikmuny:

Thank you Erdoukki, now it is working fine. i have one request though, could you make this installation lot more easier for the end user with updates ??? so that we dont have to struggle a lot in making this wonderful software work on Openwrt please ???

I will try to enhance with users feedbacks...

Already all the processes you have to do manually was because of some, now fixed, bugs in the firewall package.

Please, keep in mind that all the jobs is done, at free time, when, so, I have some.
It is also the case of the most of the OpenWrt developers, and, I also have to wait for them, when I share my works on CrowdSec.

erdoukki · 2022-01-21T10:10:48.255Z

firewall fix PR for master merged !

github.com/openwrt/packages

crowdsec-firewall-bouncer: fix initd script

openwrt:master ← erdoukki:crowdsec-firewall-bouncer-0.0.21-fix

opened 08:25AM - 15 Jan 22 UTC

erdoukki

+5 -5

Maintainer: Gérald Kerma / @erdoukki Compile tested: (aarch64_cortex-a53, espre…ssoBin, OpenWrt master and 21.02) Run tested: (aarch64_cortex-a53, espressoBin, OpenWrt 21.02.x and 19.07.x, tests done) Tests: installation and upgrade: ok ban working: ok service start/restart/stop/status/disable: ok logging: ok detection of firewall (iptables+ipset/nftables): ok OpenWrt Version tested: 21.02.x 19.07.x Description: crowdsec rename the binary from crowdsec-firewall-bouncer to cs-firewall-bouncer the initd need the correct binary name to start the process the link for github source need also to be fixed (only the information one) fix the BuildDate updated copyright ``` root@STARGATE:~# service crowdsec-firewall-bouncer restart iptables found nftables is not present root@STARGATE:~# ps | grep crowd 10051 root 783m S /usr/bin/crowdsec -c /var/etc/crowdsec/config.yaml 15744 root 694m S /usr/bin/cs-firewall-bouncer -c /var/etc/crowdsec/bouncers/crowdsec-firewall-bouncer.yaml 15761 root 1228 S grep crowd ``` ``` root@STARGATE:~# cs-firewall-bouncer -V version: v0.0.21-openwrt-0.0.21-2 BuildDate: 2022-01-15_08:15:14 GoVersion: 1.13.8 ``` Signed-off-by: Kerma Gérald <gandalf@gk2.net>

firewall initd fix for 21.02 (PR opened):

github.com/openwrt/packages

[21.02] crowdsec-firewall-bouncer: fix name in initd to start the process

openwrt:openwrt-21.02 ← erdoukki:crowdsec-firewall-bouncer-fix-21.02

opened 10:07AM - 21 Jan 22 UTC

erdoukki

+5 -5

Maintainer: Gérald Kerma / @erdoukki Compile tested: (aarch64_cortex-a53, espre…ssoBin, OpenWrt master and 21.02) Run tested: (aarch64_cortex-a53, espressoBin, OpenWrt 21.02.x, tests done) Tests: OK OpenWrt Version tested: 21.02.x Description: crowdsec rename the binary from crowdsec-firewall-bouncer to cs-firewall-bouncer the initd need the correct binary name to start the process the link for github source need also to be fixed (only the information one) fix the BuildDate updated copyright Signed-off-by: Kerma Gérald <gandalf@gk2.net> (cherry picked from commit d6b116cb43802048d883a13e2d2e95eea76ad565)

will resolve issue:

github.com/openwrt/packages

[21.02] crowdsec-firewall-bouncer: initd script error

opened 03:46PM - 18 Jan 22 UTC

erdoukki

Maintainer: Gérald Kerma / @erdoukki Environment: (aarch64_cortex-a53, espresso…Bin, OpenWrt master and 21.02) Description: crowdsec-firewall-bouncer initd/service do not start correctly. the binary name has changed and is bad referenced in the initd script. Resolved-by: https://github.com/openwrt/packages/pull/17614

PRs for lua-cs-bouncer and crowdsec-nginx-bouncer:

github.com/openwrt/packages

lua-cs-bouncer: initial package

openwrt:master ← erdoukki:lua-cs-bouncer

opened 10:07AM - 21 Jan 22 UTC

erdoukki

+93 -0

Maintainer: Gérald Kerma / @erdoukki Compile tested: (aarch64_cortex-a53, espre…ssoBin, OpenWrt master and 21.02) Run tested: (aarch64_cortex-a53, espressoBin, OpenWrt 21.02.x, tests done) Tests: OK OpenWrt Version tested: 21.02.x Description: Lua Crowdsec Bouncer module Lua module to allow ip (or not) from CrowdSec API. https://github.com/crowdsecurity/lua-cs-bouncer required for crowdsec-nginx-bouncer Signed-off-by: Kerma Gérald <gandalf@gk2.net>

github.com/openwrt/packages

crowdsec-nginx-bouncer: initial package

openwrt:master ← erdoukki:crowdsec-nginx-bouncer

opened 10:08AM - 21 Jan 22 UTC

erdoukki

+97 -0

Maintainer: Gérald Kerma / @erdoukki Compile tested: (aarch64_cortex-a53, espre…ssoBin, OpenWrt master and 21.02) Run tested: (aarch64_cortex-a53, espressoBin, OpenWrt 21.02.x, tests done) Tests: OK OpenWrt Version tested: 21.02.x Required: https://github.com/openwrt/packages/pull/17667 Description: nginx bouncer for Crowdsec https://github.com/crowdsecurity/crowdsec-nginx-bouncer Crowdsec bouncer is a lua bouncer for nginx. New/unknown IP are checked against crowdsec API, and if request should be blocked, a 403 is returned to the user, and put in cache. Signed-off-by: Kerma Gérald <gandalf@gk2.net>

...stay tuned !

plikmuny · 2022-01-21T10:38:03.346Z

Hi, that means no more fiddling with the setup of Crowdsec and I have to just install Crowdsec and bouncer and the rest works automatically??? Or is it not the case as of now?
As I understand cs-nginx-bouncer is also included in the package or should I install it manually???

Oh, my mistake. I saw just now the package. There once again a72 package is missing for Rpi4. Can you please compile for a72 architecture also? Or tell me which version I should use for my Rpi4 Openwrt.

One more question, post Crowdsec installation, which collections or parsers in addition to Crowdsec should I install??

erdoukki · 2022-01-21T10:48:03.044Z

plikmuny:

Hi, that means no more fiddling with the setup of Crowdsec and I have to just install Crowdsec and bouncer and the rest works automatically??? Or is it not the case as of now?

If you need and wand to use only the banip feature of the firewall, just do:
heart component:

opkg install crowdsec

This package will register to the official API and you'll get feed with the community, free, CrowdSec managed IPs list.

ipbans firewalling:

opkg install crowdsec-firewall-bouncer

The community IPs BANs list will be used and managed by OpenWrt System firewall software...

plikmuny:

As I understand cs-nginx-bouncer is also included in the package or should I install it manually???

if you need to protect an nginx instance on OpenWrt itself:

opkg install crowdsec-nginx-bouncer

You will then get this specific nginx component for protecting OpenWrt NGINX software.

plikmuny:

Oh, my mistake. I saw just now the package. There once again a72 package is missing for Rpi4. Can you please compile for a72 architecture also? Or tell me which version I should use for my Rpi4 Openwrt.

The component will be available on the official upstream pacakges, when it will be compiled by the buildbots, after developers get review of my PR and they validated it, to be merged in the code...
Each steps require time, to each actor !

If you want more by yourself, give a try to a build of the package.

plikmuny:

One more question, post Crowdsec installation, which collections or parsers in addition to Crowdsec should I install??

None / depends of your needs !

If you want more, you may look at the code itself, and then compare at the bouncers list, and also share your results in the wiki, or here...

erdoukki · 2022-01-23T10:17:24.793Z

anon50098793:

60M... slow servers maybe...

github.com/openwrt/packages

crowdsec/geoipupdate: enhancement request for offline database download

opened 10:36AM - 23 Jan 22 UTC

closed 11:59AM - 02 May 22 UTC

erdoukki

Maintainer: Gérald Kerma / @erdoukki Compile tested: (aarch64_cortex-a53, espre…ssoBin, OpenWrt master and 21.02) Run tested: (aarch64_cortex-a53, espressoBin, OpenWrt 21.02.x, tests done) Description: As refereed in [Idea/GeoIP: offline/update/share database](https://github.com/crowdsecurity/crowdsec/issues/1196) > CrowdSec OpenWrt package is downloading the GeoIP databases at postinstall, this may be a huge download on some users ISP, but it also may not work at all in case users want to integrate the crowdsec package in the OpenWrt firmware image. Thanks to @clayface the package geoipupdate is available since PR: https://github.com/openwrt/packages/pull/17171 The question here is like the same from https://github.com/crowdsecurity/crowdsec/issues/1196 Note: Sorry for crosslink between OpenWrt/CrowdSec but the both communities may be interested

erdoukki · 2022-02-05T09:03:08.386Z

anon50098793:

edit: looks like crowdsec-firewall-bouncer may have some issues also...

upstream topic: https://discourse.crowdsec.net/t/crowdsec-openwrt-21-02-1-iptables-ipset-package-problems/533/5
issue: https://github.com/openwrt/packages/issues/17804
PR: https://github.com/openwrt/packages/pull/17805

erdoukki · 2022-02-06T15:35:27.925Z

github.com/openwrt/packages

crowdsec: install defaults notifications

openwrt:master ← erdoukki:crowdsec-notifications

opened 09:34PM - 05 Feb 22 UTC

erdoukki

+504 -54

Maintainer: Gérald Kerma @erdoukki [gandalf@gk2.net](mailto:gandalf@gk2.net) En…vironment: (all, OpenWrt Master & 21.02.x) Description: https://docs.crowdsec.net/docs/next/notification_plugins/intro > Crowdsec supports notification plugins, meant to be able to push alerts to third party services, for alerting or integration purposes. At the time of writting, plugins exists for [slack](https://docs.crowdsec.net/docs/next/notification_plugins/slack), [splunk](https://docs.crowdsec.net/docs/next/notification_plugins/splunk), and a generic [http push](https://docs.crowdsec.net/docs/next/notification_plugins/http) plugin (allowing to push to services such as [elasticsearch](https://docs.crowdsec.net/docs/next/notification_plugins/elastic)). update crowdsec Makefile to fix plugins notifications build and install: - use correct path in GO_PKG_BUILD_PKG to build plugins - use INSTALL_DATA and INSTALL_BIN instead of CP to install plugins and config other fix: - add bouncers directory - add upstream patches for default data and config directories - rewrote & clean the defaults script (also verified with shellcheck) - rewrote & clean the Makefile - remove useless crowdsec-cli - add configdir to config file - add lapi_host and lapi_port to config file - upgrade missing configs values to defaults in config file at upgrade - add license and copyright - use CWD_VARS for Makefile variables Signed-off-by: Kerma Gérald <gandalf@gk2.net>

github.com/openwrt/packages

crowdsec-firewall-bouncer: fix API error: access forbidden

openwrt:master ← erdoukki:crowdsec-firewall-bouncer-fix-17804

opened 09:00AM - 05 Feb 22 UTC

erdoukki

+37 -11

crowdsec-firewall-bouncer: fix API error: access forbidden when bouncer is not c…orrectly registered #17804 Maintainer: Gérald Kerma @erdoukki [gandalf@gk2.net](mailto:gandalf@gk2.net) Environment: (all, OpenWrt Master & 21.02.x) Issue: https://github.com/openwrt/packages/issues/17804 Initially reported here: https://forum.openwrt.org/t/crowdsec-packages-for-openwrt/102648/25 This fix by checking deeper the bouncer status, re-registering it with force and api key if necessary This PR also fix some ENV names Fix also tests on strings Fix script net/crowdsec-firewall-bouncer/files/crowdsec-firewall-bouncer.defaults with spellcheck Fix strings with quotes Removed space before exclamation point Fix typo and replace triple dot by ellipsis Description: I got an issue, which I resolved with as small modification on the script (look from OpenWrt side) While the api_key is already defined in crowdsec-firewall-bouncer.yaml the grep on {API_KEY} will not success. It may be normal behaviour, but in case the bouncer is not actually registered, because of an error or anything out of scope, the results is the bouncer is lost because of noo re-registering ! Actual "initialisation" (at upgrade, install, ...) on OpenWrt, is in the following script: https://github.com/openwrt/packages/blob/2b28e3dfdb14d4bea995181b9f00fc32407c7a73/net/crowdsec-firewall-bouncer/files/crowdsec-firewall-bouncer.defaults If made this fix in; ## Gen&ConfigApiKey which force to re-register with the same api-key ( thanks to PR https://github.com/crowdsecurity/crowdsec/commit/9034bb791926b193f9f3fb73878399568ef656cb ) ! This is now working better, this is an issue we already know on OpenWrt, on reported and the OpenWrt CrowdSec dev topic ... https://forum.openwrt.org/t/crowdsec-packages-for-openwrt/102648/25 and already reported on the CrowdSec forum: https://discourse.crowdsec.net/t/crowdsec-openwrt-21-02-1-iptables-ipset-package-problems/533/2 /var/log/crowdsec-firewall-bouncer.log:time="13-01-2022 15:34:05" level=fatal msg="API error: access forbidden" I will share this resolution tweak in the OpenWrt CrowdSec-Firewall-Bouncer package and made a PR at OpenWrt... REF to issue: https://github.com/openwrt/packages/issues/17804 REF to upstream issue: https://github.com/crowdsecurity/crowdsec/issues/1240 Signed-off-by: Kerma Gérald <gandalf@gk2.net>

plikmuny · 2022-02-06T16:11:02.187Z

Hi, i just want to thank you for your wonderful work on this addon. It's working perfectly. Even then i should change the name backend to iptables... Is it must or it works by leaving it default?

erdoukki · 2022-02-06T19:41:49.406Z

plikmuny:

Hi, i just want to thank you for your wonderful work on this addon. It's working perfectly.

Thanks!

I still had to share some tutorials, the software is really cool and can afford a great enhancement in network security...
Stay tune!

plikmuny:

Even then i should change the name backend to iptables... Is it must or it works by leaving it default?

I you have install iptables and ipset without installing also nftables, then all will be automatically detected and the backend will be sets to iptables at services startup.
If you have only nftables, same, but with nftables.

If you have installed both nftables and iptables, then nftables will be selected in priority.

The backend cannot be sets manually on OpenWrt, but I can made a general config if needed, disabling the auto-detect of backend, and using a manual forced backend.
A tweak is also possible with removing the backend tag in the /etc/crowdsec/bouncers/crowdsec-firewall-bouncer.yaml , removing the tag ${BACKEND} which is searched and used in the auto-detect script...

erdoukki · 2022-02-06T21:44:13.580Z

I have start to wrote some notes in the Wiki...
About the upcoming feature of notifications alerts and quick howto with collections from the hub, to protect dockers instance of NextCloud and NginxProxyManager...

OpenWrt Wiki – 7 Jan 22

CrowdSec

CrowdSec This wiki page is currently a work in progress and information is currently in the process of being transferred from the community forum. Main Website: Documentation : Release info: OpenWrt Forum thread: CrowdSec Forum thread:

https://openwrt.org/docs/guide-user/services/crowdsec#external_tools a new script will be available for external tools contributing to simplify users experience with CrowdSec!

plikmuny · 2022-02-07T11:16:23.449Z

Hi erduokki:- i am getting a strange error when i try to list decisions list. This is the error i am getting

root@rpi4-e45f01048a /45# cscli decisions list
FATA[07-02-2022 12:14:48 PM] Unable to list decisions : performing request: Get "http://127.0.0.1:8080/v1/alerts?has_active_decision=true&include_capi=false&limit=100": could not get jwt token: Post "http://127.0.0.1:8080/v1/watchers/login": dial tcp 127.0.0.1:8080: connect: connection refused
what does it really mean ? how do i solve this error ?