[Ntop] Unable to open interface zc:

Discussion:

milad arabi

2018-05-03 08:26:19 UTC

Hi there
Our company purchase some products and I try use nprobe with ZC driver but
I got this error.

# nprobe -i zc:ens192f0 -t 60 -d 15 -P /milad -V 10 -T "%IPV4_SRC_ADDR

%IPV4_DST_ADDR %IN_PKTS %L4_DST_PORT %L4_SRC_PORT %IN_BYTES
%FLOW_START_MILLISECONDS %FLOW_END_MILLISECONDS %PROTOCOL %L7_PROTO_NAME
%IPV4_SRC_MASK %IPV4_DST_MASK %IN_SRC_MAC %OUT_DST_MAC %TCP_FLAGS"
--max-log-lines 100000 --cpu-affinity 0
01/May/2018 00:13:56 [plugin.c:177] No plugins found in ./plugins
01/May/2018 00:13:56 [plugin.c:185] Loading 23 plugins [.so] from
/usr/local/lib/nprobe/plugins
01/May/2018 00:13:56 [plugin.c:850] Unable to enable plugin DHCP Protocol
[/etc/nprobe.license.dhcp]: Missing license file
01/May/2018 00:13:56 [plugin.c:850] Unable to enable plugin DNS/LLMNR
Protocol [/etc/nprobe.license.dns]: Missing license file
01/May/2018 00:13:56 [plugin.c:850] Unable to enable plugin Export Plugin
[/etc/nprobe.license.export]: Missing license file
01/May/2018 00:13:56 [plugin.c:850] Unable to enable plugin FTP Protocol
[/etc/nprobe.license.ftp]: Missing license file
01/May/2018 00:13:56 [plugin.c:850] Unable to enable plugin GTPv0
Signaling Protocol [/etc/nprobe.license.gtpv0]: Missing license file
01/May/2018 00:13:56 [plugin.c:850] Unable to enable plugin GTPv1
Signaling Protocol [/etc/nprobe.license.gtpv1]: Missing license file
01/May/2018 00:13:56 [plugin.c:850] Unable to enable plugin GTPv2
Signaling Protocol [/etc/nprobe.license.gtpv2]: Missing license file
01/May/2018 00:13:56 [plugin.c:850] Unable to enable plugin HTTP Protocol
[/etc/nprobe.license.http]: Missing license file
01/May/2018 00:13:56 [plugin.c:850] Unable to enable plugin IMAP Protocol
[/etc/nprobe.license.email]: Missing license file
01/May/2018 00:13:56 [plugin.c:850] Unable to enable plugin Netflow-Lite
Plugin [/etc/nprobe.license.nflite]: Missing license file
01/May/2018 00:13:56 [plugin.c:850] Unable to enable plugin Oracle
Protocol [/etc/nprobe.license.oracle]: Missing license file
01/May/2018 00:13:56 [plugin.c:850] Unable to enable plugin POP3 Protocol
[/etc/nprobe.license.email]: Missing license file
01/May/2018 00:13:56 [plugin.c:850] Unable to enable plugin RTP Plugin
[/etc/nprobe.license.voip]: Missing license file
01/May/2018 00:13:56 [plugin.c:850] Unable to enable plugin S1AP Protocol
[/etc/nprobe.license.S1AP]: Missing license file
01/May/2018 00:13:56 [plugin.c:850] Unable to enable plugin SIP Plugin
[/etc/nprobe.license.voip]: Missing license file
01/May/2018 00:13:56 [plugin.c:850] Unable to enable plugin SMTP Protocol
[/etc/nprobe.license.email]: Missing license file
01/May/2018 00:13:56 [nprobe.c:3908] Valid nProbe Pro license found
01/May/2018 00:13:56 [nprobe.c:5530] WARNING: The output interfaceId is
set to 0: did you forget to use -Q perhaps ?
01/May/2018 00:13:56 [nprobe.c:5533] WARNING: The input interfaceId is set
to 0: did you forget to use -u perhaps ?
01/May/2018 00:13:56 [nprobe.c:5620] Welcome to nProbe Pro v.8.5.180430
($Revision: 6145 $) for x86_64-unknown-linux-gnu with native PF_RING
acceleration
01/May/2018 00:13:56 [nprobe.c:5630] Running on CentOS Linux release
7.4.1708 (Core)
1C6A1C5E82062206
01/May/2018 00:13:56 [nprobe.c:5678] Dumping flow files every 60 sec into
directory /milad
01/May/2018 00:13:56 [nprobe.c:5683] WARNING: -n parameter is missing.
127.0.0.1:2055 will be used.
01/May/2018 00:13:56 [nprobe.c:3562] Exporting flows towards
127.0.0.1:2055 using UDP
01/May/2018 00:13:56 [util.c:3471] CPU affinity successfully set to 0
01/May/2018 00:13:56 [nprobe.c:5708] Sample rate [packet: 1][flow
collection/export: 1/1]
01/May/2018 00:13:56 [nprobe.c:8318] Welcome to nProbe v.8.5.180430 for
x86_64-unknown-linux-gnu
01/May/2018 00:13:56 [nprobe.c:7326] Using NetFlow Packet Payload Len: 1472
01/May/2018 00:13:56 [plugin.c:1214] 0 plugin(s) enabled
01/May/2018 00:13:56 [nprobe.c:7765] Each flow is 96 bytes long
01/May/2018 00:13:56 [nprobe.c:7766] The # flows per packet has been set
to 14
01/May/2018 00:13:56 [nprobe.c:7769] IP TOS is accounted
01/May/2018 00:13:56 [util.c:465] GeoIP: loaded AS config file
/usr/share/ntopng/httpdocs/geoip/GeoIPASNum.dat
01/May/2018 00:13:56 [util.c:476] GeoIP: loaded AS IPv6 config file
/usr/share/ntopng/httpdocs/geoip/GeoIPASNumv6.dat
01/May/2018 00:13:56 [pro/pf_ring.c:356] Initializing PF_RING socket on
device zc:ens192f0..
01/May/2018 00:13:56 [nprobe.c:6383] Initializing pcap socket on device
zc:ens192f0..
*01/May/2018 00:13:56 [nprobe.c:6394] ERROR: Unable to open interface
zc:ens192f0.*
*01/May/2018 00:13:56 [nprobe.c:8427] ERROR: Unable to open interface
zc:ens192f0 (zc:ens192f0: No such device exists (SIOCGIFHWADDR: No such
device))*01/May/2018 00:13:56 [nprobe.c:8429] ERROR: Try using -i none if
you do not want capture from a NIC

#pfcount -i zc:ens192f0

pfring_open error [No such device] (pf_ring not loaded or interface
zc:ens192f0 is down ?)

# lsmod | grep 'pf_ring\|ixgbe'

ixgbe_zc 330574 0
ptp 19231 1 ixgbe_zc
pf_ring 1242512 514

lspci | grep -i 'ethernet'

0b:00.0 Ethernet controller: Intel Corporation 82599ES 10-Gigabit SFI/SFP+
Network Connection (rev 01)
0b:00.1 Ethernet controller: Intel Corporation 82599ES 10-Gigabit SFI/SFP+
Network Connection (rev 01)
1b:00.0 Ethernet controller: VMware VMXNET3 Ethernet Controller (rev 01)

# cat /proc/net/pf_ring/dev/ens192f0/info

Name: ens192f0
Index: 9
Address: 00:11:0A:67:16:5C
Polling Mode: NAPI/ZC
Type: Ethernet
Family: Intel ixgbe 82599
TX Queues: 1
RX Queues: 1
Num RX Slots: 32768
Num TX Slots: 32768

# ethtool -i ens192f0 | grep driver

driver: ixgbe
# systemctl status pf_ring
â pf_ring.service - Start/stop pfring service
Loaded: loaded (/usr/lib/systemd/system/pf_ring.service; enabled;
vendor preset: disabled)
Active: active (exited) since Mon 2018-04-30 23:22:06 +0430; 1h 1min ago
Process: 2408 ExecStop=/usr/local/bin/pf_ringctl stop (code=exited,
status=0/SUCCESS)
Process: 2532 ExecStart=/usr/local/bin/pf_ringctl start (code=exited,
status=0/SUCCESS)
Main PID: 2532 (code=exited, status=0/SUCCESS)
CGroup: /system.slice/pf_ring.service
Apr 30 23:22:01 ipdr2 systemd[1]: Starting Start/stop pfring service...
Apr 30 23:22:01 ipdr2 pf_ringctl[2532]: Starting PF_RING module: PF_RING
already loaded.[ OK ]
Apr 30 23:22:06 ipdr2 pf_ringctl[2532]: [ OK ]
Apr 30 23:22:06 ipdr2 systemd[1]: Started Start/stop pfring service.

any suggestion would be appreciate.

milad arabi

2018-05-03 09:15:36 UTC

Permalink

I ran all commands with root.

After runing pfcount,one line added to dmesg.

