# Suricata-IDS conflicts with other security applications

**URL:** <https://forum.suricata.io/t/suricata-ids-conflicts-with-other-security-applications/525>\
**Category:** Help\
**Created:** [August 20, 2020, 9:40am UTC](https://forum.suricata.io/t/suricata-ids-conflicts-with-other-security-applications/525 "2020-08-20T09:40:49Z")\
**Posts on this page:** 1\
**Showing post:** 17

<div class="post-metadata">

**Author:** ![ish](https://yyz2.discourse-cdn.com/flex030/user_avatar/forum.suricata.io/ish/32/8_2.png) [@ish](https://forum.suricata.io/u/ish)\
**Post date:** [August 23, 2020, 8:52pm UTC](https://forum.suricata.io/t/suricata-ids-conflicts-with-other-security-applications/525/17 "2020-08-23T20:52:37Z")

</div>

> [@Hack3rcon](#):
>
> I know, but the Suricata-IDS tutorial just show iptables. I don’t know how can I convert that iptables rules into the Firewalld!

So you could try this… Create `/etc/firewalld/direct.xml` to look like:

```xml
<?xml version="1.0" encoding="utf-8"?>
<direct>
  <rule ipv="ipv4" table="filter" chain="INPUT" priority="0">-j NFQUEUE --queue-bypass</rule>
  <rule ipv="ipv4" table="filter" chain="OUTPUT" priority="0">-j NFQUEUE --queue-bypass</rule>
</direct>

```

Note the `--queue-bypass`. This allows packets through if Suricata is not running. If you want packets to be dropped when Suricata is not running then remove that option.

After creating this file reload with `firewall-cmd --reload`.

This was tested on a CentOS 8 default install with Suricata installed from EPEL. The command line was simply `suricata -q0`.

---

_[View the full topic](https://forum.suricata.io/t/suricata-ids-conflicts-with-other-security-applications/525)._