# Use of Suricata and dpdk

**URL:** <https://forum.suricata.io/t/use-of-suricata-and-dpdk/2111>\
**Category:** Help\
**Tags:** dpdk\
**Created:** [January 10, 2022, 12:56pm UTC](https://forum.suricata.io/t/use-of-suricata-and-dpdk/2111 "2022-01-10T12:56:54Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![zhangmengyuan](https://avatars.discourse-cdn.com/v4/letter/z/5f9b8f/32.png) [@zhangmengyuan](https://forum.suricata.io/u/zhangmengyuan)\
**Post date:** [January 10, 2022, 12:56pm UTC](https://forum.suricata.io/t/use-of-suricata-and-dpdk/2111/1 "2022-01-10T12:56:54Z")

</div>

# Hello all, I’m pretty new to IDS and Ask a question 1、Use the Suricata master branch dependency after dpdk-19.11 compiles. 2、 ./dpdk-devbind.py -b igb\_uio 0000:05:00.0 ./dpdk-devbind.py -b igb\_uio 0000:06:00.0 ./dpdk-devbind.py -b igb\_uio 0000:07:00.0 ./dpdk-devbind.py -b igb\_uio 0000:08:00.0 3、 ./dpdk-devbind.py --status-dev net shows: Network devices using DPDK-compatible driver

0000:05:00.0 ‘I211 Gigabit Network Connection 1539’ drv=igb\_uio unused=igb  
0000:06:00.0 ‘I211 Gigabit Network Connection 1539’ drv=igb\_uio unused=igb  
0000:07:00.0 ‘I211 Gigabit Network Connection 1539’ drv=igb\_uio unused=igb  
0000:08:00.0 ‘I211 Gigabit Network Connection 1539’ drv=igb\_uio unused=igb

# Network devices using kernel driver

0000:03:00.0 ‘I211 Gigabit Network Connection 1539’ if=enp3s0 drv=igb unused=igb\_uio _Active_  
0000:04:00.0 ‘I211 Gigabit Network Connection 1539’ if=enp4s0 drv=igb unused=igb\_uio

4、  
vim /usr/local/etc/suricata/suricata.yaml  
dpdk:  
eal-params:  
proc-type: primary

# DPDK capture support

# RX queues (and TX queues in IPS mode) are assigned to cores in 1:1 ratio

interfaces:  
- interface: 0000:05:00.0 # PCIe address of the NIC port  
# Threading: possible values are either “auto” or number of threads  
…  
…  
5、  
Run suricata --dpdk  
shows  
[root@RFW dpdk-stable-19.11.11]# suricata --dpdk  
[11304] 10/1/2022 – 20:44:44 - (suricata.c:1138) (LogVersion) – This is Suricata version 7.0.0-dev (93842aa 2022-01-03) running in SYSTEM mode  
EAL: No available hugepages reported in hugepages-1048576kB  
[11304] 10/1/2022 – 20:44:44 - (runmode-dpdk.c:334) (ConfigSetIface) – [ERRCODE: SC\_ERR\_DPDK\_CONF(343)] - Interface “0000:05:00.0”: No such device

The reason for the error is to obtain the network port\_id, all network ports are invalid (unbound), but I use ./dpdk-devbind.py binds the network port.  
What are the other reasons?

---

<div class="post-metadata">

**Author:** ![zhangmengyuan](https://avatars.discourse-cdn.com/v4/letter/z/5f9b8f/32.png) [@zhangmengyuan](https://forum.suricata.io/u/zhangmengyuan)\
**Post date:** [January 11, 2022, 1:49am UTC](https://forum.suricata.io/t/use-of-suricata-and-dpdk/2111/2 "2022-01-11T01:49:28Z")

</div>

![ea9a4fd19396813b1b0d2b4bf6d8dbd](https://canada1.discourse-cdn.com/flex030/uploads/suricata/original/2X/7/777d0dd360c494d6f57ec8d0ef521d2e45dc7b84.png)  
 ![e17f69a5e85330a570280e442c014c2](https://canada1.discourse-cdn.com/flex030/uploads/suricata/original/2X/7/7f38c10034f6009f5872c2c5b6f8e3801938992f.png)

---

<div class="post-metadata">

**Author:** ![suricatalfon](https://yyz2.discourse-cdn.com/flex030/user_avatar/forum.suricata.io/suricatalfon/32/385_2.png) [@suricatalfon](https://forum.suricata.io/u/suricatalfon)\
**Post date:** [January 11, 2022, 1:40pm UTC](https://forum.suricata.io/t/use-of-suricata-and-dpdk/2111/3 "2022-01-11T13:40:25Z")

</div>

Hí,

Have you had some problem with autogen.sh and LIBTOOL with Suricata v7 ?

---

<div class="post-metadata">

**Author:** ![zhangmengyuan](https://avatars.discourse-cdn.com/v4/letter/z/5f9b8f/32.png) [@zhangmengyuan](https://forum.suricata.io/u/zhangmengyuan)\
**Post date:** [January 12, 2022, 1:17am UTC](https://forum.suricata.io/t/use-of-suricata-and-dpdk/2111/4 "2022-01-12T01:17:17Z")

</div>

First of all, thank you for your answer。  
I have compiled Suricata master branch (V7) with dpdk-20.11, and then it can be used normally.  
libdpdk.pc of pkgconfig will not be automatically generated for dpdk-19.11, and libdpdkpc of pkgconfig will be automatically generated after the compilation and installation of dpdk-20.11, which may be caused by the dependency problem when I rely on dpdk-19.11.