#dmesg | tail
[ 2806.601203] [PF_RING] Exceeded the maximum number of list items
[ 3055.221248] [PF_RING] Exceeded the maximum number of list items
[ 3055.227500] [PF_RING] Exceeded the maximum number of list items
[ 3248.227713] [PF_RING] Exceeded the maximum number of list items
[ 3254.607473] [PF_RING] Exceeded the maximum number of list items
[ 3908.178971] [PF_RING] Exceeded the maximum number of list items
[ 3908.185082] [PF_RING] Exceeded the maximum number of list items
[ 3990.816291] [PF_RING] Exceeded the maximum number of list items
[224420.870089] [PF_RING] Exceeded the maximum number of list items
[224902.613914] [PF_RING] Exceeded the maximum number of list items
# cat /usr/src/ixgbe-zc-5.0.4.1888/pf_ring.h | grep MAX_NUM_RING_SOCKETS
#define MAX_NUM_RING_SOCKETS 256
#define MAX_NUM_LIST_ELEMENTS MAX_NUM_RING_SOCKETS /* sizeof(bits_set)
[see below] */
#define MAX_NUM_ZC_BOUND_SOCKETS MAX_NUM_RING_SOCKETS
# cat /usr/local/include/linux/pf_ring.h | grep MAX_NUM_RING_SOCKETS
#define MAX_NUM_RING_SOCKETS 256
#define MAX_NUM_LIST_ELEMENTS MAX_NUM_RING_SOCKETS /* sizeof(bits_set)
[see below] */
#define MAX_NUM_ZC_BOUND_SOCKETS MAX_NUM_RING_SOCKETS
Hi
are you running the application as root?
Please also provide "dmesg | tailâ after running pfcount
Thank you
Alfredo

milad arabi

2018-05-03 09:28:49 UTC

Permalink

# cat /proc/net/pf_ring/info
PF_RING Version : 7.1.0
(dev:693af7a76b6f020a267459de87a03f6ce81b60ca)
Total rings : 256
Standard (non ZC) Options
Ring slots : 4096
Slot version : 17
Capture TX : Yes [RX+TX]
IP Defragment : No
Socket Mode : Standard
Cluster Fragment Queue : 0
Cluster Fragment Discard : 0
Please provide cat /proc/net/pf_ring/info
Alfredo
I ran all commands with root.
After runing pfcount,one line added to dmesg.

_______________________________________________
Ntop mailing list
http://listgateway.unipi.it/mailman/listinfo/ntop
_______________________________________________
Ntop mailing list
http://listgateway.unipi.it/mailman/listinfo/ntop

milad arabi

2018-05-03 09:43:26 UTC

Permalink

Sorry,I don't have any idea about pf_ring socket count.
I only try use nprobe with pf_ring zero copy on 10Gb network card.

Hi
it seems that you actually have 256 pf_ring sockets running (as youâve
seen this
is a hardcoded limit), is that expected?
Alfredo

# cat /proc/net/pf_ring/info
PF_RING Version : 7.1.0 (dev:693af7a76b6f020a267459de87a03f
6ce81b60ca)
Total rings : 256
Standard (non ZC) Options
Ring slots : 4096
Slot version : 17
Capture TX : Yes [RX+TX]
IP Defragment : No
Socket Mode : Standard
Cluster Fragment Queue : 0
Cluster Fragment Discard : 0
Please provide cat /proc/net/pf_ring/info
Alfredo
I ran all commands with root.
After runing pfcount,one line added to dmesg.

#dmesg | tail
[ 2806.601203] [PF_RING] Exceeded the maximum number of list items
[ 3055.221248] [PF_RING] Exceeded the maximum number of list items
[ 3055.227500] [PF_RING] Exceeded the maximum number of list items
[ 3248.227713] [PF_RING] Exceeded the maximum number of list items
[ 3254.607473] [PF_RING] Exceeded the maximum number of list items
[ 3908.178971] [PF_RING] Exceeded the maximum number of list items
[ 3908.185082] [PF_RING] Exceeded the maximum number of list items
[ 3990.816291] [PF_RING] Exceeded the maximum number of list items
[224420.870089] [PF_RING] Exceeded the maximum number of list items
[224902.613914] [PF_RING] Exceeded the maximum number of list items
# cat /usr/src/ixgbe-zc-5.0.4.1888/pf_ring.h | grep
MAX_NUM_RING_SOCKETS
#define MAX_NUM_RING_SOCKETS 256
#define MAX_NUM_LIST_ELEMENTS MAX_NUM_RING_SOCKETS /* sizeof(bits_set)
[see below] */
#define MAX_NUM_ZC_BOUND_SOCKETS MAX_NUM_RING_SOCKETS
# cat /usr/local/include/linux/pf_ring.h | grep MAX_NUM_RING_SOCKETS
#define MAX_NUM_RING_SOCKETS 256
#define MAX_NUM_LIST_ELEMENTS MAX_NUM_RING_SOCKETS /* sizeof(bits_set)
[see below] */
#define MAX_NUM_ZC_BOUND_SOCKETS MAX_NUM_RING_SOCKETS
Hi
are you running the application as root?
Please also provide "dmesg | tailâ after running pfcount
Thank you
Alfredo

milad arabi

2018-05-03 09:58:48 UTC

Permalink

