# CrowdSec package for OpenWrt

**URL:** <https://discourse.crowdsec.net/t/crowdsec-package-for-openwrt/225>\
**Category:** Uncategorized\
**Created:** [July 23, 2021, 2:07pm UTC](https://discourse.crowdsec.net/t/crowdsec-package-for-openwrt/225 "2021-07-23T14:07:07Z")\
**Posts on this page:** 20\
**Page:** 2

<div class="post-metadata">

**Author:** ![klausagnoletti](https://dub1.discourse-cdn.com/flex013/user_avatar/discourse.crowdsec.net/klausagnoletti/32/201_2.png) [@klausagnoletti](https://discourse.crowdsec.net/u/klausagnoletti)\
**Post date:** [December 3, 2021, 12:16pm UTC](https://discourse.crowdsec.net/t/crowdsec-package-for-openwrt/225/21 "2021-12-03T12:16:48Z")

</div>

Will this work for TurrisOS as well? Or will it need customization?

---

<div class="post-metadata">

**Author:** ![Gandalf](https://dub1.discourse-cdn.com/flex013/user_avatar/discourse.crowdsec.net/gandalf/32/43_2.png) [@Gandalf](https://discourse.crowdsec.net/u/Gandalf)\
**Post date:** [December 3, 2021, 12:37pm UTC](https://discourse.crowdsec.net/t/crowdsec-package-for-openwrt/225/22 "2021-12-03T12:37:07Z")

</div>

I am pretty sure it will work on TurrisOS without more customization than what is needed on OpenWrt.  
It is 21.02.x based, but I also use it on 19.07.x  
The installation process still need some customization and tweaks to be more user friendly and automated.  
We have started to discuss it here at OpenWrt forum topic :

> **[Crowdsec: initial packages v1.2.0 for OpenWrt](https://forum.openwrt.org/t/crowdsec-initial-packages-v1-2-0-for-openwrt/102648/)**
>
> Héllo all, Here is a PR for CrowdSec v1.1.1 and CrowdSec-FireWall-Bouncer v0.0.13 I still get an issue with ARM compile and buildroot… See https://github.com/openwrt/packages/issues/16193 Is there anyone who can help to fix this, please ? ...

---

<div class="post-metadata">

**Author:** ![klausagnoletti](https://dub1.discourse-cdn.com/flex013/user_avatar/discourse.crowdsec.net/klausagnoletti/32/201_2.png) [@klausagnoletti](https://discourse.crowdsec.net/u/klausagnoletti)\
**Post date:** [December 3, 2021, 12:57pm UTC](https://discourse.crowdsec.net/t/crowdsec-package-for-openwrt/225/23 "2021-12-03T12:57:15Z")

</div>

Sweet. I just contacted Turris to suggest some sort of colaboration. I’ll keep you posted on the outcome 🙂

---

<div class="post-metadata">

**Author:** ![Gandalf](https://dub1.discourse-cdn.com/flex013/user_avatar/discourse.crowdsec.net/gandalf/32/43_2.png) [@Gandalf](https://discourse.crowdsec.net/u/Gandalf)\
**Post date:** [January 7, 2022, 1:50pm UTC](https://discourse.crowdsec.net/t/crowdsec-package-for-openwrt/225/24 "2022-01-07T13:50:08Z")

</div>

Update (PR) to latest upstream release version done… 😉

> <https://github.com/openwrt/packages/pull/17515>
>
> Maintainer: Kerma Gérald \<gandalf@gk2.net\> / @erdoukki
> Run tested: (untested)
> …
> Compile tested: (arch=cortexa53, host=amd64)
> 
> Description:
> 
> Update crowdsec to latest upstream release version 1.2.2
> 
> Add missing LICENSE file
> 
> Signed-off-by: Kerma Gérald \<gandalf@gk2.net\>

and

> <https://github.com/openwrt/packages/pull/17516>
>
> Maintainer: Kerma Gérald gandalf@gk2.net / @erdoukki
> Run tested: (untested)
> Co…mpile tested: (arch=cortexa53, host=amd64)
> 
> Description:
> 
> Update crowdsec-firewall-bouncer to latest upstream release version 0.0.21
> 
> Add missing LICENSE file
> 
> Signed-off-by: Kerma Gérald \<gandalf@gk2.net\>

Will be forwarded to 21.02, as soon as validated !

Have an happy new year all…

---

<div class="post-metadata">

**Author:** ![Gandalf](https://dub1.discourse-cdn.com/flex013/user_avatar/discourse.crowdsec.net/gandalf/32/43_2.png) [@Gandalf](https://discourse.crowdsec.net/u/Gandalf)\
**Post date:** [January 7, 2022, 1:55pm UTC](https://discourse.crowdsec.net/t/crowdsec-package-for-openwrt/225/25 "2022-01-07T13:55:48Z")

</div>

If you want to contribute and/or help to the OpenWrt specifics needs, please take a look at the topic here: [Crowdsec packages for OpenWrt - For Developers - OpenWrt Forum](https://forum.openwrt.org/t/crowdsec-packages-for-openwrt/102648)

---

<div class="post-metadata">

**Author:** ![klausagnoletti](https://dub1.discourse-cdn.com/flex013/user_avatar/discourse.crowdsec.net/klausagnoletti/32/201_2.png) [@klausagnoletti](https://discourse.crowdsec.net/u/klausagnoletti)\
**Post date:** [January 7, 2022, 9:58pm UTC](https://discourse.crowdsec.net/t/crowdsec-package-for-openwrt/225/26 "2022-01-07T21:58:15Z")

</div>

Thanks for the link and for the update to 1.2.2. Someone’s asking for a wiki entry. I don’t know exactly what that means but I know that I am working along with our new ambassador, Precious, on a section in the official docs on installing on OpenWRT as well as an article on usage. And on top of that I created an issue on creating parsers for dropbear and uHTTPd so that CrowdSec on OpenWRT is able to protect itself 🙂

---

<div class="post-metadata">

**Author:** ![Gandalf](https://dub1.discourse-cdn.com/flex013/user_avatar/discourse.crowdsec.net/gandalf/32/43_2.png) [@Gandalf](https://discourse.crowdsec.net/u/Gandalf)\
**Post date:** [January 7, 2022, 10:21pm UTC](https://discourse.crowdsec.net/t/crowdsec-package-for-openwrt/225/27 "2022-01-07T22:21:47Z")

</div>

A contributor made a quick wiki on official OpenWrt space:

> **[Crowdsec](https://openwrt.org/docs/guide-user/services/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 is an...

Thanks for the issues about dropbear and uHTTPd !  
I will try to get a look at it…

For the article about OpenWrt and CrowdSec, it is still in my TODO, I hope to get some time available to work on it…

---

<div class="post-metadata">

**Author:** ![klausagnoletti](https://dub1.discourse-cdn.com/flex013/user_avatar/discourse.crowdsec.net/klausagnoletti/32/201_2.png) [@klausagnoletti](https://discourse.crowdsec.net/u/klausagnoletti)\
**Post date:** [January 9, 2022, 2:31pm UTC](https://discourse.crowdsec.net/t/crowdsec-package-for-openwrt/225/28 "2022-01-09T14:31:44Z")

</div>

Hey and thanks! Our new ambassador will be working on an article. He’ll be happy to send it to you for comments. Will that be ok?

---

<div class="post-metadata">

**Author:** ![Gandalf](https://dub1.discourse-cdn.com/flex013/user_avatar/discourse.crowdsec.net/gandalf/32/43_2.png) [@Gandalf](https://discourse.crowdsec.net/u/Gandalf)\
**Post date:** [January 13, 2022, 4:37pm UTC](https://discourse.crowdsec.net/t/crowdsec-package-for-openwrt/225/29 "2022-01-13T16:37:56Z")

</div>

Still a lot to do to tweaks fine the OpenWrt version; but today, the 21.02.x branch get the latest version of CrowdSec (1.2.2) and Crowdsec-Firewall-Bouncer (0.0.21) !

> <https://github.com/openwrt/packages/pull/17538>
>
> Maintainer: Kerma Gérald gandalf@gk2.net / @erdoukki
> Run tested: (test done on …MVEBU arch53 EspressoBin & EspressoBin-ULTRA, OpenWrt 19.07.x and 21.02.x)
> Compile tested: (arch=cortexa53, host=amd64)
> 
> Description:
> 
> Update crowdsec to latest upstream release version 1.2.2
> 
> Makefile rework
> \- use tagged version for download
> 
> (cherry picked from commit 2a34e4987bbd60091150de1886017426f10634ab)
> Signed-off-by: Kerma Gérald \<gandalf@gk2.net\>

> <https://github.com/openwrt/packages/pull/17562>
>
> Maintainer: Kerma Gérald gandalf@gk2.net / @erdoukki
> Run tested: (test done on …MVEBU arch53 EspressoBin & EspressoBin-ULTRA, OpenWrt 19.07.x and 21.02.x)
> Compile tested: (arch=cortexa53, host=amd64)
> 
> Description:
> 
> Update crowdsec-firewall-bouncer to latest upstream release version 0.0.21
> 
> Makefile rework
> \- use tagged version for download
> 
> Fixes
> \- set API\_KEY in firewall bouncer config file
> 
> (cherry picked from commit b4f48b5c23d0b5d2ab9de2041edbf69a8f6ca013)
> Signed-off-by: Kerma Gérald \<gandalf@gk2.net\>

---

<div class="post-metadata">

**Author:** ![Gandalf](https://dub1.discourse-cdn.com/flex013/user_avatar/discourse.crowdsec.net/gandalf/32/43_2.png) [@Gandalf](https://discourse.crowdsec.net/u/Gandalf)\
**Post date:** [January 15, 2022, 8:32am UTC](https://discourse.crowdsec.net/t/crowdsec-package-for-openwrt/225/30 "2022-01-15T08:32:16Z")

</div>

> [@klausagnoletti](#):
>
> Thanks for the link and for the update to 1.2.2. Someone’s asking for a wiki entry. I don’t know exactly what that means but I know that I am working along with our new ambassador, Precious, on a section in the official docs on installing on OpenWRT as well as an article on usage.

An OpenWrt user/contributor had started a wiki that you can look at:

> **[CrowdSec](https://openwrt.org/docs/guide-user/services/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:

I also just add some information about the firewall bouncer.

I found an issue on the initd of the latest release, the fix was proposed:

> <https://github.com/openwrt/packages/pull/17614>
>
> 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\>

> [@klausagnoletti](#):
>
> And on top of that I created an issue on creating parsers for dropbear and uHTTPd so that CrowdSec on OpenWRT is able to protect itself 🙂

OpenWrt may also use another Web Server than uHTTPd, and dropbear is also only the default ssh.  
The both are not afford to the internet side of OpenWrt system, so no urgency about this for me.  
Where are these issue opened ?  
In case I could help on them…  
😇

I need to do more tests with my Docker services.  
I want to protect them with my main OpenWrt GateWay/Router firewall, like I have done before with LXC services.  
I still get no time to tests and share experiences on this type of installation.  
And I get just no success with my first steps tests on ARM64 OpenWrt to get CrowdSec and Docker working…

As usual…  
Stay tuned for more (or do it yourself…) 🕶

---

<div class="post-metadata">

**Author:** ![Gandalf](https://dub1.discourse-cdn.com/flex013/user_avatar/discourse.crowdsec.net/gandalf/32/43_2.png) [@Gandalf](https://discourse.crowdsec.net/u/Gandalf)\
**Post date:** [January 15, 2022, 8:46am UTC](https://discourse.crowdsec.net/t/crowdsec-package-for-openwrt/225/31 "2022-01-15T08:46:25Z")

</div>

> [@klausagnoletti](#):
>
> Hey and thanks! Our new ambassador will be working on an article. He’ll be happy to send it to you for comments. Will that be ok?

Please, do…  
I can try help on this if I can !

---

<div class="post-metadata">

**Author:** ![klausagnoletti](https://dub1.discourse-cdn.com/flex013/user_avatar/discourse.crowdsec.net/klausagnoletti/32/201_2.png) [@klausagnoletti](https://discourse.crowdsec.net/u/klausagnoletti)\
**Post date:** [January 15, 2022, 10:03am UTC](https://discourse.crowdsec.net/t/crowdsec-package-for-openwrt/225/32 "2022-01-15T10:03:53Z")

</div>

Great! I’ll let you know when something’s ready. I created [this](https://github.com/crowdsecurity/hub/issues/332) issue on the missing parsers.

---

<div class="post-metadata">

**Author:** ![Gandalf](https://dub1.discourse-cdn.com/flex013/user_avatar/discourse.crowdsec.net/gandalf/32/43_2.png) [@Gandalf](https://discourse.crowdsec.net/u/Gandalf)\
**Post date:** [January 15, 2022, 10:16am UTC](https://discourse.crowdsec.net/t/crowdsec-package-for-openwrt/225/33 "2022-01-15T10:16:36Z")

</div>

New upstream relase 1.2.3 of CrowdSec proposed to OpenWrt:

> <https://github.com/openwrt/packages/pull/17615>
>
> 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, tests done)
> 
> Tests:
> installation and upgrade: ok
> 
> Description:
> update from latest upstream release 1.2.3
> 
> Changes (from 1.2.2):
> https://github.com/crowdsecurity/crowdsec/compare/v1.2.2...v1.2.3
> 
> Tests:
> \`\`\`
> root@STARGATE:~# crowdsec --version
> 2022/01/15 11:06:46 version: v1.2.2-openwrt-1.2.2-1
> 2022/01/15 11:06:46 Codename: alphaga
> 2022/01/15 11:06:46 BuildDate: 2022-01-14\_14:21:08
> 2022/01/15 11:06:46 GoVersion: 
> 2022/01/15 11:06:46 Constraint\_parser: \>= 1.0, \<= 2.0
> 2022/01/15 11:06:46 Constraint\_scenario: \>= 1.0, \< 3.0
> 2022/01/15 11:06:46 Constraint\_api: v1
> 2022/01/15 11:06:46 Constraint\_acquis: \>= 1.0, \< 2.0
> \`\`\`
> \`\`\`
> root@STARGATE:~# opkg install /root/crowdsec\_1.2.3-2\_aarch64\_cortex-a53.ipk 
> Upgrading crowdsec on root from 1.2.2-1 to 1.2.3-2...
> Configuring crowdsec.
> local API already registered...
> online API already registered...
> INFO\[15-01-2022 11:07:37 AM\] Wrote new 210740 bytes index to /etc/crowdsec/hub/.index.json 
> WARN\[15-01-2022 11:07:38 AM\] crowdsecurity/syslog-logs : overwrite        
> WARN\[15-01-2022 11:07:38 AM\] crowdsecurity/geoip-enrich : overwrite       
> WARN\[15-01-2022 11:07:38 AM\] crowdsecurity/dateparse-enrich : overwrite   
> WARN\[15-01-2022 11:07:38 AM\] crowdsecurity/sshd-logs : overwrite          
> WARN\[15-01-2022 11:07:39 AM\] crowdsecurity/ssh-bf : overwrite             
> WARN\[15-01-2022 11:07:39 AM\] crowdsecurity/ssh-slow-bf : overwrite        
> WARN\[15-01-2022 11:07:39 AM\] crowdsecurity/sshd : overwrite               
> WARN\[15-01-2022 11:07:39 AM\] crowdsecurity/sshd : overwrite               
> WARN\[15-01-2022 11:07:39 AM\] crowdsecurity/linux : overwrite              
> INFO\[15-01-2022 11:07:39 AM\] /etc/crowdsec/collections/sshd.yaml already exists. 
> INFO\[15-01-2022 11:07:39 AM\] /etc/crowdsec/collections/linux.yaml already exists. 
> INFO\[15-01-2022 11:07:39 AM\] Enabled crowdsecurity/linux                  
> INFO\[15-01-2022 11:07:39 AM\] Run 'sudo systemctl reload crowdsec' for the new configuration to be effective. 
> WARN\[15-01-2022 11:07:39 AM\] crowdsecurity/whitelists : overwrite         
> INFO\[15-01-2022 11:07:39 AM\] Enabled crowdsecurity/whitelists             
> INFO\[15-01-2022 11:07:39 AM\] Run 'sudo systemctl reload crowdsec' for the new configuration to be effective. 
> INFO\[15-01-2022 11:07:40 AM\] Upgrading collections                        
> INFO\[15-01-2022 11:07:40 AM\] crowdsecurity/linux : up-to-date             
> INFO\[15-01-2022 11:07:40 AM\] crowdsecurity/sshd : up-to-date              
> INFO\[15-01-2022 11:07:40 AM\] All collections are already up-to-date       
> INFO\[15-01-2022 11:07:40 AM\] Upgrading parsers                            
> INFO\[15-01-2022 11:07:40 AM\] crowdsecurity/geoip-enrich : up-to-date      
> INFO\[15-01-2022 11:07:40 AM\] crowdsecurity/whitelists : up-to-date        
> INFO\[15-01-2022 11:07:40 AM\] crowdsecurity/dateparse-enrich : up-to-date  
> INFO\[15-01-2022 11:07:40 AM\] crowdsecurity/syslog-logs : up-to-date       
> INFO\[15-01-2022 11:07:40 AM\] crowdsecurity/sshd-logs : up-to-date         
> INFO\[15-01-2022 11:07:40 AM\] All parsers are already up-to-date           
> INFO\[15-01-2022 11:07:40 AM\] Upgrading scenarios                          
> INFO\[15-01-2022 11:07:40 AM\] crowdsecurity/ssh-slow-bf : up-to-date       
> INFO\[15-01-2022 11:07:40 AM\] crowdsecurity/ssh-bf : up-to-date            
> INFO\[15-01-2022 11:07:40 AM\] All scenarios are already up-to-date         
> INFO\[15-01-2022 11:07:40 AM\] Upgrading postoverflows                      
> INFO\[15-01-2022 11:07:40 AM\] No postoverflows installed, nothing to upgrade 
> uci: Entry not found
> Collected errors:
> \* resolve\_conffiles: Existing conffile /etc/crowdsec/online\_api\_credentials.yaml is different from the conffile in the new package. The new conffile will be placed at /etc/crowdsec/online\_api\_credentials.yaml-opkg.
> \* resolve\_conffiles: Existing conffile /etc/crowdsec/local\_api\_credentials.yaml is different from the conffile in the new package. The new conffile will be placed at /etc/crowdsec/local\_api\_credentials.yaml-opkg.
> \* resolve\_conffiles: Existing conffile /etc/crowdsec/config.yaml is different from the conffile in the new package. The new conffile will be placed at /etc/crowdsec/config.yaml-opkg.
> \`\`\`
> \`\`\`
> root@STARGATE:~# crowdsec --version
> 2022/01/15 11:08:38 version: v1.2.3-openwrt-1.2.3-2
> 2022/01/15 11:08:38 Codename: alphaga
> 2022/01/15 11:08:38 BuildDate: 2022-01-15\_10:03:09
> 2022/01/15 11:08:38 GoVersion: 1.13.8
> 2022/01/15 11:08:38 Constraint\_parser: \>= 1.0, \<= 2.0
> 2022/01/15 11:08:38 Constraint\_scenario: \>= 1.0, \< 3.0
> 2022/01/15 11:08:38 Constraint\_api: v1
> 2022/01/15 11:08:38 Constraint\_acquis: \>= 1.0, \< 2.0
> \`\`\`
> 
> Signed-off-by: Kerma Gérald \<gandalf@gk2.net\>

---

<div class="post-metadata">

**Author:** ![Gandalf](https://dub1.discourse-cdn.com/flex013/user_avatar/discourse.crowdsec.net/gandalf/32/43_2.png) [@Gandalf](https://discourse.crowdsec.net/u/Gandalf)\
**Post date:** [January 18, 2022, 7:55pm UTC](https://discourse.crowdsec.net/t/crowdsec-package-for-openwrt/225/34 "2022-01-18T19:55:46Z")

</div>

> [@Gandalf](#):
>
> New upstream relase 1.2.3 of CrowdSec proposed to OpenWrt:
> 
> [crowdsec: update from upstream latest release 1.2.3 by erdoukki · Pull Request #17615 · openwrt/packages · GitHub](https://github.com/openwrt/packages/pull/17615)

Merged, and cherry-picked to a new PR for 21.02.x

> <https://github.com/openwrt/packages/pull/17636>
>
> 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
> logging: ok
> enroll in webconsole: ok
> cscli: ok
> service reload/restart/status/disable/enable: ok
> 
> OpenWrt Version tested:
> 21.02.x
> 19.07.x
> 
> Description:
> update from latest upstream release 1.2.3
> updated copyright
> 
> Changes (from 1.2.2):
> crowdsecurity/crowdsec@v1.2.2...v1.2.3
> 
> Tests:
> \`\`\`
> root@STARGATE:~# crowdsec --version
> 2022/01/15 11:06:46 version: v1.2.2-openwrt-1.2.2-1
> 2022/01/15 11:06:46 Codename: alphaga
> 2022/01/15 11:06:46 BuildDate: 2022-01-14\_14:21:08
> 2022/01/15 11:06:46 GoVersion: 
> 2022/01/15 11:06:46 Constraint\_parser: \>= 1.0, \<= 2.0
> 2022/01/15 11:06:46 Constraint\_scenario: \>= 1.0, \< 3.0
> 2022/01/15 11:06:46 Constraint\_api: v1
> 2022/01/15 11:06:46 Constraint\_acquis: \>= 1.0, \< 2.0
> \`\`\`
> \`\`\`
> root@STARGATE:~# opkg install /root/crowdsec\_1.2.3-2\_aarch64\_cortex-a53.ipk 
> Upgrading crowdsec on root from 1.2.2-1 to 1.2.3-2...
> Configuring crowdsec.
> local API already registered...
> online API already registered...
> INFO\[15-01-2022 11:07:37 AM\] Wrote new 210740 bytes index to /etc/crowdsec/hub/.index.json 
> WARN\[15-01-2022 11:07:38 AM\] crowdsecurity/syslog-logs : overwrite        
> WARN\[15-01-2022 11:07:38 AM\] crowdsecurity/geoip-enrich : overwrite       
> WARN\[15-01-2022 11:07:38 AM\] crowdsecurity/dateparse-enrich : overwrite   
> WARN\[15-01-2022 11:07:38 AM\] crowdsecurity/sshd-logs : overwrite          
> WARN\[15-01-2022 11:07:39 AM\] crowdsecurity/ssh-bf : overwrite             
> WARN\[15-01-2022 11:07:39 AM\] crowdsecurity/ssh-slow-bf : overwrite        
> WARN\[15-01-2022 11:07:39 AM\] crowdsecurity/sshd : overwrite               
> WARN\[15-01-2022 11:07:39 AM\] crowdsecurity/sshd : overwrite               
> WARN\[15-01-2022 11:07:39 AM\] crowdsecurity/linux : overwrite              
> INFO\[15-01-2022 11:07:39 AM\] /etc/crowdsec/collections/sshd.yaml already exists. 
> INFO\[15-01-2022 11:07:39 AM\] /etc/crowdsec/collections/linux.yaml already exists. 
> INFO\[15-01-2022 11:07:39 AM\] Enabled crowdsecurity/linux                  
> INFO\[15-01-2022 11:07:39 AM\] Run 'sudo systemctl reload crowdsec' for the new configuration to be effective. 
> WARN\[15-01-2022 11:07:39 AM\] crowdsecurity/whitelists : overwrite         
> INFO\[15-01-2022 11:07:39 AM\] Enabled crowdsecurity/whitelists             
> INFO\[15-01-2022 11:07:39 AM\] Run 'sudo systemctl reload crowdsec' for the new configuration to be effective. 
> INFO\[15-01-2022 11:07:40 AM\] Upgrading collections                        
> INFO\[15-01-2022 11:07:40 AM\] crowdsecurity/linux : up-to-date             
> INFO\[15-01-2022 11:07:40 AM\] crowdsecurity/sshd : up-to-date              
> INFO\[15-01-2022 11:07:40 AM\] All collections are already up-to-date       
> INFO\[15-01-2022 11:07:40 AM\] Upgrading parsers                            
> INFO\[15-01-2022 11:07:40 AM\] crowdsecurity/geoip-enrich : up-to-date      
> INFO\[15-01-2022 11:07:40 AM\] crowdsecurity/whitelists : up-to-date        
> INFO\[15-01-2022 11:07:40 AM\] crowdsecurity/dateparse-enrich : up-to-date  
> INFO\[15-01-2022 11:07:40 AM\] crowdsecurity/syslog-logs : up-to-date       
> INFO\[15-01-2022 11:07:40 AM\] crowdsecurity/sshd-logs : up-to-date         
> INFO\[15-01-2022 11:07:40 AM\] All parsers are already up-to-date           
> INFO\[15-01-2022 11:07:40 AM\] Upgrading scenarios                          
> INFO\[15-01-2022 11:07:40 AM\] crowdsecurity/ssh-slow-bf : up-to-date       
> INFO\[15-01-2022 11:07:40 AM\] crowdsecurity/ssh-bf : up-to-date            
> INFO\[15-01-2022 11:07:40 AM\] All scenarios are already up-to-date         
> INFO\[15-01-2022 11:07:40 AM\] Upgrading postoverflows                      
> INFO\[15-01-2022 11:07:40 AM\] No postoverflows installed, nothing to upgrade 
> uci: Entry not found
> Collected errors:
> \* resolve\_conffiles: Existing conffile /etc/crowdsec/online\_api\_credentials.yaml is different from the conffile in the new package. The new conffile will be placed at /etc/crowdsec/online\_api\_credentials.yaml-opkg.
> \* resolve\_conffiles: Existing conffile /etc/crowdsec/local\_api\_credentials.yaml is different from the conffile in the new package. The new conffile will be placed at /etc/crowdsec/local\_api\_credentials.yaml-opkg.
> \* resolve\_conffiles: Existing conffile /etc/crowdsec/config.yaml is different from the conffile in the new package. The new conffile will be placed at /etc/crowdsec/config.yaml-opkg.
> \`\`\`
> \`\`\`
> root@STARGATE:~# crowdsec --version
> 2022/01/15 11:08:38 version: v1.2.3-openwrt-1.2.3-2
> 2022/01/15 11:08:38 Codename: alphaga
> 2022/01/15 11:08:38 BuildDate: 2022-01-15\_10:03:09
> 2022/01/15 11:08:38 GoVersion: 1.13.8
> 2022/01/15 11:08:38 Constraint\_parser: \>= 1.0, \<= 2.0
> 2022/01/15 11:08:38 Constraint\_scenario: \>= 1.0, \< 3.0
> 2022/01/15 11:08:38 Constraint\_api: v1
> 2022/01/15 11:08:38 Constraint\_acquis: \>= 1.0, \< 2.0
> \`\`\`
> 
> (cherry picked from commit https://github.com/openwrt/packages/commit/de41b63ca45be91273e0ea97213b2a6a29ba2a9a)
> Signed-off-by: Kerma Gérald gandalf@gk2.net

---

<div class="post-metadata">

**Author:** ![plikmuny](https://avatars.discourse-cdn.com/v4/letter/p/eb8c5e/32.png) [@plikmuny](https://discourse.crowdsec.net/u/plikmuny)\
**Post date:** [January 21, 2022, 7:52am UTC](https://discourse.crowdsec.net/t/crowdsec-package-for-openwrt/225/35 "2022-01-21T07:52:25Z")

</div>

Hi Gandalf, thanks for your help in installing Crowdsec, finally I got crowdsec running on my Rpi4 with Openwrt. But I have difficulty in choosing the collections or parsers. Do you have any default or may have collections for the post installation of crowdsec to be installed? I mean for the functioning of crowdsec, which further packages are necessary or just the setup is enough to do the job?

---

<div class="post-metadata">

**Author:** ![Gandalf](https://dub1.discourse-cdn.com/flex013/user_avatar/discourse.crowdsec.net/gandalf/32/43_2.png) [@Gandalf](https://discourse.crowdsec.net/u/Gandalf)\
**Post date:** [January 21, 2022, 9:18am UTC](https://discourse.crowdsec.net/t/crowdsec-package-for-openwrt/225/36 "2022-01-21T09:18:57Z")

</div>

The OpenWrt packages as defaults already installed with the post process package.  
It will cover all needed on OpenWrt system.

The CrowdSec team as in is TODO list to work on more specific components for OpenWrt.  
I also will help on this or may be do some parts myself.

Please take a look at the official CrowdSec documentation if you want better understanding the possibilities of the tools.  
You wan also look at the blog and tutorials already available.

The defaults setup is enough for 99% of the needs on OpenWrt.

The Wiki CrowdSec Documentation at OpenWrt Wiki still need enhancement to help end-user.  
But I always try to be as much as possible user-friendly on the OpenWrt packages version of CrowdSec.  
I may also wrote specific howto, maybe, later.

You may also try to explain the needs you want to cover which is not in the default configuration already if you want anyone to help ?

---

<div class="post-metadata">

**Author:** ![Gandalf](https://dub1.discourse-cdn.com/flex013/user_avatar/discourse.crowdsec.net/gandalf/32/43_2.png) [@Gandalf](https://discourse.crowdsec.net/u/Gandalf)\
**Post date:** [January 21, 2022, 10:12am UTC](https://discourse.crowdsec.net/t/crowdsec-package-for-openwrt/225/37 "2022-01-21T10:12:25Z")

</div>

firewall fix PR for master merged !

> <https://github.com/openwrt/packages/pull/17614>
>
> 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):

> <https://github.com/openwrt/packages/pull/17666>
>
> 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:

> <https://github.com/openwrt/packages/issues/17637>
>
> 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:

> <https://github.com/openwrt/packages/pull/17667>
>
> 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\>

> <https://github.com/openwrt/packages/pull/17668>
>
> 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 !

---

<div class="post-metadata">

**Author:** ![wulfy23](https://dub1.discourse-cdn.com/flex013/user_avatar/discourse.crowdsec.net/wulfy23/32/176_2.png) [@wulfy23](https://discourse.crowdsec.net/u/wulfy23)\
**Post date:** [January 23, 2022, 6:49am UTC](https://discourse.crowdsec.net/t/crowdsec-package-for-openwrt/225/38 "2022-01-23T06:49:30Z")

</div>

planning to fix the;

- uci-defaults firstboot problem?
- ipv6 problem?

anytime soon? not sure why you pushed to have these in the stable branch with so many issues… wasting peoples time and creating an unfillable support burden on the crowdsec community… development branch is understandable… but stable branch was a mistake…

---

<div class="post-metadata">

**Author:** ![Gandalf](https://dub1.discourse-cdn.com/flex013/user_avatar/discourse.crowdsec.net/gandalf/32/43_2.png) [@Gandalf](https://discourse.crowdsec.net/u/Gandalf)\
**Post date:** [January 23, 2022, 9:22am UTC](https://discourse.crowdsec.net/t/crowdsec-package-for-openwrt/225/40 "2022-01-23T09:22:47Z")

</div>

🤯

> **HIDDEN RIGHT OF REPLY (only) no useful technical contents**
>
> > [@wulfy23](#):
> >
> > ipv6 problem?
> 
> First time I hear of this !  
> Can you explain ?
> 
> > [@wulfy23](#):
> >
> > uci-defaults firstboot problem?
> 
> Yourself only problem.  
> Need to be studied, but not urgent !
> 
> > [@wulfy23](#):
> >
> > anytime soon?
> 
> Sure, when I get some time !
> 
> > [@wulfy23](#):
> >
> > not sure why you pushed to have these in the stable branch with so many issues…
> 
> So many issues ?  
> Really ?
> 
> > [@wulfy23](#):
> >
> > wasting peoples time and creating an unfillable support burden on the crowdsec community…
> 
> Can I laugh ?  
> Do you really think this as valuable ?  
> Do you feel better by saying again ?
> 
> > [@wulfy23](#):
> >
> > development branch is understandable…
> 
> So anyone can test and help, but not request, for himself !
> 
> > [@wulfy23](#):
> >
> > but stable branch was a mistake…
> 
> It was so hard to be accepted at first, but take _you_ on some others able to test and evaluate the CrowdSec solution !
> 
> Do you feel your sentence as judgment, or do you express your effort as valuable ?
> 
> I do not see anything from you on this work for sharing any valuable information.  
> Nothing on the Wiki, nothing as trolling and bad meaning !
> 
> @wulfy23  
> As I said, if you want _your_ need being taking done as professional service, I may be open to your sponsorship !  
> If not, now way, I get it when I can, when I want, when I need, when I feel to !  
> No one but you at the OpenWrt subject about CrowdSec package take so bad feeling and so aggressive words than you do.  
> It makes some time now you decide to become trolling all I do !  
> You take from respectuous fan feeling to bad aggressive trolling…  
> What may have I done to you ?  
> What take you to this bad minding !  
> You become bad and more bad at OpenWrt, not followed by anyone, then you get more here !?  
> Great, if you like it…  
> I do not understand, but I my have to give a try than some off the population on this earth are not able to prefer judgment and war to effort and share.  
> You take so time on this, I have to take the point.
> 
> Do you really think you will get any results with this like ?  
> I may give you just one last full answer about all, then I will ignore, and may be no apologize may ever take you back…
> 
> - I do not work for money at OpenWrt !
> - but, I trust in the best of all…
> - I am human and may do some errors !
> - but, I learn and always share my fixes…
> 
> OpenWrt is a hobby, it is a pleasure to collaborate, it is a community mainly trusting and respecting human care…  
> CrowdSec share the same spirit for me, with innovative and collaborative solution, that I share with OpenWrt people…  
> This all was a beautiful adventure, and it is just a start…
> 
> > If you find serenity and happiness, some may be jealous. Be happy anyway.  
> > (M.T.)
> 
> At all others, sorry for the noise, I may trash this “answer” if you prefer, but I need to explain, because trolls also may be save from themselves, may be ! 😇

Official OpenWrt forum CrowdSec packages topic:

> **[Crowdsec packages for OpenWrt](https://forum.openwrt.org/t/crowdsec-packages-for-openwrt/102648)**
>
> Héllo all, Here is a PR for CrowdSec v1.1.1 and CrowdSec-FireWall-Bouncer v0.0.13 I still get an issue with ARM compile and buildroot… See https://github.com/openwrt/packages/issues/16193 Is there anyone who can help to fix this, please ? ...

---

<div class="post-metadata">

**Author:** ![Gandalf](https://dub1.discourse-cdn.com/flex013/user_avatar/discourse.crowdsec.net/gandalf/32/43_2.png) [@Gandalf](https://discourse.crowdsec.net/u/Gandalf)\
**Post date:** [January 23, 2022, 10:17am UTC](https://discourse.crowdsec.net/t/crowdsec-package-for-openwrt/225/41 "2022-01-23T10:17:43Z")

</div>

> [@wulfy23](#):
>
> uci-defaults firstboot problem?

> <https://github.com/crowdsecurity/crowdsec/issues/1196>
>
> At first, it is a specific OpenWrt packaging need, but I like to share the need …here, which may be also a global enhancement.
> 
> \*\*Is your feature request related to a problem? Please describe.\*\*
> 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.
> 
> \*\*Describe the solution you'd like\*\*
> It will be better to have an complementary OpenWrt package with the GeoIP database as dependency.
> 
> \*\*Describe alternatives you've considered\*\* (Optional) 
> An offline package solution may be better than a postpone downloading tweak.
> May be also the \[geoip/geoipupdate\](https://github.com/maxmind/geoipupdate) tool will be sufficient and give us the update feature for another software.
> 
> \*\*Example of what you imagine\*\*
> I can propose to OpenWrt developers a crowdsec-data-geoip OpenWrt specific package which contains the geoip database files.
> This is a simple solution.
> This will fix the issue.
> This will not broke anything.
> This may need an update of crowdsec package dependency, but may work also without.
> This can still be enhanced later.
> 
> \*\*Additional context\*\*
> TOR or, maybe other software/tools, may also require the GeoIP DB.
> May be it is possible to have these GeoIP DB, used by all with simply storing them on a default \[DATADIR\](https://github.com/maxmind/geoipupdate/blob/bcfacbc47d5607ea4fb20ae341326cd1ae3a2326/conf/GeoIP.conf.default#L17) location.
> 
> What do you think of this ?
> Please share your experience on this...

[Previous page](https://discourse.crowdsec.net/t/crowdsec-package-for-openwrt/225.md?page=1)

[Next page](https://discourse.crowdsec.net/t/crowdsec-package-for-openwrt/225.md?page=3)