# Quick how-to for firewall bouncer on Ubiquity EdgeRouter

**URL:** <https://discourse.crowdsec.net/t/quick-how-to-for-firewall-bouncer-on-ubiquity-edgerouter/361>\
**Category:** crowdsec\
**Created:** [November 25, 2021, 7:13pm UTC](https://discourse.crowdsec.net/t/quick-how-to-for-firewall-bouncer-on-ubiquity-edgerouter/361 "2021-11-25T19:13:56Z")\
**Posts on this page:** 20\
**Page:** 1

<div class="post-metadata">

**Author:** ![mwegrzynek](https://dub1.discourse-cdn.com/flex013/user_avatar/discourse.crowdsec.net/mwegrzynek/32/191_2.png) [@mwegrzynek](https://discourse.crowdsec.net/u/mwegrzynek)\
**Post date:** [November 25, 2021, 7:13pm UTC](https://discourse.crowdsec.net/t/quick-how-to-for-firewall-bouncer-on-ubiquity-edgerouter/361/1 "2021-11-25T19:13:56Z")

</div>

Hi!

I would like to share my recipe for running a CrowdSec  
firewall bouncer on an EdgeOS router – it was tested on a ER-6P and it worked  
quite well for the last 4 months on my company’s router.

I’m assuming the following:

- you have admin access to a Linux VM or PC with Ubuntu or Arch
- you have basic Linux CLI skills (can open terminal and run commands)
- you are familiar with SSH and EdgeOS configuration
- you are running a separate machine with CrowdSec’s LocalAPI   
(running full CrowdSec installation on router should be possible,  
but I didn’t test it)
- your router is available at `yourroutersaddress`. Every time you see this word  
in the instructions replace it with your real router’s address  
(for ex. 192.168.1.1)

Things you should run on your PC are prefixed with `pc `,  
the ones to run on your router `router ` and the ones run on a LocalAPI Server - `la`.

Anyway, let’s get into business:

1. You have to install Go toolchain and Git on your Linux PC or VM:

2. Then, clone CrowdSec bouncer repository to folder on your PC:

3. Now you have to establish your router’s architecture.  
For modern Cavium-based routers (ER-4, ER-6P, ER-12, …) it’s `mips64`.  
For Mediatek-based ones (ER-X, ER-10X, …) it’s `mipsle`.

4. Build your CrowdSec bouncer’s binary

5. After a short while, the build process should finish and you’ll have a   
bouncer binary in your current folder named `crowdsec-firewall-bouncer`.

6. Connect to your LocalAPI server and create a bouncer token:

7. It’s time to SSH to your router and prepare your bouncers configuration.  
We’ll install everything int the `/config` folder as it’s the only location  
I know that survives firmware upgrades.

8. Now we need to copy our bouncer’s binary from our PC to EdgeRouter.  
From the git checkout directory on your local pc from step 2. run:

9. Now the last step: On your router run

That’s it!

I tried to proof this tutorial, but I’m sure there are at least some errors and omissions. Feel free  
to post your corrections into this thread, I’ll try to update this guide accordingly.

Enjoy!

Edit: I removed integration with EdgeOS firewall – it caused a lot of race conditions. Right now the bouncer just inserts two rules to INPUT and FORWARD chains.

---

<div class="post-metadata">

**Author:** ![thibault](https://dub1.discourse-cdn.com/flex013/user_avatar/discourse.crowdsec.net/thibault/32/2_2.png) [@thibault](https://discourse.crowdsec.net/u/thibault)\
**Post date:** [December 2, 2021, 8:19am UTC](https://discourse.crowdsec.net/t/quick-how-to-for-firewall-bouncer-on-ubiquity-edgerouter/361/2 "2021-12-02T08:19:49Z")

</div>

That’s great, thank you very much 🙂

Is there any issues you faced or suggested improvements based on your experience ?

---

<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 13, 2022, 4:18am UTC](https://discourse.crowdsec.net/t/quick-how-to-for-firewall-bouncer-on-ubiquity-edgerouter/361/3 "2022-01-13T04:18:21Z")

</div>

thankyou so much! your guide (2nd half) was extremely helpful as i’m trying to do the same on OpenWrt and no instructions are available…

i did not manage to get it running yet (no log is created) so difficult to debug… but I would have been really lost without these simple step by step guide…

I wonder why it’s so hard to find simple guides like this? many seem to just address peices or are oversimplified and miss critical steps…

---

<div class="post-metadata">

**Author:** ![mwegrzynek](https://dub1.discourse-cdn.com/flex013/user_avatar/discourse.crowdsec.net/mwegrzynek/32/191_2.png) [@mwegrzynek](https://discourse.crowdsec.net/u/mwegrzynek)\
**Post date:** [January 14, 2022, 3:52pm UTC](https://discourse.crowdsec.net/t/quick-how-to-for-firewall-bouncer-on-ubiquity-edgerouter/361/4 "2022-01-14T15:52:05Z")

</div>

Wow, nice to hear it was useful to someone 🙂 Regarding your problems with CrowdSec bouncer on OpenWRT:

- mine is writing logs to `/var/log/crowdsec-firewall.bouncer.log`, check if you have anything there,

- if there is no log file, check if the bouncer is really runing, by running on your router:

- in that case, run

Best of luck!

---

<div class="post-metadata">

**Author:** ![svgo](https://avatars.discourse-cdn.com/v4/letter/s/9d8465/32.png) [@svgo](https://discourse.crowdsec.net/u/svgo)\
**Post date:** [January 19, 2022, 8:39pm UTC](https://discourse.crowdsec.net/t/quick-how-to-for-firewall-bouncer-on-ubiquity-edgerouter/361/5 "2022-01-19T20:39:24Z")

</div>

Thank you for valuable information Tried this on Edgerouter-x and i am seeing this error

systemctl status crowdsec-firewall-bouncer.service

- crowdsec-firewall-bouncer.service - The firewall bouncer for CrowdSec  
Loaded: loaded (/config/user-data/crowdsec-firewall-bouncer.service; linked; vendor preset: enabled)  
Active: failed (Result: exit-code) since Wed 2022-01-19 15:22:52 EST; 10min ago  
Process: 5109 ExecStart=/config/user-data/crowdsec-firewall-bouncer -c /config/user-data/crowdsec/bouncers/crowdsec-firewall-bouncer.yaml (code=exited, status=203/EXEC)  
Process: 5104 ExecStartPre=/sbin/ipset create crowdsec6-blacklists hash:net timeout 3600 (code=exited, status=0/SUCCESS)  
Process: 5101 ExecStartPre=/sbin/ipset create crowdsec-blacklists hash:net timeout 3600 (code=exited, status=0/SUCCESS)  
Process: 5098 ExecStartPre=/sbin/ipset destroy crowdsec6-blacklists (code=exited, status=0/SUCCESS)  
Process: 5095 ExecStartPre=/sbin/ipset destroy crowdsec-blacklists (code=exited, status=0/SUCCESS)  
Main PID: 5109 (code=exited, status=203/EXEC)

i have compiled the binary using MIPS …any idea how i can i get this corrected ?

---

<div class="post-metadata">

**Author:** ![mwegrzynek](https://dub1.discourse-cdn.com/flex013/user_avatar/discourse.crowdsec.net/mwegrzynek/32/191_2.png) [@mwegrzynek](https://discourse.crowdsec.net/u/mwegrzynek)\
**Post date:** [January 20, 2022, 9:41am UTC](https://discourse.crowdsec.net/t/quick-how-to-for-firewall-bouncer-on-ubiquity-edgerouter/361/6 "2022-01-20T09:41:32Z")

</div>

Hi! Please run

```auto
/config/user-data/crowdsec-firewall-bouncer -t -c /config/user-data/crowdsec/bouncers/crowdsec-firewall-bouncer.yaml

```

and post results.

---

<div class="post-metadata">

**Author:** ![svgo](https://avatars.discourse-cdn.com/v4/letter/s/9d8465/32.png) [@svgo](https://discourse.crowdsec.net/u/svgo)\
**Post date:** [January 20, 2022, 4:10pm UTC](https://discourse.crowdsec.net/t/quick-how-to-for-firewall-bouncer-on-ubiquity-edgerouter/361/7 "2022-01-20T16:10:11Z")

</div>

root@EdgeRouter~# /config/user-data/crowdsec-firewall-bouncer -t -c /config/user-data/crowdsec/bouncers/crowdsec-firewall-bouncer.yaml  
-vbash: /config/user-data/crowdsec-firewall-bouncer: cannot execute binary file

also tried using the configure prompt  
root@EdgeRouter# /config/user-data/crowdsec-firewall-bouncer -t -c /config/user-data/crowdsec/bouncers/crowdsec-firewall-bouncer.yaml  
vbash: /config/user-data/crowdsec-firewall-bouncer: cannot execute binary file  
[edit]

These are commands i have ran on the linux box  
root@homeassistant:/tmp#git clone [GitHub - crowdsecurity/cs-firewall-bouncer: Crowdsec bouncer written in golang for firewalls](https://github.com/crowdsecurity/cs-firewall-bouncer.git)  
root@homeassistant:/tmp/cs-firewall-bouncer# export GOARCH=mips  
root@homeassistant:/tmp/cs-firewall-bouncer# export GOOS=linux  
root@homeassistant:/tmp/cs-firewall-bouncer# make  
root@homeassistant:/tmp/cs-firewall-bouncer# scp crowdsec-firewall-bouncer [root@10.0.0.1](mailto:root@10.0.0.1):/config/user-data/crowdsec-firewall-bouncer

Here is my router uname -a Information  
root@EdgeRouter# uname -a  
Linux EdgeRouter 4.14.54-UBNT #1 SMP Tue May 11 13:23:28 UTC 2021 mips GNU/Linux

---

<div class="post-metadata">

**Author:** ![mwegrzynek](https://dub1.discourse-cdn.com/flex013/user_avatar/discourse.crowdsec.net/mwegrzynek/32/191_2.png) [@mwegrzynek](https://discourse.crowdsec.net/u/mwegrzynek)\
**Post date:** [January 26, 2022, 4:44pm UTC](https://discourse.crowdsec.net/t/quick-how-to-for-firewall-bouncer-on-ubiquity-edgerouter/361/8 "2022-01-26T16:44:28Z")

</div>

It seems the `crowdsec-firewall-bouncer` binary is build for wrong architecture. Can you post results of running

```auto
file crowdsec-firewall-bouncer

```

on the PC you built the binary?

Mine look more or less like this:

```auto
crowdsec-firewall-bouncer: ELF 64-bit MSB executable, MIPS, MIPS-III version 1 (SYSV), statically linked, Go BuildID=C-r7kcaeDcuP6zU20pGF/PnlGdSSuAdo7RLErzG_G/GWGw0pfd9_ujG4Gz9K5t/OdRPzq1q8ScP3VebY19w, stripped

```

for a MIPS64 build.

---

<div class="post-metadata">

**Author:** ![svgo](https://avatars.discourse-cdn.com/v4/letter/s/9d8465/32.png) [@svgo](https://discourse.crowdsec.net/u/svgo)\
**Post date:** [January 26, 2022, 7:31pm UTC](https://discourse.crowdsec.net/t/quick-how-to-for-firewall-bouncer-on-ubiquity-edgerouter/361/9 "2022-01-26T19:31:22Z")

</div>

file crowdsec-firewall-bouncer  
crowdsec-firewall-bouncer: ELF 32-bit MSB executable, MIPS, MIPS32 version 1 (SYSV), statically linked, Go BuildID=AkG2AM\_R7ZIpNEYzlbJp/TlmqWEUDxk\_Pxyc7pAz1/sP5iD2AL256FGnUHGfb\_/KZQYtT\_JIvxOJ-ygnfF4, stripped

---

<div class="post-metadata">

**Author:** ![mwegrzynek](https://dub1.discourse-cdn.com/flex013/user_avatar/discourse.crowdsec.net/mwegrzynek/32/191_2.png) [@mwegrzynek](https://discourse.crowdsec.net/u/mwegrzynek)\
**Post date:** [January 26, 2022, 8:12pm UTC](https://discourse.crowdsec.net/t/quick-how-to-for-firewall-bouncer-on-ubiquity-edgerouter/361/10 "2022-01-26T20:12:05Z")

</div>

Hmm, it also seems fine. Can you double check you have the same file on your router?

---

<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:** [February 8, 2022, 1:46am UTC](https://discourse.crowdsec.net/t/quick-how-to-for-firewall-bouncer-on-ubiquity-edgerouter/361/11 "2022-02-08T01:46:48Z")

</div>

Post your `uname -ar` to check the arch.  
It must be same than the one with  
`file crowdsec-firewall-bouncer`  
You may also checked another binary of the system with file…like @mwegrzynek already suggest.  
Also take a look to your binary with  
`ls -hal crowdsec-firewall-bouncer`  
to see the status of the eXecute permission. If not already sets, add it with  
`chmod a+x crowdsec-firewall-bouncer`

---

<div class="post-metadata">

**Author:** ![svgo](https://avatars.discourse-cdn.com/v4/letter/s/9d8465/32.png) [@svgo](https://discourse.crowdsec.net/u/svgo)\
**Post date:** [February 11, 2022, 2:40pm UTC](https://discourse.crowdsec.net/t/quick-how-to-for-firewall-bouncer-on-ubiquity-edgerouter/361/12 "2022-02-11T14:40:08Z")

</div>

Thankyou @Gandalf

here is the output of uname -ar

> root@EdgeRouter:/config/user-data# ls -hal crowdsec-firewall-bouncer  
> -rwxr-xr-x 1 admin vyattacf 8.6M Jan 19 14:39 crowdsec-firewall-bouncer  
> root@EdgeRouter:/config/user-data# uname -ar  
> Linux EdgeRouter 4.14.54-UBNT #1 SMP Tue May 11 13:23:28 UTC 2021 mips GNU/Linux

---

<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:** [February 18, 2022, 1:32pm UTC](https://discourse.crowdsec.net/t/quick-how-to-for-firewall-bouncer-on-ubiquity-edgerouter/361/13 "2022-02-18T13:32:55Z")

</div>

> [@svgo](#):
>
> Process: 5109 ExecStart=/config/user-data/crowdsec-firewall-bouncer -c /config/user-data/crowdsec/bouncers/crowdsec-firewall-bouncer.yaml (code=exited, status=203/EXEC)

> <https://stackoverflow.com/questions/58790889/fail-to-start-a-process-as-a-service-code-exited-status-203-exec>

Can you simply test crowdsec from command-line ?

```auto
$ crowdsec --version

```

---

<div class="post-metadata">

**Author:** ![mwegrzynek](https://dub1.discourse-cdn.com/flex013/user_avatar/discourse.crowdsec.net/mwegrzynek/32/191_2.png) [@mwegrzynek](https://discourse.crowdsec.net/u/mwegrzynek)\
**Post date:** [March 1, 2022, 3:19pm UTC](https://discourse.crowdsec.net/t/quick-how-to-for-firewall-bouncer-on-ubiquity-edgerouter/361/14 "2022-03-01T15:19:15Z")

</div>

OK, I found a solution. For EdgeRouter-X please use

```auto
export GOARCH=mipsle

```

instead of

```auto
export GOARCH=mips

```

and it should work.

---

<div class="post-metadata">

**Author:** ![svgo](https://avatars.discourse-cdn.com/v4/letter/s/9d8465/32.png) [@svgo](https://discourse.crowdsec.net/u/svgo)\
**Post date:** [March 1, 2022, 6:59pm UTC](https://discourse.crowdsec.net/t/quick-how-to-for-firewall-bouncer-on-ubiquity-edgerouter/361/15 "2022-03-01T18:59:28Z")

</div>

> [@mwegrzynek](#):
>
> ```auto
> /config/user-data/crowdsec-firewall-bouncer -t -c /config/user-data/crowdsec/bouncers/crowdsec-firewall-bouncer.yaml
> 
> ```

Now i am not getting any errors …I will update my results shortly

---

<div class="post-metadata">

**Author:** ![svgo](https://avatars.discourse-cdn.com/v4/letter/s/9d8465/32.png) [@svgo](https://discourse.crowdsec.net/u/svgo)\
**Post date:** [March 1, 2022, 7:35pm UTC](https://discourse.crowdsec.net/t/quick-how-to-for-firewall-bouncer-on-ubiquity-edgerouter/361/16 "2022-03-01T19:35:18Z")

</div>

```auto
time="01-03-2022 14:28:20" level=info msg="backend type : ipset"
time="01-03-2022 14:28:20" level=info msg="iptables for ipv4 initiated"
time="01-03-2022 14:28:20" level=info msg="ipset clean-up : /sbin/ipset -exist flush crowdsec-blacklists"
time="01-03-2022 14:28:20" level=info msg="Checking existing set"
time="01-03-2022 14:28:21" level=info msg="iptables for ipv6 initiated"
time="01-03-2022 14:28:21" level=info msg="ipset clean-up : /sbin/ipset -exist flush crowdsec6-blacklists"
time="01-03-2022 14:28:21" level=info msg="Checking existing set"
time="01-03-2022 14:28:22" level=info msg="Processing new and deleted decisions . . ."
time="01-03-2022 14:28:34" level=info msg="Error while inserting in set (/sbin/ipset -exist add crowdsec6-blacklists 2620:96:e000:b0cc:e:2:7:4 timeout 592377): exit status 1 --> ipset v6.30: Syntax error: cannot parse 2620:96:e000:b0cc:e:2:7:4: resolving to IPv4 address failed\n"
time="01-03-2022 14:29:06" level=info msg="Error while inserting in set (/sbin/ipset -exist add crowdsec6-blacklists 2604:a880:4:1d0::2b8:0 timeout 379977): exit status 1 --> ipset v6.30: Syntax error: cannot parse 2604:a880:4:1d0::2b8:0: resolving to IPv4 address failed\n"
time="01-03-2022 14:29:09" level=info msg="Error while inserting in set (/sbin/ipset -exist add crowdsec6-blacklists 2a03:b0c0:2:f0::16c:e001 timeout 135177): exit status 1 --> ipset v6.30: Syntax error: cannot parse 2a03:b0c0:2:f0::16c:e001: resolving to IPv4 address failed\n"
time="01-03-2022 14:31:14" level=info msg="11138 decisions added"

```

It is finally working … i see IPV6 errors …i can ignore them

---

<div class="post-metadata">

**Author:** ![eugeniu](https://dub1.discourse-cdn.com/flex013/user_avatar/discourse.crowdsec.net/eugeniu/32/309_2.png) [@eugeniu](https://discourse.crowdsec.net/u/eugeniu)\
**Post date:** [March 9, 2022, 2:18pm UTC](https://discourse.crowdsec.net/t/quick-how-to-for-firewall-bouncer-on-ubiquity-edgerouter/361/17 "2022-03-09T14:18:53Z")

</div>

I cannot get it to work on an EdgeRouter 12

```auto
file crowdsec-firewall-bouncer
ELF 64-bit MSB executable, MIPS, MIPS-III version 1 (SYSV), statically linked, Go BuildID=fFO2yqjI0IwwQh_Bc-4y/o3wYN3TSY2F4foRfaKiw/Qf7TVLRfh3JbkWnwBmMB/PLA48R4IceCkaWPKIPCy, stripped

```

the service is running but with some errors:

```auto
sudo systemctl status crowdsec-firewall-bouncer
* crowdsec-firewall-bouncer.service
   Loaded: loaded (/config/user-data/crowdsec-firewall-bouncer.service; linked; vendor preset: enabled)
   Active: active (running) since Wed 2022-03-09 16:10:26 EET; 2min 29s ago
  Process: 7409 ExecStartPost=/bin/sleep 0.1 (code=exited, status=0/SUCCESS)
  Process: 7387 ExecStartPre=/sbin/ipset create crowdsec6-blacklists hash:net timeout 3600 family inet6 (code=exited, status=0/SUCCESS)
  Process: 7383 ExecStartPre=/sbin/ipset create crowdsec-blacklists hash:net timeout 3600 (code=exited, status=1/FAILURE)
  Process: 7381 ExecStartPre=/sbin/ipset destroy crowdsec6-blacklists (code=exited, status=0/SUCCESS)
  Process: 7378 ExecStartPre=/sbin/ipset destroy crowdsec-blacklists (code=exited, status=1/FAILURE)
 Main PID: 7389 (crowdsec-firewa)
   CGroup: /system.slice/crowdsec-firewall-bouncer.service
           `-7389 /config/user-data/crowdsec-firewall-bouncer -c /config/user-data/crowdsec/bouncers/crowdsec-firewall-bouncer.yaml

```

```auto
/config/user-data/crowdsec-firewall-bouncer -t -c /config/user-data/crowdsec/bouncers/crowdsec-firewall-bouncer.yaml
INFO[0000] crowdsec-firewall-bouncer v0.0.23-rc3-3-g701f619-701f6199a1ab4de24fe1fc3dbd3254f1514fff02
INFO[0000] config is valid

```

I get an error:

```auto
time="09-03-2022 16:10:29" level=info msg="Error while inserting in set (/sbin/ipset -exist add crowdsec-blacklists 222.255.148.167 timeout 596087): exit status 1 --> ipset v6.30: Timeout cannot be used: set was created without timeout support\n"
time="09-03-2022 16:10:29" level=info msg="Error while inserting in set (/sbin/ipset -exist add crowdsec-blacklists 137.184.77.9 timeout 596087): exit status 1 --> ipset v6.30: Timeout cannot be used: set was created without timeout support\n"
time="09-03-2022 16:10:29" level=info msg="Error while inserting in set (/sbin/ipset -exist add crowdsec-blacklists 106.12.176.108 timeout 596087): exit status 1 --> ipset v6.30: Timeout cannot be used: set was created without timeout support\n"
time="09-03-2022 16:10:29" level=info msg="Error while inserting in set (/sbin/ipset -exist add crowdsec-blacklists 165.232.154.178 timeout 596087): exit status 1 --> ipset v6.30: Timeout cannot be used: set was created without timeout support\n"
time="09-03-2022 16:10:29" level=info msg="Error while inserting in set (/sbin/ipset -exist add crowdsec-blacklists 119.159.234.131 timeout 596088): exit status 1 --> ipset v6.30: Timeout cannot be used: set was created without timeout support\n"
time="09-03-2022 16:10:29" level=info msg="Error while inserting in set (/sbin/ipset -exist add crowdsec-blacklists 46.101.149.216 timeout 596088): exit status 1 --> ipset v6.30: Timeout cannot be used: set was created without timeout support\n"
time="09-03-2022 16:10:29" level=info msg="300 decisions added"

```

---

<div class="post-metadata">

**Author:** ![eugeniu](https://dub1.discourse-cdn.com/flex013/user_avatar/discourse.crowdsec.net/eugeniu/32/309_2.png) [@eugeniu](https://discourse.crowdsec.net/u/eugeniu)\
**Post date:** [March 9, 2022, 4:38pm UTC](https://discourse.crowdsec.net/t/quick-how-to-for-firewall-bouncer-on-ubiquity-edgerouter/361/18 "2022-03-09T16:38:16Z")

</div>

> [@mwegrzynek](#):
>
> `set firewall group address-group crowdsec-blacklists description "Blacklist managed by CrowdSec"`

I have noticed that if a firewall address group is created before the service stars, it throws errors an it is unable to add ip addresses to it but it is not created beforehand it loasa with no errors, it is able to add addresses to the list but it is imposible to add the grup to a firewall rule…

---

<div class="post-metadata">

**Author:** ![eugeniu](https://dub1.discourse-cdn.com/flex013/user_avatar/discourse.crowdsec.net/eugeniu/32/309_2.png) [@eugeniu](https://discourse.crowdsec.net/u/eugeniu)\
**Post date:** [March 9, 2022, 6:00pm UTC](https://discourse.crowdsec.net/t/quick-how-to-for-firewall-bouncer-on-ubiquity-edgerouter/361/19 "2022-03-09T18:00:35Z")

</div>

I have tried on an ER-X and on ER12, the same errors

---

<div class="post-metadata">

**Author:** ![mwegrzynek](https://dub1.discourse-cdn.com/flex013/user_avatar/discourse.crowdsec.net/mwegrzynek/32/191_2.png) [@mwegrzynek](https://discourse.crowdsec.net/u/mwegrzynek)\
**Post date:** [March 16, 2022, 10:32am UTC](https://discourse.crowdsec.net/t/quick-how-to-for-firewall-bouncer-on-ubiquity-edgerouter/361/20 "2022-03-16T10:32:02Z")

</div>

Please try updated HOWTO, without integration with EdgeOS firewall configuration – should fix your errors.

[Next page](https://discourse.crowdsec.net/t/quick-how-to-for-firewall-bouncer-on-ubiquity-edgerouter/361.md?page=2)