# grep "Device\|Appl" /proc/net/pf_ring/*
/proc/net/pf_ring/2308-lo.1:Bound Device(s) : lo
/proc/net/pf_ring/2308-lo.1:Appl. Name : nProbe
/proc/net/pf_ring/2308-lo.10:Bound Device(s) : lo
/proc/net/pf_ring/2308-lo.10:Appl. Name : nProbe
/proc/net/pf_ring/2308-lo.100:Bound Device(s) : lo
/proc/net/pf_ring/2308-lo.100:Appl. Name : nProbe
/proc/net/pf_ring/2308-lo.101:Bound Device(s) : lo
/proc/net/pf_ring/2308-lo.101:Appl. Name : nProbe
/proc/net/pf_ring/2308-lo.102:Bound Device(s) : lo
/proc/net/pf_ring/2308-lo.102:Appl. Name : nProbe
/proc/net/pf_ring/2308-lo.103:Bound Device(s) : lo
/proc/net/pf_ring/2308-lo.103:Appl. Name : nProbe
/proc/net/pf_ring/2308-lo.104:Bound Device(s) : lo
/proc/net/pf_ring/2308-lo.104:Appl. Name : nProbe
/proc/net/pf_ring/2308-lo.105:Bound Device(s) : lo
/proc/net/pf_ring/2308-lo.105:Appl. Name : nProbe
/proc/net/pf_ring/2308-lo.106:Bound Device(s) : lo
/proc/net/pf_ring/2308-lo.106:Appl. Name : nProbe
/proc/net/pf_ring/2308-lo.107:Bound Device(s) : lo
/proc/net/pf_ring/2308-lo.107:Appl. Name : nProbe
/proc/net/pf_ring/2308-lo.108:Bound Device(s) : lo
/proc/net/pf_ring/2308-lo.108:Appl. Name : nProbe
/proc/net/pf_ring/2308-lo.109:Bound Device(s) : lo
/proc/net/pf_ring/2308-lo.109:Appl. Name : nProbe
/proc/net/pf_ring/2308-lo.11:Bound Device(s) : lo
/proc/net/pf_ring/2308-lo.11:Appl. Name : nProbe
/proc/net/pf_ring/2308-lo.110:Bound Device(s) : lo
/proc/net/pf_ring/2308-lo.110:Appl. Name : nProbe
/proc/net/pf_ring/2308-lo.111:Bound Device(s) : lo
/proc/net/pf_ring/2308-lo.111:Appl. Name : nProbe
/proc/net/pf_ring/2308-lo.112:Bound Device(s) : lo
/proc/net/pf_ring/2308-lo.112:Appl. Name : nProbe
/proc/net/pf_ring/2308-lo.113:Bound Device(s) : lo
/proc/net/pf_ring/2308-lo.113:Appl. Name : nProbe
/proc/net/pf_ring/2308-lo.114:Bound Device(s) : lo
/proc/net/pf_ring/2308-lo.114:Appl. Name : nProbe
/proc/net/pf_ring/2308-lo.115:Bound Device(s) : lo
/proc/net/pf_ring/2308-lo.115:Appl. Name : nProbe
/proc/net/pf_ring/2308-lo.116:Bound Device(s) : lo
/proc/net/pf_ring/2308-lo.116:Appl. Name : nProbe
/proc/net/pf_ring/2308-lo.117:Bound Device(s) : lo
/proc/net/pf_ring/2308-lo.117:Appl. Name : nProbe
/proc/net/pf_ring/2308-lo.118:Bound Device(s) : lo
/proc/net/pf_ring/2308-lo.118:Appl. Name : nProbe
/proc/net/pf_ring/2308-lo.119:Bound Device(s) : lo
/proc/net/pf_ring/2308-lo.119:Appl. Name : nProbe
/proc/net/pf_ring/2308-lo.12:Bound Device(s) : lo
/proc/net/pf_ring/2308-lo.12:Appl. Name : nProbe
/proc/net/pf_ring/2308-lo.120:Bound Device(s) : lo
/proc/net/pf_ring/2308-lo.120:Appl. Name : nProbe
/proc/net/pf_ring/2308-lo.121:Bound Device(s) : lo
/proc/net/pf_ring/2308-lo.121:Appl. Name : nProbe
/proc/net/pf_ring/2308-lo.122:Bound Device(s) : lo
/proc/net/pf_ring/2308-lo.122:Appl. Name : nProbe
/proc/net/pf_ring/2308-lo.123:Bound Device(s) : lo
/proc/net/pf_ring/2308-lo.123:Appl. Name : nProbe
/proc/net/pf_ring/2308-lo.124:Bound Device(s) : lo
/proc/net/pf_ring/2308-lo.124:Appl. Name : nProbe
/proc/net/pf_ring/2308-lo.125:Bound Device(s) : lo
/proc/net/pf_ring/2308-lo.125:Appl. Name : nProbe
/proc/net/pf_ring/2308-lo.126:Bound Device(s) : lo
/proc/net/pf_ring/2308-lo.126:Appl. Name : nProbe
/proc/net/pf_ring/2308-lo.127:Bound Device(s) : lo
/proc/net/pf_ring/2308-lo.127:Appl. Name : nProbe
/proc/net/pf_ring/2308-lo.128:Bound Device(s) : lo
/proc/net/pf_ring/2308-lo.128:Appl. Name : nProbe
/proc/net/pf_ring/2308-lo.129:Bound Device(s) : lo
/proc/net/pf_ring/2308-lo.129:Appl. Name : nProbe
/proc/net/pf_ring/2308-lo.13:Bound Device(s) : lo
/proc/net/pf_ring/2308-lo.13:Appl. Name : nProbe
/proc/net/pf_ring/2308-lo.130:Bound Device(s) : lo
/proc/net/pf_ring/2308-lo.130:Appl. Name : nProbe
/proc/net/pf_ring/2308-lo.131:Bound Device(s) : lo
/proc/net/pf_ring/2308-lo.131:Appl. Name : nProbe
/proc/net/pf_ring/2308-lo.132:Bound Device(s) : lo
/proc/net/pf_ring/2308-lo.132:Appl. Name : nProbe
/proc/net/pf_ring/2308-lo.133:Bound Device(s) : lo
/proc/net/pf_ring/2308-lo.133:Appl. Name : nProbe
/proc/net/pf_ring/2308-lo.134:Bound Device(s) : lo
/proc/net/pf_ring/2308-lo.134:Appl. Name : nProbe
/proc/net/pf_ring/2308-lo.135:Bound Device(s) : lo
/proc/net/pf_ring/2308-lo.135:Appl. Name : nProbe
/proc/net/pf_ring/2308-lo.136:Bound Device(s) : lo
/proc/net/pf_ring/2308-lo.136:Appl. Name : nProbe
/proc/net/pf_ring/2308-lo.137:Bound Device(s) : lo
/proc/net/pf_ring/2308-lo.137:Appl. Name : nProbe
/proc/net/pf_ring/2308-lo.138:Bound Device(s) : lo
/proc/net/pf_ring/2308-lo.138:Appl. Name : nProbe
/proc/net/pf_ring/2308-lo.139:Bound Device(s) : lo
/proc/net/pf_ring/2308-lo.139:Appl. Name : nProbe
/proc/net/pf_ring/2308-lo.14:Bound Device(s) : lo
/proc/net/pf_ring/2308-lo.14:Appl. Name : nProbe
/proc/net/pf_ring/2308-lo.140:Bound Device(s) : lo
/proc/net/pf_ring/2308-lo.140:Appl. Name : nProbe
/proc/net/pf_ring/2308-lo.141:Bound Device(s) : lo
/proc/net/pf_ring/2308-lo.141:Appl. Name : nProbe
/proc/net/pf_ring/2308-lo.142:Bound Device(s) : lo
/proc/net/pf_ring/2308-lo.142:Appl. Name : nProbe
/proc/net/pf_ring/2308-lo.143:Bound Device(s) : lo
/proc/net/pf_ring/2308-lo.143:Appl. Name : nProbe
/proc/net/pf_ring/2308-lo.144:Bound Device(s) : lo
/proc/net/pf_ring/2308-lo.144:Appl. Name : nProbe
/proc/net/pf_ring/2308-lo.145:Bound Device(s) : lo
/proc/net/pf_ring/2308-lo.145:Appl. Name : nProbe
/proc/net/pf_ring/2308-lo.146:Bound Device(s) : lo
/proc/net/pf_ring/2308-lo.146:Appl. Name : nProbe
/proc/net/pf_ring/2308-lo.147:Bound Device(s) : lo
/proc/net/pf_ring/2308-lo.147:Appl. Name : nProbe
/proc/net/pf_ring/2308-lo.148:Bound Device(s) : lo
/proc/net/pf_ring/2308-lo.148:Appl. Name : nProbe
/proc/net/pf_ring/2308-lo.149:Bound Device(s) : lo
/proc/net/pf_ring/2308-lo.149:Appl. Name : nProbe
/proc/net/pf_ring/2308-lo.15:Bound Device(s) : lo
/proc/net/pf_ring/2308-lo.15:Appl. Name : nProbe
/proc/net/pf_ring/2308-lo.150:Bound Device(s) : lo
/proc/net/pf_ring/2308-lo.150:Appl. Name : nProbe
/proc/net/pf_ring/2308-lo.151:Bound Device(s) : lo
/proc/net/pf_ring/2308-lo.151:Appl. Name : nProbe
/proc/net/pf_ring/2308-lo.152:Bound Device(s) : lo
/proc/net/pf_ring/2308-lo.152:Appl. Name : nProbe
/proc/net/pf_ring/2308-lo.153:Bound Device(s) : lo
/proc/net/pf_ring/2308-lo.153:Appl. Name : nProbe
/proc/net/pf_ring/2308-lo.154:Bound Device(s) : lo
/proc/net/pf_ring/2308-lo.154:Appl. Name : nProbe
/proc/net/pf_ring/2308-lo.155:Bound Device(s) : lo
/proc/net/pf_ring/2308-lo.155:Appl. Name : nProbe
/proc/net/pf_ring/2308-lo.156:Bound Device(s) : lo
/proc/net/pf_ring/2308-lo.156:Appl. Name : nProbe
/proc/net/pf_ring/2308-lo.157:Bound Device(s) : lo
/proc/net/pf_ring/2308-lo.157:Appl. Name : nProbe
/proc/net/pf_ring/2308-lo.158:Bound Device(s) : lo
/proc/net/pf_ring/2308-lo.158:Appl. Name : nProbe
/proc/net/pf_ring/2308-lo.159:Bound Device(s) : lo
/proc/net/pf_ring/2308-lo.159:Appl. Name : nProbe
/proc/net/pf_ring/2308-lo.16:Bound Device(s) : lo
/proc/net/pf_ring/2308-lo.16:Appl. Name : nProbe
/proc/net/pf_ring/2308-lo.160:Bound Device(s) : lo
/proc/net/pf_ring/2308-lo.160:Appl. Name : nProbe
/proc/net/pf_ring/2308-lo.161:Bound Device(s) : lo
/proc/net/pf_ring/2308-lo.161:Appl. Name : nProbe
/proc/net/pf_ring/2308-lo.162:Bound Device(s) : lo
/proc/net/pf_ring/2308-lo.162:Appl. Name : nProbe
/proc/net/pf_ring/2308-lo.163:Bound Device(s) : lo
/proc/net/pf_ring/2308-lo.163:Appl. Name : nProbe
/proc/net/pf_ring/2308-lo.164:Bound Device(s) : lo
/proc/net/pf_ring/2308-lo.164:Appl. Name : nProbe
/proc/net/pf_ring/2308-lo.165:Bound Device(s) : lo
/proc/net/pf_ring/2308-lo.165:Appl. Name : nProbe
/proc/net/pf_ring/2308-lo.166:Bound Device(s) : lo
/proc/net/pf_ring/2308-lo.166:Appl. Name : nProbe
/proc/net/pf_ring/2308-lo.167:Bound Device(s) : lo
/proc/net/pf_ring/2308-lo.167:Appl. Name : nProbe
/proc/net/pf_ring/2308-lo.168:Bound Device(s) : lo
/proc/net/pf_ring/2308-lo.168:Appl. Name : nProbe
/proc/net/pf_ring/2308-lo.169:Bound Device(s) : lo
/proc/net/pf_ring/2308-lo.169:Appl. Name : nProbe
/proc/net/pf_ring/2308-lo.17:Bound Device(s) : lo
/proc/net/pf_ring/2308-lo.17:Appl. Name : nProbe
/proc/net/pf_ring/2308-lo.170:Bound Device(s) : lo
/proc/net/pf_ring/2308-lo.170:Appl. Name : nProbe
/proc/net/pf_ring/2308-lo.171:Bound Device(s) : lo
/proc/net/pf_ring/2308-lo.171:Appl. Name : nProbe
/proc/net/pf_ring/2308-lo.172:Bound Device(s) : lo
/proc/net/pf_ring/2308-lo.172:Appl. Name : nProbe
/proc/net/pf_ring/2308-lo.173:Bound Device(s) : lo
/proc/net/pf_ring/2308-lo.173:Appl. Name : nProbe
/proc/net/pf_ring/2308-lo.174:Bound Device(s) : lo
/proc/net/pf_ring/2308-lo.174:Appl. Name : nProbe
/proc/net/pf_ring/2308-lo.175:Bound Device(s) : lo
/proc/net/pf_ring/2308-lo.175:Appl. Name : nProbe
/proc/net/pf_ring/2308-lo.176:Bound Device(s) : lo
/proc/net/pf_ring/2308-lo.176:Appl. Name : nProbe
/proc/net/pf_ring/2308-lo.177:Bound Device(s) : lo
/proc/net/pf_ring/2308-lo.177:Appl. Name : nProbe
/proc/net/pf_ring/2308-lo.178:Bound Device(s) : lo
/proc/net/pf_ring/2308-lo.178:Appl. Name : nProbe
/proc/net/pf_ring/2308-lo.179:Bound Device(s) : lo
/proc/net/pf_ring/2308-lo.179:Appl. Name : nProbe
/proc/net/pf_ring/2308-lo.18:Bound Device(s) : lo
/proc/net/pf_ring/2308-lo.18:Appl. Name : nProbe
/proc/net/pf_ring/2308-lo.180:Bound Device(s) : lo
/proc/net/pf_ring/2308-lo.180:Appl. Name : nProbe
/proc/net/pf_ring/2308-lo.181:Bound Device(s) : lo
/proc/net/pf_ring/2308-lo.181:Appl. Name : nProbe
/proc/net/pf_ring/2308-lo.182:Bound Device(s) : lo
/proc/net/pf_ring/2308-lo.182:Appl. Name : nProbe
/proc/net/pf_ring/2308-lo.183:Bound Device(s) : lo
/proc/net/pf_ring/2308-lo.183:Appl. Name : nProbe
/proc/net/pf_ring/2308-lo.184:Bound Device(s) : lo
/proc/net/pf_ring/2308-lo.184:Appl. Name : nProbe
/proc/net/pf_ring/2308-lo.185:Bound Device(s) : lo
/proc/net/pf_ring/2308-lo.185:Appl. Name : nProbe
/proc/net/pf_ring/2308-lo.186:Bound Device(s) : lo
/proc/net/pf_ring/2308-lo.186:Appl. Name : nProbe
/proc/net/pf_ring/2308-lo.187:Bound Device(s) : lo
/proc/net/pf_ring/2308-lo.187:Appl. Name : nProbe
/proc/net/pf_ring/2308-lo.188:Bound Device(s) : lo
/proc/net/pf_ring/2308-lo.188:Appl. Name : nProbe
/proc/net/pf_ring/2308-lo.189:Bound Device(s) : lo
/proc/net/pf_ring/2308-lo.189:Appl. Name : nProbe
/proc/net/pf_ring/2308-lo.19:Bound Device(s) : lo
/proc/net/pf_ring/2308-lo.19:Appl. Name : nProbe
/proc/net/pf_ring/2308-lo.190:Bound Device(s) : lo
/proc/net/pf_ring/2308-lo.190:Appl. Name : nProbe
/proc/net/pf_ring/2308-lo.191:Bound Device(s) : lo
/proc/net/pf_ring/2308-lo.191:Appl. Name : nProbe
/proc/net/pf_ring/2308-lo.192:Bound Device(s) : lo
/proc/net/pf_ring/2308-lo.192:Appl. Name : nProbe
/proc/net/pf_ring/2308-lo.193:Bound Device(s) : lo
/proc/net/pf_ring/2308-lo.193:Appl. Name : nProbe
/proc/net/pf_ring/2308-lo.194:Bound Device(s) : lo
/proc/net/pf_ring/2308-lo.194:Appl. Name : nProbe
/proc/net/pf_ring/2308-lo.195:Bound Device(s) : lo
/proc/net/pf_ring/2308-lo.195:Appl. Name : nProbe
/proc/net/pf_ring/2308-lo.196:Bound Device(s) : lo
/proc/net/pf_ring/2308-lo.196:Appl. Name : nProbe
/proc/net/pf_ring/2308-lo.197:Bound Device(s) : lo
/proc/net/pf_ring/2308-lo.197:Appl. Name : nProbe
/proc/net/pf_ring/2308-lo.198:Bound Device(s) : lo
/proc/net/pf_ring/2308-lo.198:Appl. Name : nProbe
/proc/net/pf_ring/2308-lo.199:Bound Device(s) : lo
/proc/net/pf_ring/2308-lo.199:Appl. Name : nProbe
/proc/net/pf_ring/2308-lo.2:Bound Device(s) : lo
/proc/net/pf_ring/2308-lo.2:Appl. Name : nProbe
/proc/net/pf_ring/2308-lo.20:Bound Device(s) : lo
/proc/net/pf_ring/2308-lo.20:Appl. Name : nProbe
/proc/net/pf_ring/2308-lo.200:Bound Device(s) : lo
/proc/net/pf_ring/2308-lo.200:Appl. Name : nProbe
/proc/net/pf_ring/2308-lo.201:Bound Device(s) : lo
/proc/net/pf_ring/2308-lo.201:Appl. Name : nProbe
/proc/net/pf_ring/2308-lo.202:Bound Device(s) : lo
/proc/net/pf_ring/2308-lo.202:Appl. Name : nProbe
/proc/net/pf_ring/2308-lo.203:Bound Device(s) : lo
/proc/net/pf_ring/2308-lo.203:Appl. Name : nProbe
/proc/net/pf_ring/2308-lo.204:Bound Device(s) : lo
/proc/net/pf_ring/2308-lo.204:Appl. Name : nProbe
/proc/net/pf_ring/2308-lo.205:Bound Device(s) : lo
/proc/net/pf_ring/2308-lo.205:Appl. Name : nProbe
/proc/net/pf_ring/2308-lo.206:Bound Device(s) : lo
/proc/net/pf_ring/2308-lo.206:Appl. Name : nProbe
/proc/net/pf_ring/2308-lo.207:Bound Device(s) : lo
/proc/net/pf_ring/2308-lo.207:Appl. Name : nProbe
/proc/net/pf_ring/2308-lo.208:Bound Device(s) : lo
/proc/net/pf_ring/2308-lo.208:Appl. Name : nProbe
/proc/net/pf_ring/2308-lo.209:Bound Device(s) : lo
/proc/net/pf_ring/2308-lo.209:Appl. Name : nProbe
/proc/net/pf_ring/2308-lo.21:Bound Device(s) : lo
/proc/net/pf_ring/2308-lo.21:Appl. Name : nProbe
/proc/net/pf_ring/2308-lo.210:Bound Device(s) : lo
/proc/net/pf_ring/2308-lo.210:Appl. Name : nProbe
/proc/net/pf_ring/2308-lo.211:Bound Device(s) : lo
/proc/net/pf_ring/2308-lo.211:Appl. Name : nProbe
/proc/net/pf_ring/2308-lo.212:Bound Device(s) : lo
/proc/net/pf_ring/2308-lo.212:Appl. Name : nProbe
/proc/net/pf_ring/2308-lo.213:Bound Device(s) : lo
/proc/net/pf_ring/2308-lo.213:Appl. Name : nProbe
/proc/net/pf_ring/2308-lo.214:Bound Device(s) : lo
/proc/net/pf_ring/2308-lo.214:Appl. Name : nProbe
/proc/net/pf_ring/2308-lo.215:Bound Device(s) : lo
/proc/net/pf_ring/2308-lo.215:Appl. Name : nProbe
/proc/net/pf_ring/2308-lo.216:Bound Device(s) : lo
/proc/net/pf_ring/2308-lo.216:Appl. Name : nProbe
/proc/net/pf_ring/2308-lo.217:Bound Device(s) : lo
/proc/net/pf_ring/2308-lo.217:Appl. Name : nProbe
/proc/net/pf_ring/2308-lo.218:Bound Device(s) : lo
/proc/net/pf_ring/2308-lo.218:Appl. Name : nProbe
/proc/net/pf_ring/2308-lo.219:Bound Device(s) : lo
/proc/net/pf_ring/2308-lo.219:Appl. Name : nProbe
/proc/net/pf_ring/2308-lo.22:Bound Device(s) : lo
/proc/net/pf_ring/2308-lo.22:Appl. Name : nProbe
/proc/net/pf_ring/2308-lo.220:Bound Device(s) : lo
/proc/net/pf_ring/2308-lo.220:Appl. Name : nProbe
/proc/net/pf_ring/2308-lo.221:Bound Device(s) : lo
/proc/net/pf_ring/2308-lo.221:Appl. Name : nProbe
/proc/net/pf_ring/2308-lo.222:Bound Device(s) : lo
/proc/net/pf_ring/2308-lo.222:Appl. Name : nProbe
/proc/net/pf_ring/2308-lo.223:Bound Device(s) : lo
/proc/net/pf_ring/2308-lo.223:Appl. Name : nProbe
/proc/net/pf_ring/2308-lo.224:Bound Device(s) : lo
/proc/net/pf_ring/2308-lo.224:Appl. Name : nProbe
/proc/net/pf_ring/2308-lo.225:Bound Device(s) : lo
/proc/net/pf_ring/2308-lo.225:Appl. Name : nProbe
/proc/net/pf_ring/2308-lo.226:Bound Device(s) : lo
/proc/net/pf_ring/2308-lo.226:Appl. Name : nProbe
/proc/net/pf_ring/2308-lo.227:Bound Device(s) : lo
/proc/net/pf_ring/2308-lo.227:Appl. Name : nProbe
/proc/net/pf_ring/2308-lo.228:Bound Device(s) : lo
/proc/net/pf_ring/2308-lo.228:Appl. Name : nProbe
/proc/net/pf_ring/2308-lo.229:Bound Device(s) : lo
/proc/net/pf_ring/2308-lo.229:Appl. Name : nProbe
/proc/net/pf_ring/2308-lo.23:Bound Device(s) : lo
/proc/net/pf_ring/2308-lo.23:Appl. Name : nProbe
/proc/net/pf_ring/2308-lo.230:Bound Device(s) : lo
/proc/net/pf_ring/2308-lo.230:Appl. Name : nProbe
/proc/net/pf_ring/2308-lo.231:Bound Device(s) : lo
/proc/net/pf_ring/2308-lo.231:Appl. Name : nProbe
/proc/net/pf_ring/2308-lo.232:Bound Device(s) : lo
/proc/net/pf_ring/2308-lo.232:Appl. Name : nProbe
/proc/net/pf_ring/2308-lo.233:Bound Device(s) : lo
/proc/net/pf_ring/2308-lo.233:Appl. Name : nProbe
/proc/net/pf_ring/2308-lo.234:Bound Device(s) : lo
/proc/net/pf_ring/2308-lo.234:Appl. Name : nProbe
/proc/net/pf_ring/2308-lo.235:Bound Device(s) : lo
/proc/net/pf_ring/2308-lo.235:Appl. Name : nProbe
/proc/net/pf_ring/2308-lo.236:Bound Device(s) : lo
/proc/net/pf_ring/2308-lo.236:Appl. Name : nProbe
/proc/net/pf_ring/2308-lo.237:Bound Device(s) : lo
/proc/net/pf_ring/2308-lo.237:Appl. Name : nProbe
/proc/net/pf_ring/2308-lo.238:Bound Device(s) : lo
/proc/net/pf_ring/2308-lo.238:Appl. Name : nProbe
/proc/net/pf_ring/2308-lo.239:Bound Device(s) : lo
/proc/net/pf_ring/2308-lo.239:Appl. Name : nProbe
/proc/net/pf_ring/2308-lo.24:Bound Device(s) : lo
/proc/net/pf_ring/2308-lo.24:Appl. Name : nProbe
/proc/net/pf_ring/2308-lo.240:Bound Device(s) : lo
/proc/net/pf_ring/2308-lo.240:Appl. Name : nProbe
/proc/net/pf_ring/2308-lo.241:Bound Device(s) : lo
/proc/net/pf_ring/2308-lo.241:Appl. Name : nProbe
/proc/net/pf_ring/2308-lo.242:Bound Device(s) : lo
/proc/net/pf_ring/2308-lo.242:Appl. Name : nProbe
/proc/net/pf_ring/2308-lo.243:Bound Device(s) : lo
/proc/net/pf_ring/2308-lo.243:Appl. Name : nProbe
/proc/net/pf_ring/2308-lo.244:Bound Device(s) : lo
/proc/net/pf_ring/2308-lo.244:Appl. Name : nProbe
/proc/net/pf_ring/2308-lo.245:Bound Device(s) : lo
/proc/net/pf_ring/2308-lo.245:Appl. Name : nProbe
/proc/net/pf_ring/2308-lo.246:Bound Device(s) : lo
/proc/net/pf_ring/2308-lo.246:Appl. Name : nProbe
/proc/net/pf_ring/2308-lo.247:Bound Device(s) : lo
/proc/net/pf_ring/2308-lo.247:Appl. Name : nProbe
/proc/net/pf_ring/2308-lo.248:Bound Device(s) : lo
/proc/net/pf_ring/2308-lo.248:Appl. Name : nProbe
/proc/net/pf_ring/2308-lo.249:Bound Device(s) : lo
/proc/net/pf_ring/2308-lo.249:Appl. Name : nProbe
/proc/net/pf_ring/2308-lo.25:Bound Device(s) : lo
/proc/net/pf_ring/2308-lo.25:Appl. Name : nProbe
/proc/net/pf_ring/2308-lo.250:Bound Device(s) : lo
/proc/net/pf_ring/2308-lo.250:Appl. Name : nProbe
/proc/net/pf_ring/2308-lo.251:Bound Device(s) : lo
/proc/net/pf_ring/2308-lo.251:Appl. Name : nProbe
/proc/net/pf_ring/2308-lo.252:Bound Device(s) : lo
/proc/net/pf_ring/2308-lo.252:Appl. Name : nProbe
/proc/net/pf_ring/2308-lo.253:Bound Device(s) : lo
/proc/net/pf_ring/2308-lo.253:Appl. Name : nProbe
/proc/net/pf_ring/2308-lo.254:Bound Device(s) : lo
/proc/net/pf_ring/2308-lo.254:Appl. Name : nProbe
/proc/net/pf_ring/2308-lo.255:Bound Device(s) : lo
/proc/net/pf_ring/2308-lo.255:Appl. Name : nProbe
/proc/net/pf_ring/2308-lo.256:Bound Device(s) : lo
/proc/net/pf_ring/2308-lo.256:Appl. Name : nProbe
/proc/net/pf_ring/2308-lo.26:Bound Device(s) : lo
/proc/net/pf_ring/2308-lo.26:Appl. Name : nProbe
/proc/net/pf_ring/2308-lo.27:Bound Device(s) : lo
/proc/net/pf_ring/2308-lo.27:Appl. Name : nProbe
/proc/net/pf_ring/2308-lo.28:Bound Device(s) : lo
/proc/net/pf_ring/2308-lo.28:Appl. Name : nProbe
/proc/net/pf_ring/2308-lo.29:Bound Device(s) : lo
/proc/net/pf_ring/2308-lo.29:Appl. Name : nProbe
/proc/net/pf_ring/2308-lo.3:Bound Device(s) : lo
/proc/net/pf_ring/2308-lo.3:Appl. Name : nProbe
/proc/net/pf_ring/2308-lo.30:Bound Device(s) : lo
/proc/net/pf_ring/2308-lo.30:Appl. Name : nProbe
/proc/net/pf_ring/2308-lo.31:Bound Device(s) : lo
/proc/net/pf_ring/2308-lo.31:Appl. Name : nProbe
/proc/net/pf_ring/2308-lo.32:Bound Device(s) : lo
/proc/net/pf_ring/2308-lo.32:Appl. Name : nProbe
/proc/net/pf_ring/2308-lo.33:Bound Device(s) : lo
/proc/net/pf_ring/2308-lo.33:Appl. Name : nProbe
/proc/net/pf_ring/2308-lo.34:Bound Device(s) : lo
/proc/net/pf_ring/2308-lo.34:Appl. Name : nProbe
/proc/net/pf_ring/2308-lo.35:Bound Device(s) : lo
/proc/net/pf_ring/2308-lo.35:Appl. Name : nProbe
/proc/net/pf_ring/2308-lo.36:Bound Device(s) : lo
/proc/net/pf_ring/2308-lo.36:Appl. Name : nProbe
/proc/net/pf_ring/2308-lo.37:Bound Device(s) : lo
/proc/net/pf_ring/2308-lo.37:Appl. Name : nProbe
/proc/net/pf_ring/2308-lo.38:Bound Device(s) : lo
/proc/net/pf_ring/2308-lo.38:Appl. Name : nProbe
/proc/net/pf_ring/2308-lo.39:Bound Device(s) : lo
/proc/net/pf_ring/2308-lo.39:Appl. Name : nProbe
/proc/net/pf_ring/2308-lo.4:Bound Device(s) : lo
/proc/net/pf_ring/2308-lo.4:Appl. Name : nProbe
/proc/net/pf_ring/2308-lo.40:Bound Device(s) : lo
/proc/net/pf_ring/2308-lo.40:Appl. Name : nProbe
/proc/net/pf_ring/2308-lo.41:Bound Device(s) : lo
/proc/net/pf_ring/2308-lo.41:Appl. Name : nProbe
/proc/net/pf_ring/2308-lo.42:Bound Device(s) : lo
/proc/net/pf_ring/2308-lo.42:Appl. Name : nProbe
/proc/net/pf_ring/2308-lo.43:Bound Device(s) : lo
/proc/net/pf_ring/2308-lo.43:Appl. Name : nProbe
/proc/net/pf_ring/2308-lo.44:Bound Device(s) : lo
/proc/net/pf_ring/2308-lo.44:Appl. Name : nProbe
/proc/net/pf_ring/2308-lo.45:Bound Device(s) : lo
/proc/net/pf_ring/2308-lo.45:Appl. Name : nProbe
/proc/net/pf_ring/2308-lo.46:Bound Device(s) : lo
/proc/net/pf_ring/2308-lo.46:Appl. Name : nProbe
/proc/net/pf_ring/2308-lo.47:Bound Device(s) : lo
/proc/net/pf_ring/2308-lo.47:Appl. Name : nProbe
/proc/net/pf_ring/2308-lo.48:Bound Device(s) : lo
/proc/net/pf_ring/2308-lo.48:Appl. Name : nProbe
/proc/net/pf_ring/2308-lo.49:Bound Device(s) : lo
/proc/net/pf_ring/2308-lo.49:Appl. Name : nProbe
/proc/net/pf_ring/2308-lo.5:Bound Device(s) : lo
/proc/net/pf_ring/2308-lo.5:Appl. Name : nProbe
/proc/net/pf_ring/2308-lo.50:Bound Device(s) : lo
/proc/net/pf_ring/2308-lo.50:Appl. Name : nProbe
/proc/net/pf_ring/2308-lo.51:Bound Device(s) : lo
/proc/net/pf_ring/2308-lo.51:Appl. Name : nProbe
/proc/net/pf_ring/2308-lo.52:Bound Device(s) : lo
/proc/net/pf_ring/2308-lo.52:Appl. Name : nProbe
/proc/net/pf_ring/2308-lo.53:Bound Device(s) : lo
/proc/net/pf_ring/2308-lo.53:Appl. Name : nProbe
/proc/net/pf_ring/2308-lo.54:Bound Device(s) : lo
/proc/net/pf_ring/2308-lo.54:Appl. Name : nProbe
/proc/net/pf_ring/2308-lo.55:Bound Device(s) : lo
/proc/net/pf_ring/2308-lo.55:Appl. Name : nProbe
/proc/net/pf_ring/2308-lo.56:Bound Device(s) : lo
/proc/net/pf_ring/2308-lo.56:Appl. Name : nProbe
/proc/net/pf_ring/2308-lo.57:Bound Device(s) : lo
/proc/net/pf_ring/2308-lo.57:Appl. Name : nProbe
/proc/net/pf_ring/2308-lo.58:Bound Device(s) : lo
/proc/net/pf_ring/2308-lo.58:Appl. Name : nProbe
/proc/net/pf_ring/2308-lo.59:Bound Device(s) : lo
/proc/net/pf_ring/2308-lo.59:Appl. Name : nProbe
/proc/net/pf_ring/2308-lo.6:Bound Device(s) : lo
/proc/net/pf_ring/2308-lo.6:Appl. Name : nProbe
/proc/net/pf_ring/2308-lo.60:Bound Device(s) : lo
/proc/net/pf_ring/2308-lo.60:Appl. Name : nProbe
/proc/net/pf_ring/2308-lo.61:Bound Device(s) : lo
/proc/net/pf_ring/2308-lo.61:Appl. Name : nProbe
/proc/net/pf_ring/2308-lo.62:Bound Device(s) : lo
/proc/net/pf_ring/2308-lo.62:Appl. Name : nProbe
/proc/net/pf_ring/2308-lo.63:Bound Device(s) : lo
/proc/net/pf_ring/2308-lo.63:Appl. Name : nProbe
/proc/net/pf_ring/2308-lo.64:Bound Device(s) : lo
/proc/net/pf_ring/2308-lo.64:Appl. Name : nProbe
/proc/net/pf_ring/2308-lo.65:Bound Device(s) : lo
/proc/net/pf_ring/2308-lo.65:Appl. Name : nProbe
/proc/net/pf_ring/2308-lo.66:Bound Device(s) : lo
/proc/net/pf_ring/2308-lo.66:Appl. Name : nProbe
/proc/net/pf_ring/2308-lo.67:Bound Device(s) : lo
/proc/net/pf_ring/2308-lo.67:Appl. Name : nProbe
/proc/net/pf_ring/2308-lo.68:Bound Device(s) : lo
/proc/net/pf_ring/2308-lo.68:Appl. Name : nProbe
/proc/net/pf_ring/2308-lo.69:Bound Device(s) : lo
/proc/net/pf_ring/2308-lo.69:Appl. Name : nProbe
/proc/net/pf_ring/2308-lo.7:Bound Device(s) : lo
/proc/net/pf_ring/2308-lo.7:Appl. Name : nProbe
/proc/net/pf_ring/2308-lo.70:Bound Device(s) : lo
/proc/net/pf_ring/2308-lo.70:Appl. Name : nProbe
/proc/net/pf_ring/2308-lo.71:Bound Device(s) : lo
/proc/net/pf_ring/2308-lo.71:Appl. Name : nProbe
/proc/net/pf_ring/2308-lo.72:Bound Device(s) : lo
/proc/net/pf_ring/2308-lo.72:Appl. Name : nProbe
/proc/net/pf_ring/2308-lo.73:Bound Device(s) : lo
/proc/net/pf_ring/2308-lo.73:Appl. Name : nProbe
/proc/net/pf_ring/2308-lo.74:Bound Device(s) : lo
/proc/net/pf_ring/2308-lo.74:Appl. Name : nProbe
/proc/net/pf_ring/2308-lo.75:Bound Device(s) : lo
/proc/net/pf_ring/2308-lo.75:Appl. Name : nProbe
/proc/net/pf_ring/2308-lo.76:Bound Device(s) : lo
/proc/net/pf_ring/2308-lo.76:Appl. Name : nProbe
/proc/net/pf_ring/2308-lo.77:Bound Device(s) : lo
/proc/net/pf_ring/2308-lo.77:Appl. Name : nProbe
/proc/net/pf_ring/2308-lo.78:Bound Device(s) : lo
/proc/net/pf_ring/2308-lo.78:Appl. Name : nProbe
/proc/net/pf_ring/2308-lo.79:Bound Device(s) : lo
/proc/net/pf_ring/2308-lo.79:Appl. Name : nProbe
/proc/net/pf_ring/2308-lo.8:Bound Device(s) : lo
/proc/net/pf_ring/2308-lo.8:Appl. Name : nProbe
/proc/net/pf_ring/2308-lo.80:Bound Device(s) : lo
/proc/net/pf_ring/2308-lo.80:Appl. Name : nProbe
/proc/net/pf_ring/2308-lo.81:Bound Device(s) : lo
/proc/net/pf_ring/2308-lo.81:Appl. Name : nProbe
/proc/net/pf_ring/2308-lo.82:Bound Device(s) : lo
/proc/net/pf_ring/2308-lo.82:Appl. Name : nProbe
/proc/net/pf_ring/2308-lo.83:Bound Device(s) : lo
/proc/net/pf_ring/2308-lo.83:Appl. Name : nProbe
/proc/net/pf_ring/2308-lo.84:Bound Device(s) : lo
/proc/net/pf_ring/2308-lo.84:Appl. Name : nProbe
/proc/net/pf_ring/2308-lo.85:Bound Device(s) : lo
/proc/net/pf_ring/2308-lo.85:Appl. Name : nProbe
/proc/net/pf_ring/2308-lo.86:Bound Device(s) : lo
/proc/net/pf_ring/2308-lo.86:Appl. Name : nProbe
/proc/net/pf_ring/2308-lo.87:Bound Device(s) : lo
/proc/net/pf_ring/2308-lo.87:Appl. Name : nProbe
/proc/net/pf_ring/2308-lo.88:Bound Device(s) : lo
/proc/net/pf_ring/2308-lo.88:Appl. Name : nProbe
/proc/net/pf_ring/2308-lo.89:Bound Device(s) : lo
/proc/net/pf_ring/2308-lo.89:Appl. Name : nProbe
/proc/net/pf_ring/2308-lo.9:Bound Device(s) : lo
/proc/net/pf_ring/2308-lo.9:Appl. Name : nProbe
/proc/net/pf_ring/2308-lo.90:Bound Device(s) : lo
/proc/net/pf_ring/2308-lo.90:Appl. Name : nProbe
/proc/net/pf_ring/2308-lo.91:Bound Device(s) : lo
/proc/net/pf_ring/2308-lo.91:Appl. Name : nProbe
/proc/net/pf_ring/2308-lo.92:Bound Device(s) : lo
/proc/net/pf_ring/2308-lo.92:Appl. Name : nProbe
/proc/net/pf_ring/2308-lo.93:Bound Device(s) : lo
/proc/net/pf_ring/2308-lo.93:Appl. Name : nProbe
/proc/net/pf_ring/2308-lo.94:Bound Device(s) : lo
/proc/net/pf_ring/2308-lo.94:Appl. Name : nProbe
/proc/net/pf_ring/2308-lo.95:Bound Device(s) : lo
/proc/net/pf_ring/2308-lo.95:Appl. Name : nProbe
/proc/net/pf_ring/2308-lo.96:Bound Device(s) : lo
/proc/net/pf_ring/2308-lo.96:Appl. Name : nProbe
/proc/net/pf_ring/2308-lo.97:Bound Device(s) : lo
/proc/net/pf_ring/2308-lo.97:Appl. Name : nProbe
/proc/net/pf_ring/2308-lo.98:Bound Device(s) : lo
/proc/net/pf_ring/2308-lo.98:Appl. Name : nProbe
/proc/net/pf_ring/2308-lo.99:Bound Device(s) : lo
/proc/net/pf_ring/2308-lo.99:Appl. Name : nProbe
grep: /proc/net/pf_ring/dev: Is a directory
grep: /proc/net/pf_ring/stats: Is a directory

This proccess exists, is that normal?

# ps aux | grep nprobe
nobody 2308 0.0 0.2 673056 342844 ? Ssl Apr30 1:41
/usr/local/bin/nprobe /run/nprobe.conf
Please provide the output of: grep "Device\|Appl" /proc/net/pf_ring/*
Alfredo
Sorry,I don't have any idea about pf_ring socket count.
I only try use nprobe with pf_ring zero copy on 10Gb network card.

Hi
it seems that you actually have 256 pf_ring sockets running (as youâve
seen this
is a hardcoded limit), is that expected?
Alfredo

# cat /proc/net/pf_ring/info
PF_RING Version : 7.1.0 (dev:693af7a76b6f020a267459de8
7a03f6ce81b60ca)
Total rings : 256
Standard (non ZC) Options
Ring slots : 4096
Slot version : 17
Capture TX : Yes [RX+TX]
IP Defragment : No
Socket Mode : Standard
Cluster Fragment Queue : 0
Cluster Fragment Discard : 0
Please provide cat /proc/net/pf_ring/info
Alfredo
I ran all commands with root.
After runing pfcount,one line added to dmesg.

#dmesg | tail
[ 2806.601203] [PF_RING] Exceeded the maximum number of list items
[ 3055.221248] [PF_RING] Exceeded the maximum number of list items
[ 3055.227500] [PF_RING] Exceeded the maximum number of list items
[ 3248.227713] [PF_RING] Exceeded the maximum number of list items
[ 3254.607473] [PF_RING] Exceeded the maximum number of list items
[ 3908.178971] [PF_RING] Exceeded the maximum number of list items
[ 3908.185082] [PF_RING] Exceeded the maximum number of list items
[ 3990.816291] [PF_RING] Exceeded the maximum number of list items
[224420.870089] [PF_RING] Exceeded the maximum number of list items
[224902.613914] [PF_RING] Exceeded the maximum number of list items
# cat /usr/src/ixgbe-zc-5.0.4.1888/pf_ring.h | grep
MAX_NUM_RING_SOCKETS
#define MAX_NUM_RING_SOCKETS 256
#define MAX_NUM_LIST_ELEMENTS MAX_NUM_RING_SOCKETS /* sizeof(bits_set)
[see below] */
#define MAX_NUM_ZC_BOUND_SOCKETS MAX_NUM_RING_SOCKETS
# cat /usr/local/include/linux/pf_ring.h | grep MAX_NUM_RING_SOCKETS
#define MAX_NUM_RING_SOCKETS 256
#define MAX_NUM_LIST_ELEMENTS MAX_NUM_RING_SOCKETS /* sizeof(bits_set)
[see below] */
#define MAX_NUM_ZC_BOUND_SOCKETS MAX_NUM_RING_SOCKETS

On Thu, May 3, 2018 at 1:24 PM, Alfredo Cardigliano <

Hi
are you running the application as root?
Please also provide "dmesg | tailâ after running pfcount
Thank you
Alfredo

milad arabi

2018-05-03 10:10:19 UTC

Permalink

CentOS Linux release 7.4.1708 (Core)
Linux test2 3.10.0-693.21.1.el7.x86_64 #1 SMP Wed Mar 7 19:03:37 UTC 2018
x86_64 x86_64 x86_64 GNU/Linux

What OS/version are you running?
Alfredo

This proccess exists, is that normal?

Hi
it seems that you actually have 256 pf_ring sockets running (as youâve
seen this
is a hardcoded limit), is that expected?
Alfredo

# cat /proc/net/pf_ring/info
PF_RING Version : 7.1.0 (dev:693af7a76b6f020a267459de8
7a03f6ce81b60ca)
Total rings : 256
Standard (non ZC) Options
Ring slots : 4096
Slot version : 17
Capture TX : Yes [RX+TX]
IP Defragment : No
Socket Mode : Standard
Cluster Fragment Queue : 0
Cluster Fragment Discard : 0

On Thu, May 3, 2018 at 1:54 PM, Alfredo Cardigliano <

Please provide cat /proc/net/pf_ring/info
Alfredo
I ran all commands with root.
After runing pfcount,one line added to dmesg.

#dmesg | tail
[ 2806.601203] [PF_RING] Exceeded the maximum number of list items
[ 3055.221248] [PF_RING] Exceeded the maximum number of list items
[ 3055.227500] [PF_RING] Exceeded the maximum number of list items
[ 3248.227713] [PF_RING] Exceeded the maximum number of list items
[ 3254.607473] [PF_RING] Exceeded the maximum number of list items
[ 3908.178971] [PF_RING] Exceeded the maximum number of list items
[ 3908.185082] [PF_RING] Exceeded the maximum number of list items
[ 3990.816291] [PF_RING] Exceeded the maximum number of list items
[224420.870089] [PF_RING] Exceeded the maximum number of list items
[224902.613914] [PF_RING] Exceeded the maximum number of list items
# cat /usr/src/ixgbe-zc-5.0.4.1888/pf_ring.h | grep
MAX_NUM_RING_SOCKETS
#define MAX_NUM_RING_SOCKETS 256
#define MAX_NUM_LIST_ELEMENTS MAX_NUM_RING_SOCKETS /* sizeof(bits_set)
[see below] */
#define MAX_NUM_ZC_BOUND_SOCKETS MAX_NUM_RING_SOCKETS
# cat /usr/local/include/linux/pf_ring.h | grep MAX_NUM_RING_SOCKETS
#define MAX_NUM_RING_SOCKETS 256
#define MAX_NUM_LIST_ELEMENTS MAX_NUM_RING_SOCKETS /* sizeof(bits_set)
[see below] */
#define MAX_NUM_ZC_BOUND_SOCKETS MAX_NUM_RING_SOCKETS

On Thu, May 3, 2018 at 1:24 PM, Alfredo Cardigliano <

Hi
are you running the application as root?
Please also provide "dmesg | tailâ after running pfcount
Thank you
Alfredo

milad arabi

2018-05-03 19:54:52 UTC

Permalink

Hi Alfredo
Thank you for your responsiveness.

I think I have some misunderstand of difference between
/etc/pf_ring/interfaces.conf , /etc/nprobe/nprobe.conf , pf_ring service
and when should I use these.
previously I put CAPTURE_INTERFACES="ens192f0" in interfaces.conf , and
nprobe.conf had -i=lo by default. and try to run nprobe -i zc: ens192f0 in
cli.

Now I try all possible situation to get result, finally I do these:

- I disable pf_ring service by this command:systemctl disable pf_ring
(this command does not affected and pf_ring service run in system startup)
- so I rename nprobe.conf to bak-nprobe.conf
- I epmty interfaces.conf

# dmesg | tail
[ 20.550170] ixgbe 0000:0b:00.0 ens192f0: detected SFP+: 6
[ 20.807227] ixgbe 0000:0b:00.0 ens192f0: detected SFP+: 6
[ 20.948811] ixgbe 0000:0b:00.0 ens192f0: NIC Link is Up 10 Gbps, Flow
Control: RX
[ 21.024222] ixgbe 0000:0b:00.1 ens192f1: detected SFP+: 5
[ 21.257108] ixgbe 0000:0b:00.1 ens192f1: detected SFP+: 5
[ 21.503244] ixgbe 0000:0b:00.1 ens192f1: detected SFP+: 5
[ 21.765299] ixgbe 0000:0b:00.1 ens192f1: detected SFP+: 5
[ 39.010813] [PF_RING] Removing lo/info from /proc
[ 39.010826] [PF_RING] Removing lo from /proc
[ 39.024827] [PF_RING] Exit network namespace ffff88182fba8000

# grep "Device\|Appl" /proc/net/pf_ring/*

grep: /proc/net/pf_ring/dev: Is a directory
grep: /proc/net/pf_ring/stats: Is a directory

# nprobe -i zc:ens192f0

.
. other outputs
.
04/May/2018 00:06:44 [nprobe.c:7766] The # flows per packet has been set
to 14
04/May/2018 00:06:44 [nprobe.c:7769] IP TOS is accounted
04/May/2018 00:06:44 [util.c:465] GeoIP: loaded AS config file
/usr/share/ntopng/httpdocs/geoip/GeoIPASNum.dat
04/May/2018 00:06:44 [util.c:476] GeoIP: loaded AS IPv6 config file
/usr/share/ntopng/httpdocs/geoip/GeoIPASNumv6.dat
04/May/2018 00:06:44 [pro/pf_ring.c:356] Initializing PF_RING socket on
device zc:ens192f0..
04/May/2018 00:06:45 [pro/pf_ring.c:398] Dumping traffic statistics on
/proc/net/pf_ring/stats/2334-ens192f0.1
.
. all the way down to 2334-ens192f0.256
.
04/May/2018 00:11:01 [pro/pf_ring.c:356] Initializing PF_RING socket on
device zc:ens192f0..
04/May/2018 00:11:02 [pro/pf_ring.c:398] Dumping traffic statistics on
/proc/net/pf_ring/stats/2334-ens192f0.256
04/May/2018 00:11:02 [pro/pf_ring.c:463] PF_RING enabled on zc:ens192f0
04/May/2018 00:11:02 [pro/pf_ring.c:356] Initializing PF_RING socket on
device zc:ens192f0..
04/May/2018 00:11:02 [nprobe.c:6383] Initializing pcap socket on device
zc:ens192f0..
04/May/2018 00:11:02 [nprobe.c:6394] ERROR: Unable to open interface
zc:ens192f0.
04/May/2018 00:11:02 [nprobe.c:8427] ERROR: Unable to open interface
zc:ens192f0 (zc:ens192f0: No such device exists (SIOCGIFHWADDR: No such
device))
04/May/2018 00:11:02 [nprobe.c:8429] ERROR: Try using -i none if you do
not want capture from a NIC

# pfcount -i zc:ens192f0

Using PF_RING v.7.1.0
10000Mb/s]
# Device RX channels: 1
# Polling threads: 1
Dumping statistics on /proc/net/pf_ring/stats/2345-ens192f0.259
=========================
Absolute Stats: [793'278 pkts total][0 pkts dropped][0.0% dropped]
[793'278 pkts rcvd][602'603'743 bytes rcvd]
=========================

nprobe -i ens192f0

this command works

Is the nprobe -i ens192f0 have zero copy ability by default? or I do
still something wrong?

Hi
It seems that you have many nprobe processes using the default
configuration (capturing from localhost) but this
is not expected (you should see just 1 process). Did you play with the
nprobe service perhaps?
I just installed a fresh system with the same OS and packages, to make
sure that this is not due to some bug in
the systemd scripts, and I am not able to reproduce this behaviour..
Please restart the machine and check the number of processes after the
boot.
Alfredo
CentOS Linux release 7.4.1708 (Core)
Linux test2 3.10.0-693.21.1.el7.x86_64 #1 SMP Wed Mar 7 19:03:37 UTC 2018
x86_64 x86_64 x86_64 GNU/Linux

What OS/version are you running?
Alfredo

This proccess exists, is that normal?

Hi
it seems that you actually have 256 pf_ring sockets running (as youâve
seen this
is a hardcoded limit), is that expected?
Alfredo

# cat /proc/net/pf_ring/info
PF_RING Version : 7.1.0 (dev:693af7a76b6f020a267459de8
7a03f6ce81b60ca)
Total rings : 256
Standard (non ZC) Options
Ring slots : 4096
Slot version : 17
Capture TX : Yes [RX+TX]
IP Defragment : No
Socket Mode : Standard
Cluster Fragment Queue : 0
Cluster Fragment Discard : 0

On Thu, May 3, 2018 at 1:54 PM, Alfredo Cardigliano <

Please provide cat /proc/net/pf_ring/info
Alfredo
I ran all commands with root.
After runing pfcount,one line added to dmesg.

#dmesg | tail
[ 2806.601203] [PF_RING] Exceeded the maximum number of list items
[ 3055.221248] [PF_RING] Exceeded the maximum number of list items
[ 3055.227500] [PF_RING] Exceeded the maximum number of list items
[ 3248.227713] [PF_RING] Exceeded the maximum number of list items
[ 3254.607473] [PF_RING] Exceeded the maximum number of list items
[ 3908.178971] [PF_RING] Exceeded the maximum number of list items
[ 3908.185082] [PF_RING] Exceeded the maximum number of list items
[ 3990.816291] [PF_RING] Exceeded the maximum number of list items
[224420.870089] [PF_RING] Exceeded the maximum number of list items
[224902.613914] [PF_RING] Exceeded the maximum number of list items
# cat /usr/src/ixgbe-zc-5.0.4.1888/pf_ring.h | grep
MAX_NUM_RING_SOCKETS
#define MAX_NUM_RING_SOCKETS 256
#define MAX_NUM_LIST_ELEMENTS MAX_NUM_RING_SOCKETS /*
sizeof(bits_set) [see below] */
#define MAX_NUM_ZC_BOUND_SOCKETS MAX_NUM_RING_SOCKETS
# cat /usr/local/include/linux/pf_ring.h | grep MAX_NUM_RING_SOCKETS
#define MAX_NUM_RING_SOCKETS 256
#define MAX_NUM_LIST_ELEMENTS MAX_NUM_RING_SOCKETS /*
sizeof(bits_set) [see below] */
#define MAX_NUM_ZC_BOUND_SOCKETS MAX_NUM_RING_SOCKETS

On Thu, May 3, 2018 at 1:24 PM, Alfredo Cardigliano <

Hi
are you running the application as root?
Please also provide "dmesg | tailâ after running pfcount
Thank you
Alfredo

milad arabi

2018-05-03 20:53:45 UTC

Permalink

Could you please check my output at https://asciinema.org/a/179653

Hi
please make sure there is no other application running on zc:ens192f0 when
you run nprobe (you can check /proc/net/pf_ring/*),
if you are still not able to run it, please provide dmesg | tail after
running nprobe -i zc:ens192f0
Alfredo
Hi Alfredo
Thank you for your responsiveness.
I think I have some misunderstand of difference between
/etc/pf_ring/interfaces.conf , /etc/nprobe/nprobe.conf , pf_ring service
and when should I use these.
previously I put CAPTURE_INTERFACES="ens192f0" in interfaces.conf , and
nprobe.conf had -i=lo by default. and try to run nprobe -i zc: ens192f0 in
cli.
- I disable pf_ring service by this command:systemctl disable pf_ring
(this command does not affected and pf_ring service run in system startup)
- so I rename nprobe.conf to bak-nprobe.conf
- I epmty interfaces.conf

# grep "Device\|Appl" /proc/net/pf_ring/*

grep: /proc/net/pf_ring/dev: Is a directory
grep: /proc/net/pf_ring/stats: Is a directory

# nprobe -i zc:ens192f0

# pfcount -i zc:ens192f0

nprobe -i ens192f0

this command works

Is the nprobe -i ens192f0 have zero copy ability by default? or I do
still something wrong?

What OS/version are you running?
Alfredo

This proccess exists, is that normal?

# ps aux | grep nprobe
nobody 2308 0.0 0.2 673056 342844 ? Ssl Apr30 1:41
/usr/local/bin/nprobe /run/nprobe.conf

On Thu, May 3, 2018 at 2:20 PM, Alfredo Cardigliano <

Please provide the output of: grep "Device\|Appl" /proc/net/pf_ring/*
Alfredo
Sorry,I don't have any idea about pf_ring socket count.
I only try use nprobe with pf_ring zero copy on 10Gb network card.
On Thu, May 3, 2018 at 2:04 PM, Alfredo Cardigliano <

Hi
it seems that you actually have 256 pf_ring sockets running (as youâve
seen this
is a hardcoded limit), is that expected?
Alfredo

# cat /proc/net/pf_ring/info
PF_RING Version : 7.1.0 (dev:693af7a76b6f020a267459de8
7a03f6ce81b60ca)
Total rings : 256
Standard (non ZC) Options
Ring slots : 4096
Slot version : 17
Capture TX : Yes [RX+TX]
IP Defragment : No
Socket Mode : Standard
Cluster Fragment Queue : 0
Cluster Fragment Discard : 0

On Thu, May 3, 2018 at 1:54 PM, Alfredo Cardigliano <

Please provide cat /proc/net/pf_ring/info
Alfredo
I ran all commands with root.
After runing pfcount,one line added to dmesg.

#dmesg | tail
[ 2806.601203] [PF_RING] Exceeded the maximum number of list items
[ 3055.221248] [PF_RING] Exceeded the maximum number of list items
[ 3055.227500] [PF_RING] Exceeded the maximum number of list items
[ 3248.227713] [PF_RING] Exceeded the maximum number of list items
[ 3254.607473] [PF_RING] Exceeded the maximum number of list items
[ 3908.178971] [PF_RING] Exceeded the maximum number of list items
[ 3908.185082] [PF_RING] Exceeded the maximum number of list items
[ 3990.816291] [PF_RING] Exceeded the maximum number of list items
[224420.870089] [PF_RING] Exceeded the maximum number of list items
[224902.613914] [PF_RING] Exceeded the maximum number of list items
# cat /usr/src/ixgbe-zc-5.0.4.1888/pf_ring.h | grep
MAX_NUM_RING_SOCKETS
#define MAX_NUM_RING_SOCKETS 256
#define MAX_NUM_LIST_ELEMENTS MAX_NUM_RING_SOCKETS /*
sizeof(bits_set) [see below] */
#define MAX_NUM_ZC_BOUND_SOCKETS MAX_NUM_RING_SOCKETS
# cat /usr/local/include/linux/pf_ring.h | grep MAX_NUM_RING_SOCKETS
#define MAX_NUM_RING_SOCKETS 256
#define MAX_NUM_LIST_ELEMENTS MAX_NUM_RING_SOCKETS /*
sizeof(bits_set) [see below] */
#define MAX_NUM_ZC_BOUND_SOCKETS MAX_NUM_RING_SOCKETS

On Thu, May 3, 2018 at 1:24 PM, Alfredo Cardigliano <

Hi
are you running the application as root?
Please also provide "dmesg | tailâ after running pfcount
Thank you
Alfredo

milad arabi

2018-05-04 10:11:21 UTC

Permalink

Hi
Thank you for your follow up.
I update nprobe(and pf_ring), test command line and nprobe.conf, on both
cases work fine.

cli output:
https://asciinema.org/a/179699

Hi
we added more verbosity and safety checks to latest nprobe to debug this
issue,
please update and send us the output again.
Thank you
Alfredo
Could you please check my output at https://asciinema.org/a/179653

Hi
please make sure there is no other application running on zc:ens192f0
when you run nprobe (you can check /proc/net/pf_ring/*),
if you are still not able to run it, please provide dmesg | tail after
running nprobe -i zc:ens192f0
Alfredo
Hi Alfredo
Thank you for your responsiveness.
I think I have some misunderstand of difference between
/etc/pf_ring/interfaces.conf , /etc/nprobe/nprobe.conf , pf_ring service
and when should I use these.
previously I put CAPTURE_INTERFACES="ens192f0" in interfaces.conf , and
nprobe.conf had -i=lo by default. and try to run nprobe -i zc: ens192f0 in
cli.
- I disable pf_ring service by this command:systemctl disable pf_ring
(this command does not affected and pf_ring service run in system startup)
- so I rename nprobe.conf to bak-nprobe.conf
- I epmty interfaces.conf

# grep "Device\|Appl" /proc/net/pf_ring/*

grep: /proc/net/pf_ring/dev: Is a directory
grep: /proc/net/pf_ring/stats: Is a directory

# nprobe -i zc:ens192f0

# pfcount -i zc:ens192f0

nprobe -i ens192f0

this command works

Is the nprobe -i ens192f0 have zero copy ability by default? or I do
still something wrong?

What OS/version are you running?
Alfredo

This proccess exists, is that normal?

# ps aux | grep nprobe
nobody 2308 0.0 0.2 673056 342844 ? Ssl Apr30 1:41
/usr/local/bin/nprobe /run/nprobe.conf

On Thu, May 3, 2018 at 2:20 PM, Alfredo Cardigliano <

Hi
it seems that you actually have 256 pf_ring sockets running (as
youâve seen this
is a hardcoded limit), is that expected?
Alfredo

# cat /proc/net/pf_ring/info
PF_RING Version : 7.1.0 (dev:693af7a76b6f020a267459de8
7a03f6ce81b60ca)
Total rings : 256
Standard (non ZC) Options
Ring slots : 4096
Slot version : 17
Capture TX : Yes [RX+TX]
IP Defragment : No
Socket Mode : Standard
Cluster Fragment Queue : 0
Cluster Fragment Discard : 0

On Thu, May 3, 2018 at 1:54 PM, Alfredo Cardigliano <

Please provide cat /proc/net/pf_ring/info
Alfredo
I ran all commands with root.
After runing pfcount,one line added to dmesg.

#dmesg | tail
[ 2806.601203] [PF_RING] Exceeded the maximum number of list items
[ 3055.221248] [PF_RING] Exceeded the maximum number of list items
[ 3055.227500] [PF_RING] Exceeded the maximum number of list items
[ 3248.227713] [PF_RING] Exceeded the maximum number of list items
[ 3254.607473] [PF_RING] Exceeded the maximum number of list items
[ 3908.178971] [PF_RING] Exceeded the maximum number of list items
[ 3908.185082] [PF_RING] Exceeded the maximum number of list items
[ 3990.816291] [PF_RING] Exceeded the maximum number of list items
[224420.870089] [PF_RING] Exceeded the maximum number of list items
[224902.613914] [PF_RING] Exceeded the maximum number of list items
# cat /usr/src/ixgbe-zc-5.0.4.1888/pf_ring.h | grep
MAX_NUM_RING_SOCKETS
#define MAX_NUM_RING_SOCKETS 256
#define MAX_NUM_LIST_ELEMENTS MAX_NUM_RING_SOCKETS /*
sizeof(bits_set) [see below] */
#define MAX_NUM_ZC_BOUND_SOCKETS MAX_NUM_RING_SOCKETS
# cat /usr/local/include/linux/pf_ring.h | grep
MAX_NUM_RING_SOCKETS
#define MAX_NUM_RING_SOCKETS 256
#define MAX_NUM_LIST_ELEMENTS MAX_NUM_RING_SOCKETS /*
sizeof(bits_set) [see below] */
#define MAX_NUM_ZC_BOUND_SOCKETS MAX_NUM_RING_SOCKETS

On Thu, May 3, 2018 at 1:24 PM, Alfredo Cardigliano <

Hi
are you running the application as root?
Please also provide "dmesg | tailâ after running pfcount
Thank you
Alfredo