Mailing List Archive

help with packet dropping when bursting traffic
Hi there, I am struggling with a weird packet dropping. My environment is pfring zc with intel x520 nic. I started a pfcount to listen to one of 10Gb port of this card. When a burst traffic up to 2Gb came in, ifconfig showed thousands packets were dropped. The reason I called it weird is when the traffic remained in 2Gb, no packet dropped any more.

Any comment?
Re: help with packet dropping when bursting traffic [ In reply to ]
Hi
please provide:
- the pfcount command you are using
- cat /proc/net/pf_ring/dev/<interface>/info
- cat /proc/cpuinfo
- lstopo

Thank you
Alfredo

> On 24 Nov 2019, at 07:38, Yong Wang <cnwangyong@gmail.com> wrote:
>
>
> Hi there, I am struggling with a weird packet dropping. My environment is pfring zc with intel x520 nic. I started a pfcount to listen to one of 10Gb port of this card. When a burst traffic up to 2Gb came in, ifconfig showed thousands packets were dropped. The reason I called it weird is when the traffic remained in 2Gb, no packet dropped any more.
>
> Any comment?
> _______________________________________________
> Ntop-misc mailing list
> Ntop-misc@listgateway.unipi.it <mailto:Ntop-misc@listgateway.unipi.it>
> http://listgateway.unipi.it/mailman/listinfo/ntop-misc <http://listgateway.unipi.it/mailman/listinfo/ntop-misc>
Re: help with packet dropping when bursting traffic [ In reply to ]
Hi Alfredo, sorry for the late reply. I have being try to solve it but
unfortunately it doesn't work so far. So, here is some updated info for you:

what happened:
about 2Gbps captured by a 10Gb port, zcount reported no drops, ethtool -S
reported no rs_dropped, but ip -s link report more than 300K packets
dropped.

-OS:
centos 7, kernel 3.10

-capture port:
82599EB based dual-port card

-command line:
zcount -i p1p1

- cat /proc/net/pf_ring/dev/<interface>/info
[root@r510 p1p1]# cat info
Name: p1p1
Index: 10
Address: 48:F8:DB:7E:DA: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


[root@r510 pf_ring]# cat 31372-p1p1.120
Bound Device(s) : p1p1
Active : 1
Breed : Standard
Appl. Name : pfring-zc-99-p1p1
Socket Mode : RX only
Capture Direction : RX only
Sampling Rate : 1
Filtering Sampling Rate: 0
IP Defragment : No
BPF Filtering : Disabled
Sw Filt Hash Rules : 0
Sw Filt WC Rules : 0
Sw Filt Hash Match : 0
Sw Filt Hash Miss : 0
Sw Filt Hash Filtered : 0
Hw Filt Rules : 0
Poll Pkt Watermark : 128
Num Poll Calls : 0
Poll Watermark Timeout : 0
Channel Id Mask : 0xFFFFFFFFFFFFFFFF
VLAN Id : 65535
Slot Version : 17 [7.5.0]
Min Num Slots : 65538
Bucket Len : 1518
Slot Len : 1568 [bucket+header]
Tot Memory : 102772736
Tot Packets : 20306173
Tot Pkt Lost : 0
Tot Insert : 20306173
Tot Read : 20306172
Insert Offset : 37222704
Remove Offset : 37220768
Num Free Slots : 65536
Reflect: Fwd Ok : 0
Reflect: Fwd Errors : 0



- cat /proc/cpuinfo
24core cpu, this is the last one, all others looks like this:

processor : 23
vendor_id : GenuineIntel
cpu family : 6
model : 44
model name : Intel(R) Xeon(R) CPU X5675 @ 3.07GHz
stepping : 2
microcode : 0x1f
cpu MHz : 3066.920
cache size : 12288 KB
physical id : 0
siblings : 12
core id : 10
cpu cores : 6
apicid : 21
initial apicid : 21
fpu : yes
fpu_exception : yes
cpuid level : 11
wp : yes
flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca
cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht
tm pbe syscall nx pdpe1gb rdtscp lm constant_tsc
arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc aperfmperf
eagerfpu pn i pclmulqdq dtes64 monitor
ds_cpl vmx smx est tm2 ssse3 cx16 xtpr pdcm pcid dca sse4_1 sse4_2 popcnt
aes lahf_lm ssbd ibrs ibpb st ibp
tpr_shadow vnmi flexpriority ept vpid dtherm ida arat spec_ctrl intel_stibp
flush_l1d
bogomips : 6133.23
clflush size : 64
cache_alignment : 64
address sizes : 40 bits physical, 48 bits virtual
power management:


- lstopo
[root@r510 tmp]# lstopo-no-graphics
Machine (64GB total)
NUMANode L#0 (P#0 32GB) + Package L#0 + L3 L#0 (12MB)
L2 L#0 (256KB) + L1d L#0 (32KB) + L1i L#0 (32KB) + Core L#0
PU L#0 (P#0)
PU L#1 (P#12)
L2 L#1 (256KB) + L1d L#1 (32KB) + L1i L#1 (32KB) + Core L#1
PU L#2 (P#2)
PU L#3 (P#14)
L2 L#2 (256KB) + L1d L#2 (32KB) + L1i L#2 (32KB) + Core L#2
PU L#4 (P#4)
PU L#5 (P#16)
L2 L#3 (256KB) + L1d L#3 (32KB) + L1i L#3 (32KB) + Core L#3
PU L#6 (P#6)
PU L#7 (P#18)
L2 L#4 (256KB) + L1d L#4 (32KB) + L1i L#4 (32KB) + Core L#4
PU L#8 (P#8)
PU L#9 (P#20)
L2 L#5 (256KB) + L1d L#5 (32KB) + L1i L#5 (32KB) + Core L#5
PU L#10 (P#10)
PU L#11 (P#22)
NUMANode L#1 (P#1 32GB) + Package L#1 + L3 L#1 (12MB)
L2 L#6 (256KB) + L1d L#6 (32KB) + L1i L#6 (32KB) + Core L#6
PU L#12 (P#1)
PU L#13 (P#13)
L2 L#7 (256KB) + L1d L#7 (32KB) + L1i L#7 (32KB) + Core L#7
PU L#14 (P#3)
PU L#15 (P#15)
L2 L#8 (256KB) + L1d L#8 (32KB) + L1i L#8 (32KB) + Core L#8
PU L#16 (P#5)
PU L#17 (P#17)
L2 L#9 (256KB) + L1d L#9 (32KB) + L1i L#9 (32KB) + Core L#9
PU L#18 (P#7)
PU L#19 (P#19)
L2 L#10 (256KB) + L1d L#10 (32KB) + L1i L#10 (32KB) + Core L#10
PU L#20 (P#9)
PU L#21 (P#21)
L2 L#11 (256KB) + L1d L#11 (32KB) + L1i L#11 (32KB) + Core L#11
PU L#22 (P#11)
PU L#23 (P#23)
Misc(MemoryModule)
Misc(MemoryModule)
Misc(MemoryModule)
Misc(MemoryModule)
Misc(MemoryModule)
Misc(MemoryModule)
Misc(MemoryModule)
Misc(MemoryModule)
HostBridge L#0
PCIBridge
PCI 14e4:163b
Net L#0 "em1"
PCI 14e4:163b
Net L#1 "em2"
PCIBridge
PCI 1000:0079
Block(Disk) L#2 "sda"
PCIBridge
PCIBridge
PCIBridge
PCI 8086:10e8
Net L#3 "p2p1"
PCI 8086:10e8
Net L#4 "p2p2"
PCIBridge
PCI 8086:10e8
Net L#5 "p2p3"
PCI 8086:10e8
Net L#6 "p2p4"
PCIBridge
PCI 8086:10fb
Net L#7 "p1p1"
PCI 8086:10fb
Net L#8 "p1p2"
PCIBridge
PCI 102b:0532
GPU L#9 "card0"
GPU L#10 "controlD64"







On Mon, Nov 25, 2019 at 4:11 PM Alfredo Cardigliano <cardigliano@ntop.org>
wrote:

> Hi
> please provide:
> - the pfcount command you are using
> - cat /proc/net/pf_ring/dev/<interface>/info
> - cat /proc/cpuinfo
> - lstopo
>
> Thank you
> Alfredo
>
> On 24 Nov 2019, at 07:38, Yong Wang <cnwangyong@gmail.com> wrote:
>
>
> Hi there, I am struggling with a weird packet dropping. My environment is
> pfring zc with intel x520 nic. I started a pfcount to listen to one of 10Gb
> port of this card. When a burst traffic up to 2Gb came in, ifconfig showed
> thousands packets were dropped. The reason I called it weird is when the
> traffic remained in 2Gb, no packet dropped any more.
>
> Any comment?
> _______________________________________________
> Ntop-misc mailing list
> Ntop-misc@listgateway.unipi.it
> http://listgateway.unipi.it/mailman/listinfo/ntop-misc
>
>
> _______________________________________________
> Ntop-misc mailing list
> Ntop-misc@listgateway.unipi.it
> http://listgateway.unipi.it/mailman/listinfo/ntop-misc
Re: help with packet dropping when bursting traffic [ In reply to ]
Hi
it seems you are not actually enabling ZC capture, please add the zc: prefix
to the interface name (e.g. -i zc:p1p1)

Regards
Alfredo

> On 25 Dec 2019, at 06:46, Wang <cnwangyong@gmail.com> wrote:
>
> Hi Alfredo, sorry for the late reply. I have being try to solve it but unfortunately it doesn't work so far. So, here is some updated info for you:
>
> what happened:
> about 2Gbps captured by a 10Gb port, zcount reported no drops, ethtool -S reported no rs_dropped, but ip -s link report more than 300K packets dropped.
>
> -OS:
> centos 7, kernel 3.10
>
> -capture port:
> 82599EB based dual-port card
>
> -command line:
> zcount -i p1p1
>
> - cat /proc/net/pf_ring/dev/<interface>/info
> [root@r510 p1p1]# cat info
> Name: p1p1
> Index: 10
> Address: 48:F8:DB:7E:DA: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
>
>
> [root@r510 pf_ring]# cat 31372-p1p1.120
> Bound Device(s) : p1p1
> Active : 1
> Breed : Standard
> Appl. Name : pfring-zc-99-p1p1
> Socket Mode : RX only
> Capture Direction : RX only
> Sampling Rate : 1
> Filtering Sampling Rate: 0
> IP Defragment : No
> BPF Filtering : Disabled
> Sw Filt Hash Rules : 0
> Sw Filt WC Rules : 0
> Sw Filt Hash Match : 0
> Sw Filt Hash Miss : 0
> Sw Filt Hash Filtered : 0
> Hw Filt Rules : 0
> Poll Pkt Watermark : 128
> Num Poll Calls : 0
> Poll Watermark Timeout : 0
> Channel Id Mask : 0xFFFFFFFFFFFFFFFF
> VLAN Id : 65535
> Slot Version : 17 [7.5.0]
> Min Num Slots : 65538
> Bucket Len : 1518
> Slot Len : 1568 [bucket+header]
> Tot Memory : 102772736
> Tot Packets : 20306173
> Tot Pkt Lost : 0
> Tot Insert : 20306173
> Tot Read : 20306172
> Insert Offset : 37222704
> Remove Offset : 37220768
> Num Free Slots : 65536
> Reflect: Fwd Ok : 0
> Reflect: Fwd Errors : 0
>
>
>
> - cat /proc/cpuinfo
> 24core cpu, this is the last one, all others looks like this:
>
> processor : 23
> vendor_id : GenuineIntel
> cpu family : 6
> model : 44
> model name : Intel(R) Xeon(R) CPU X5675 @ 3.07GHz
> stepping : 2
> microcode : 0x1f
> cpu MHz : 3066.920
> cache size : 12288 KB
> physical id : 0
> siblings : 12
> core id : 10
> cpu cores : 6
> apicid : 21
> initial apicid : 21
> fpu : yes
> fpu_exception : yes
> cpuid level : 11
> wp : yes
> flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx pdpe1gb rdtscp lm constant_tsc arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc aperfmperf eagerfpu pn i pclmulqdq dtes64 monitor ds_cpl vmx smx est tm2 ssse3 cx16 xtpr pdcm pcid dca sse4_1 sse4_2 popcnt aes lahf_lm ssbd ibrs ibpb st ibp tpr_shadow vnmi flexpriority ept vpid dtherm ida arat spec_ctrl intel_stibp flush_l1d
> bogomips : 6133.23
> clflush size : 64
> cache_alignment : 64
> address sizes : 40 bits physical, 48 bits virtual
> power management:
>
>
> - lstopo
> [root@r510 tmp]# lstopo-no-graphics
> Machine (64GB total)
> NUMANode L#0 (P#0 32GB) + Package L#0 + L3 L#0 (12MB)
> L2 L#0 (256KB) + L1d L#0 (32KB) + L1i L#0 (32KB) + Core L#0
> PU L#0 (P#0)
> PU L#1 (P#12)
> L2 L#1 (256KB) + L1d L#1 (32KB) + L1i L#1 (32KB) + Core L#1
> PU L#2 (P#2)
> PU L#3 (P#14)
> L2 L#2 (256KB) + L1d L#2 (32KB) + L1i L#2 (32KB) + Core L#2
> PU L#4 (P#4)
> PU L#5 (P#16)
> L2 L#3 (256KB) + L1d L#3 (32KB) + L1i L#3 (32KB) + Core L#3
> PU L#6 (P#6)
> PU L#7 (P#18)
> L2 L#4 (256KB) + L1d L#4 (32KB) + L1i L#4 (32KB) + Core L#4
> PU L#8 (P#8)
> PU L#9 (P#20)
> L2 L#5 (256KB) + L1d L#5 (32KB) + L1i L#5 (32KB) + Core L#5
> PU L#10 (P#10)
> PU L#11 (P#22)
> NUMANode L#1 (P#1 32GB) + Package L#1 + L3 L#1 (12MB)
> L2 L#6 (256KB) + L1d L#6 (32KB) + L1i L#6 (32KB) + Core L#6
> PU L#12 (P#1)
> PU L#13 (P#13)
> L2 L#7 (256KB) + L1d L#7 (32KB) + L1i L#7 (32KB) + Core L#7
> PU L#14 (P#3)
> PU L#15 (P#15)
> L2 L#8 (256KB) + L1d L#8 (32KB) + L1i L#8 (32KB) + Core L#8
> PU L#16 (P#5)
> PU L#17 (P#17)
> L2 L#9 (256KB) + L1d L#9 (32KB) + L1i L#9 (32KB) + Core L#9
> PU L#18 (P#7)
> PU L#19 (P#19)
> L2 L#10 (256KB) + L1d L#10 (32KB) + L1i L#10 (32KB) + Core L#10
> PU L#20 (P#9)
> PU L#21 (P#21)
> L2 L#11 (256KB) + L1d L#11 (32KB) + L1i L#11 (32KB) + Core L#11
> PU L#22 (P#11)
> PU L#23 (P#23)
> Misc(MemoryModule)
> Misc(MemoryModule)
> Misc(MemoryModule)
> Misc(MemoryModule)
> Misc(MemoryModule)
> Misc(MemoryModule)
> Misc(MemoryModule)
> Misc(MemoryModule)
> HostBridge L#0
> PCIBridge
> PCI 14e4:163b
> Net L#0 "em1"
> PCI 14e4:163b
> Net L#1 "em2"
> PCIBridge
> PCI 1000:0079
> Block(Disk) L#2 "sda"
> PCIBridge
> PCIBridge
> PCIBridge
> PCI 8086:10e8
> Net L#3 "p2p1"
> PCI 8086:10e8
> Net L#4 "p2p2"
> PCIBridge
> PCI 8086:10e8
> Net L#5 "p2p3"
> PCI 8086:10e8
> Net L#6 "p2p4"
> PCIBridge
> PCI 8086:10fb
> Net L#7 "p1p1"
> PCI 8086:10fb
> Net L#8 "p1p2"
> PCIBridge
> PCI 102b:0532
> GPU L#9 "card0"
> GPU L#10 "controlD64"
>
>
>
>
>
>
>
> On Mon, Nov 25, 2019 at 4:11 PM Alfredo Cardigliano <cardigliano@ntop.org <mailto:cardigliano@ntop.org>> wrote:
> Hi
> please provide:
> - the pfcount command you are using
> - cat /proc/net/pf_ring/dev/<interface>/info
> - cat /proc/cpuinfo
> - lstopo
>
> Thank you
> Alfredo
>
>> On 24 Nov 2019, at 07:38, Yong Wang <cnwangyong@gmail.com <mailto:cnwangyong@gmail.com>> wrote:
>>
>>
>> Hi there, I am struggling with a weird packet dropping. My environment is pfring zc with intel x520 nic. I started a pfcount to listen to one of 10Gb port of this card. When a burst traffic up to 2Gb came in, ifconfig showed thousands packets were dropped. The reason I called it weird is when the traffic remained in 2Gb, no packet dropped any more.
>>
>> Any comment?
>> _______________________________________________
>> Ntop-misc mailing list
>> Ntop-misc@listgateway.unipi.it <mailto:Ntop-misc@listgateway.unipi.it>
>> http://listgateway.unipi.it/mailman/listinfo/ntop-misc <http://listgateway.unipi.it/mailman/listinfo/ntop-misc>
> _______________________________________________
> Ntop-misc mailing list
> Ntop-misc@listgateway.unipi.it <mailto:Ntop-misc@listgateway.unipi.it>
> http://listgateway.unipi.it/mailman/listinfo/ntop-misc <http://listgateway.unipi.it/mailman/listinfo/ntop-misc>_______________________________________________
> Ntop-misc mailing list
> Ntop-misc@listgateway.unipi.it
> http://listgateway.unipi.it/mailman/listinfo/ntop-misc
Re: help with packet dropping when bursting traffic [ In reply to ]
thanks, I will try this out.

Sent from my iPhone

> On Dec 27, 2019, at 5:29 PM, Alfredo Cardigliano <cardigliano@ntop.org> wrote:
>
> ?Hi
> it seems you are not actually enabling ZC capture, please add the zc: prefix
> to the interface name (e.g. -i zc:p1p1)
>
> Regards
> Alfredo
>
>> On 25 Dec 2019, at 06:46, Wang <cnwangyong@gmail.com> wrote:
>>
>> Hi Alfredo, sorry for the late reply. I have being try to solve it but unfortunately it doesn't work so far. So, here is some updated info for you:
>>
>> what happened:
>> about 2Gbps captured by a 10Gb port, zcount reported no drops, ethtool -S reported no rs_dropped, but ip -s link report more than 300K packets dropped.
>>
>> -OS:
>> centos 7, kernel 3.10
>>
>> -capture port:
>> 82599EB based dual-port card
>>
>> -command line:
>> zcount -i p1p1
>>
>> - cat /proc/net/pf_ring/dev/<interface>/info
>> [root@r510 p1p1]# cat info
>> Name: p1p1
>> Index: 10
>> Address: 48:F8:DB:7E:DA: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
>>
>>
>> [root@r510 pf_ring]# cat 31372-p1p1.120
>> Bound Device(s) : p1p1
>> Active : 1
>> Breed : Standard
>> Appl. Name : pfring-zc-99-p1p1
>> Socket Mode : RX only
>> Capture Direction : RX only
>> Sampling Rate : 1
>> Filtering Sampling Rate: 0
>> IP Defragment : No
>> BPF Filtering : Disabled
>> Sw Filt Hash Rules : 0
>> Sw Filt WC Rules : 0
>> Sw Filt Hash Match : 0
>> Sw Filt Hash Miss : 0
>> Sw Filt Hash Filtered : 0
>> Hw Filt Rules : 0
>> Poll Pkt Watermark : 128
>> Num Poll Calls : 0
>> Poll Watermark Timeout : 0
>> Channel Id Mask : 0xFFFFFFFFFFFFFFFF
>> VLAN Id : 65535
>> Slot Version : 17 [7.5.0]
>> Min Num Slots : 65538
>> Bucket Len : 1518
>> Slot Len : 1568 [bucket+header]
>> Tot Memory : 102772736
>> Tot Packets : 20306173
>> Tot Pkt Lost : 0
>> Tot Insert : 20306173
>> Tot Read : 20306172
>> Insert Offset : 37222704
>> Remove Offset : 37220768
>> Num Free Slots : 65536
>> Reflect: Fwd Ok : 0
>> Reflect: Fwd Errors : 0
>>
>>
>>
>> - cat /proc/cpuinfo
>> 24core cpu, this is the last one, all others looks like this:
>>
>> processor : 23
>> vendor_id : GenuineIntel
>> cpu family : 6
>> model : 44
>> model name : Intel(R) Xeon(R) CPU X5675 @ 3.07GHz
>> stepping : 2
>> microcode : 0x1f
>> cpu MHz : 3066.920
>> cache size : 12288 KB
>> physical id : 0
>> siblings : 12
>> core id : 10
>> cpu cores : 6
>> apicid : 21
>> initial apicid : 21
>> fpu : yes
>> fpu_exception : yes
>> cpuid level : 11
>> wp : yes
>> flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx pdpe1gb rdtscp lm constant_tsc arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc aperfmperf eagerfpu pn i pclmulqdq dtes64 monitor ds_cpl vmx smx est tm2 ssse3 cx16 xtpr pdcm pcid dca sse4_1 sse4_2 popcnt aes lahf_lm ssbd ibrs ibpb st ibp tpr_shadow vnmi flexpriority ept vpid dtherm ida arat spec_ctrl intel_stibp flush_l1d
>> bogomips : 6133.23
>> clflush size : 64
>> cache_alignment : 64
>> address sizes : 40 bits physical, 48 bits virtual
>> power management:
>>
>>
>> - lstopo
>> [root@r510 tmp]# lstopo-no-graphics
>> Machine (64GB total)
>> NUMANode L#0 (P#0 32GB) + Package L#0 + L3 L#0 (12MB)
>> L2 L#0 (256KB) + L1d L#0 (32KB) + L1i L#0 (32KB) + Core L#0
>> PU L#0 (P#0)
>> PU L#1 (P#12)
>> L2 L#1 (256KB) + L1d L#1 (32KB) + L1i L#1 (32KB) + Core L#1
>> PU L#2 (P#2)
>> PU L#3 (P#14)
>> L2 L#2 (256KB) + L1d L#2 (32KB) + L1i L#2 (32KB) + Core L#2
>> PU L#4 (P#4)
>> PU L#5 (P#16)
>> L2 L#3 (256KB) + L1d L#3 (32KB) + L1i L#3 (32KB) + Core L#3
>> PU L#6 (P#6)
>> PU L#7 (P#18)
>> L2 L#4 (256KB) + L1d L#4 (32KB) + L1i L#4 (32KB) + Core L#4
>> PU L#8 (P#8)
>> PU L#9 (P#20)
>> L2 L#5 (256KB) + L1d L#5 (32KB) + L1i L#5 (32KB) + Core L#5
>> PU L#10 (P#10)
>> PU L#11 (P#22)
>> NUMANode L#1 (P#1 32GB) + Package L#1 + L3 L#1 (12MB)
>> L2 L#6 (256KB) + L1d L#6 (32KB) + L1i L#6 (32KB) + Core L#6
>> PU L#12 (P#1)
>> PU L#13 (P#13)
>> L2 L#7 (256KB) + L1d L#7 (32KB) + L1i L#7 (32KB) + Core L#7
>> PU L#14 (P#3)
>> PU L#15 (P#15)
>> L2 L#8 (256KB) + L1d L#8 (32KB) + L1i L#8 (32KB) + Core L#8
>> PU L#16 (P#5)
>> PU L#17 (P#17)
>> L2 L#9 (256KB) + L1d L#9 (32KB) + L1i L#9 (32KB) + Core L#9
>> PU L#18 (P#7)
>> PU L#19 (P#19)
>> L2 L#10 (256KB) + L1d L#10 (32KB) + L1i L#10 (32KB) + Core L#10
>> PU L#20 (P#9)
>> PU L#21 (P#21)
>> L2 L#11 (256KB) + L1d L#11 (32KB) + L1i L#11 (32KB) + Core L#11
>> PU L#22 (P#11)
>> PU L#23 (P#23)
>> Misc(MemoryModule)
>> Misc(MemoryModule)
>> Misc(MemoryModule)
>> Misc(MemoryModule)
>> Misc(MemoryModule)
>> Misc(MemoryModule)
>> Misc(MemoryModule)
>> Misc(MemoryModule)
>> HostBridge L#0
>> PCIBridge
>> PCI 14e4:163b
>> Net L#0 "em1"
>> PCI 14e4:163b
>> Net L#1 "em2"
>> PCIBridge
>> PCI 1000:0079
>> Block(Disk) L#2 "sda"
>> PCIBridge
>> PCIBridge
>> PCIBridge
>> PCI 8086:10e8
>> Net L#3 "p2p1"
>> PCI 8086:10e8
>> Net L#4 "p2p2"
>> PCIBridge
>> PCI 8086:10e8
>> Net L#5 "p2p3"
>> PCI 8086:10e8
>> Net L#6 "p2p4"
>> PCIBridge
>> PCI 8086:10fb
>> Net L#7 "p1p1"
>> PCI 8086:10fb
>> Net L#8 "p1p2"
>> PCIBridge
>> PCI 102b:0532
>> GPU L#9 "card0"
>> GPU L#10 "controlD64"
>>
>>
>>
>>
>>
>>
>>
>> On Mon, Nov 25, 2019 at 4:11 PM Alfredo Cardigliano <cardigliano@ntop.org> wrote:
>>> Hi
>>> please provide:
>>> - the pfcount command you are using
>>> - cat /proc/net/pf_ring/dev/<interface>/info
>>> - cat /proc/cpuinfo
>>> - lstopo
>>>
>>> Thank you
>>> Alfredo
>>>
>>>> On 24 Nov 2019, at 07:38, Yong Wang <cnwangyong@gmail.com> wrote:
>>>>
>>>>
>>>> Hi there, I am struggling with a weird packet dropping. My environment is pfring zc with intel x520 nic. I started a pfcount to listen to one of 10Gb port of this card. When a burst traffic up to 2Gb came in, ifconfig showed thousands packets were dropped. The reason I called it weird is when the traffic remained in 2Gb, no packet dropped any more.
>>>>
>>>> Any comment?
>>>> _______________________________________________
>>>> Ntop-misc mailing list
>>>> Ntop-misc@listgateway.unipi.it
>>>> http://listgateway.unipi.it/mailman/listinfo/ntop-misc
>>>
>>> _______________________________________________
>>> Ntop-misc mailing list
>>> Ntop-misc@listgateway.unipi.it
>>> http://listgateway.unipi.it/mailman/listinfo/ntop-misc
>> _______________________________________________
>> Ntop-misc mailing list
>> Ntop-misc@listgateway.unipi.it
>> http://listgateway.unipi.it/mailman/listinfo/ntop-misc
>
> _______________________________________________
> Ntop-misc mailing list
> Ntop-misc@listgateway.unipi.it
> http://listgateway.unipi.it/mailman/listinfo/ntop-misc
Re: help with packet dropping when bursting traffic [ In reply to ]
Thank you, it worked and now there’s no drop any more.
As to the output of my lstopo, p1p1 is connected to a PCIBridge, so which numa node should I bind zc driver and my app to.

Many thanks,
Wang

Sent from my iPhone

> On Dec 27, 2019, at 5:29 PM, Alfredo Cardigliano <cardigliano@ntop.org> wrote:
>
> ?Hi
> it seems you are not actually enabling ZC capture, please add the zc: prefix
> to the interface name (e.g. -i zc:p1p1)
>
> Regards
> Alfredo
>
>> On 25 Dec 2019, at 06:46, Wang <cnwangyong@gmail.com> wrote:
>>
>> Hi Alfredo, sorry for the late reply. I have being try to solve it but unfortunately it doesn't work so far. So, here is some updated info for you:
>>
>> what happened:
>> about 2Gbps captured by a 10Gb port, zcount reported no drops, ethtool -S reported no rs_dropped, but ip -s link report more than 300K packets dropped.
>>
>> -OS:
>> centos 7, kernel 3.10
>>
>> -capture port:
>> 82599EB based dual-port card
>>
>> -command line:
>> zcount -i p1p1
>>
>> - cat /proc/net/pf_ring/dev/<interface>/info
>> [root@r510 p1p1]# cat info
>> Name: p1p1
>> Index: 10
>> Address: 48:F8:DB:7E:DA: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
>>
>>
>> [root@r510 pf_ring]# cat 31372-p1p1.120
>> Bound Device(s) : p1p1
>> Active : 1
>> Breed : Standard
>> Appl. Name : pfring-zc-99-p1p1
>> Socket Mode : RX only
>> Capture Direction : RX only
>> Sampling Rate : 1
>> Filtering Sampling Rate: 0
>> IP Defragment : No
>> BPF Filtering : Disabled
>> Sw Filt Hash Rules : 0
>> Sw Filt WC Rules : 0
>> Sw Filt Hash Match : 0
>> Sw Filt Hash Miss : 0
>> Sw Filt Hash Filtered : 0
>> Hw Filt Rules : 0
>> Poll Pkt Watermark : 128
>> Num Poll Calls : 0
>> Poll Watermark Timeout : 0
>> Channel Id Mask : 0xFFFFFFFFFFFFFFFF
>> VLAN Id : 65535
>> Slot Version : 17 [7.5.0]
>> Min Num Slots : 65538
>> Bucket Len : 1518
>> Slot Len : 1568 [bucket+header]
>> Tot Memory : 102772736
>> Tot Packets : 20306173
>> Tot Pkt Lost : 0
>> Tot Insert : 20306173
>> Tot Read : 20306172
>> Insert Offset : 37222704
>> Remove Offset : 37220768
>> Num Free Slots : 65536
>> Reflect: Fwd Ok : 0
>> Reflect: Fwd Errors : 0
>>
>>
>>
>> - cat /proc/cpuinfo
>> 24core cpu, this is the last one, all others looks like this:
>>
>> processor : 23
>> vendor_id : GenuineIntel
>> cpu family : 6
>> model : 44
>> model name : Intel(R) Xeon(R) CPU X5675 @ 3.07GHz
>> stepping : 2
>> microcode : 0x1f
>> cpu MHz : 3066.920
>> cache size : 12288 KB
>> physical id : 0
>> siblings : 12
>> core id : 10
>> cpu cores : 6
>> apicid : 21
>> initial apicid : 21
>> fpu : yes
>> fpu_exception : yes
>> cpuid level : 11
>> wp : yes
>> flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx pdpe1gb rdtscp lm constant_tsc arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc aperfmperf eagerfpu pn i pclmulqdq dtes64 monitor ds_cpl vmx smx est tm2 ssse3 cx16 xtpr pdcm pcid dca sse4_1 sse4_2 popcnt aes lahf_lm ssbd ibrs ibpb st ibp tpr_shadow vnmi flexpriority ept vpid dtherm ida arat spec_ctrl intel_stibp flush_l1d
>> bogomips : 6133.23
>> clflush size : 64
>> cache_alignment : 64
>> address sizes : 40 bits physical, 48 bits virtual
>> power management:
>>
>>
>> - lstopo
>> [root@r510 tmp]# lstopo-no-graphics
>> Machine (64GB total)
>> NUMANode L#0 (P#0 32GB) + Package L#0 + L3 L#0 (12MB)
>> L2 L#0 (256KB) + L1d L#0 (32KB) + L1i L#0 (32KB) + Core L#0
>> PU L#0 (P#0)
>> PU L#1 (P#12)
>> L2 L#1 (256KB) + L1d L#1 (32KB) + L1i L#1 (32KB) + Core L#1
>> PU L#2 (P#2)
>> PU L#3 (P#14)
>> L2 L#2 (256KB) + L1d L#2 (32KB) + L1i L#2 (32KB) + Core L#2
>> PU L#4 (P#4)
>> PU L#5 (P#16)
>> L2 L#3 (256KB) + L1d L#3 (32KB) + L1i L#3 (32KB) + Core L#3
>> PU L#6 (P#6)
>> PU L#7 (P#18)
>> L2 L#4 (256KB) + L1d L#4 (32KB) + L1i L#4 (32KB) + Core L#4
>> PU L#8 (P#8)
>> PU L#9 (P#20)
>> L2 L#5 (256KB) + L1d L#5 (32KB) + L1i L#5 (32KB) + Core L#5
>> PU L#10 (P#10)
>> PU L#11 (P#22)
>> NUMANode L#1 (P#1 32GB) + Package L#1 + L3 L#1 (12MB)
>> L2 L#6 (256KB) + L1d L#6 (32KB) + L1i L#6 (32KB) + Core L#6
>> PU L#12 (P#1)
>> PU L#13 (P#13)
>> L2 L#7 (256KB) + L1d L#7 (32KB) + L1i L#7 (32KB) + Core L#7
>> PU L#14 (P#3)
>> PU L#15 (P#15)
>> L2 L#8 (256KB) + L1d L#8 (32KB) + L1i L#8 (32KB) + Core L#8
>> PU L#16 (P#5)
>> PU L#17 (P#17)
>> L2 L#9 (256KB) + L1d L#9 (32KB) + L1i L#9 (32KB) + Core L#9
>> PU L#18 (P#7)
>> PU L#19 (P#19)
>> L2 L#10 (256KB) + L1d L#10 (32KB) + L1i L#10 (32KB) + Core L#10
>> PU L#20 (P#9)
>> PU L#21 (P#21)
>> L2 L#11 (256KB) + L1d L#11 (32KB) + L1i L#11 (32KB) + Core L#11
>> PU L#22 (P#11)
>> PU L#23 (P#23)
>> Misc(MemoryModule)
>> Misc(MemoryModule)
>> Misc(MemoryModule)
>> Misc(MemoryModule)
>> Misc(MemoryModule)
>> Misc(MemoryModule)
>> Misc(MemoryModule)
>> Misc(MemoryModule)
>> HostBridge L#0
>> PCIBridge
>> PCI 14e4:163b
>> Net L#0 "em1"
>> PCI 14e4:163b
>> Net L#1 "em2"
>> PCIBridge
>> PCI 1000:0079
>> Block(Disk) L#2 "sda"
>> PCIBridge
>> PCIBridge
>> PCIBridge
>> PCI 8086:10e8
>> Net L#3 "p2p1"
>> PCI 8086:10e8
>> Net L#4 "p2p2"
>> PCIBridge
>> PCI 8086:10e8
>> Net L#5 "p2p3"
>> PCI 8086:10e8
>> Net L#6 "p2p4"
>> PCIBridge
>> PCI 8086:10fb
>> Net L#7 "p1p1"
>> PCI 8086:10fb
>> Net L#8 "p1p2"
>> PCIBridge
>> PCI 102b:0532
>> GPU L#9 "card0"
>> GPU L#10 "controlD64"
>>
>>
>>
>>
>>
>>
>>
>> On Mon, Nov 25, 2019 at 4:11 PM Alfredo Cardigliano <cardigliano@ntop.org> wrote:
>>> Hi
>>> please provide:
>>> - the pfcount command you are using
>>> - cat /proc/net/pf_ring/dev/<interface>/info
>>> - cat /proc/cpuinfo
>>> - lstopo
>>>
>>> Thank you
>>> Alfredo
>>>
>>>> On 24 Nov 2019, at 07:38, Yong Wang <cnwangyong@gmail.com> wrote:
>>>>
>>>>
>>>> Hi there, I am struggling with a weird packet dropping. My environment is pfring zc with intel x520 nic. I started a pfcount to listen to one of 10Gb port of this card. When a burst traffic up to 2Gb came in, ifconfig showed thousands packets were dropped. The reason I called it weird is when the traffic remained in 2Gb, no packet dropped any more.
>>>>
>>>> Any comment?
>>>> _______________________________________________
>>>> Ntop-misc mailing list
>>>> Ntop-misc@listgateway.unipi.it
>>>> http://listgateway.unipi.it/mailman/listinfo/ntop-misc
>>>
>>> _______________________________________________
>>> Ntop-misc mailing list
>>> Ntop-misc@listgateway.unipi.it
>>> http://listgateway.unipi.it/mailman/listinfo/ntop-misc
>> _______________________________________________
>> Ntop-misc mailing list
>> Ntop-misc@listgateway.unipi.it
>> http://listgateway.unipi.it/mailman/listinfo/ntop-misc
>
> _______________________________________________
> Ntop-misc mailing list
> Ntop-misc@listgateway.unipi.it
> http://listgateway.unipi.it/mailman/listinfo/ntop-misc
Re: help with packet dropping when bursting traffic [ In reply to ]
Hi Wang
in this case you can use any of the 2 numa nodes.

Alfredo

> On 29 Dec 2019, at 04:20, Yong Wang <cnwangyong@gmail.com> wrote:
>
> Thank you, it worked and now there’s no drop any more.
> As to the output of my lstopo, p1p1 is connected to a PCIBridge, so which numa node should I bind zc driver and my app to.
>
> Many thanks,
> Wang
>
> Sent from my iPhone
>
>> On Dec 27, 2019, at 5:29 PM, Alfredo Cardigliano <cardigliano@ntop.org <mailto:cardigliano@ntop.org>> wrote:
>>
>> ?Hi
>> it seems you are not actually enabling ZC capture, please add the zc: prefix
>> to the interface name (e.g. -i zc:p1p1)
>>
>> Regards
>> Alfredo
>>
>>> On 25 Dec 2019, at 06:46, Wang <cnwangyong@gmail.com <mailto:cnwangyong@gmail.com>> wrote:
>>>
>>> Hi Alfredo, sorry for the late reply. I have being try to solve it but unfortunately it doesn't work so far. So, here is some updated info for you:
>>>
>>> what happened:
>>> about 2Gbps captured by a 10Gb port, zcount reported no drops, ethtool -S reported no rs_dropped, but ip -s link report more than 300K packets dropped.
>>>
>>> -OS:
>>> centos 7, kernel 3.10
>>>
>>> -capture port:
>>> 82599EB based dual-port card
>>>
>>> -command line:
>>> zcount -i p1p1
>>>
>>> - cat /proc/net/pf_ring/dev/<interface>/info
>>> [root@r510 p1p1]# cat info
>>> Name: p1p1
>>> Index: 10
>>> Address: 48:F8:DB:7E:DA: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
>>>
>>>
>>> [root@r510 pf_ring]# cat 31372-p1p1.120
>>> Bound Device(s) : p1p1
>>> Active : 1
>>> Breed : Standard
>>> Appl. Name : pfring-zc-99-p1p1
>>> Socket Mode : RX only
>>> Capture Direction : RX only
>>> Sampling Rate : 1
>>> Filtering Sampling Rate: 0
>>> IP Defragment : No
>>> BPF Filtering : Disabled
>>> Sw Filt Hash Rules : 0
>>> Sw Filt WC Rules : 0
>>> Sw Filt Hash Match : 0
>>> Sw Filt Hash Miss : 0
>>> Sw Filt Hash Filtered : 0
>>> Hw Filt Rules : 0
>>> Poll Pkt Watermark : 128
>>> Num Poll Calls : 0
>>> Poll Watermark Timeout : 0
>>> Channel Id Mask : 0xFFFFFFFFFFFFFFFF
>>> VLAN Id : 65535
>>> Slot Version : 17 [7.5.0]
>>> Min Num Slots : 65538
>>> Bucket Len : 1518
>>> Slot Len : 1568 [bucket+header]
>>> Tot Memory : 102772736
>>> Tot Packets : 20306173
>>> Tot Pkt Lost : 0
>>> Tot Insert : 20306173
>>> Tot Read : 20306172
>>> Insert Offset : 37222704
>>> Remove Offset : 37220768
>>> Num Free Slots : 65536
>>> Reflect: Fwd Ok : 0
>>> Reflect: Fwd Errors : 0
>>>
>>>
>>>
>>> - cat /proc/cpuinfo
>>> 24core cpu, this is the last one, all others looks like this:
>>>
>>> processor : 23
>>> vendor_id : GenuineIntel
>>> cpu family : 6
>>> model : 44
>>> model name : Intel(R) Xeon(R) CPU X5675 @ 3.07GHz
>>> stepping : 2
>>> microcode : 0x1f
>>> cpu MHz : 3066.920
>>> cache size : 12288 KB
>>> physical id : 0
>>> siblings : 12
>>> core id : 10
>>> cpu cores : 6
>>> apicid : 21
>>> initial apicid : 21
>>> fpu : yes
>>> fpu_exception : yes
>>> cpuid level : 11
>>> wp : yes
>>> flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx pdpe1gb rdtscp lm constant_tsc arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc aperfmperf eagerfpu pn i pclmulqdq dtes64 monitor ds_cpl vmx smx est tm2 ssse3 cx16 xtpr pdcm pcid dca sse4_1 sse4_2 popcnt aes lahf_lm ssbd ibrs ibpb st ibp tpr_shadow vnmi flexpriority ept vpid dtherm ida arat spec_ctrl intel_stibp flush_l1d
>>> bogomips : 6133.23
>>> clflush size : 64
>>> cache_alignment : 64
>>> address sizes : 40 bits physical, 48 bits virtual
>>> power management:
>>>
>>>
>>> - lstopo
>>> [root@r510 tmp]# lstopo-no-graphics
>>> Machine (64GB total)
>>> NUMANode L#0 (P#0 32GB) + Package L#0 + L3 L#0 (12MB)
>>> L2 L#0 (256KB) + L1d L#0 (32KB) + L1i L#0 (32KB) + Core L#0
>>> PU L#0 (P#0)
>>> PU L#1 (P#12)
>>> L2 L#1 (256KB) + L1d L#1 (32KB) + L1i L#1 (32KB) + Core L#1
>>> PU L#2 (P#2)
>>> PU L#3 (P#14)
>>> L2 L#2 (256KB) + L1d L#2 (32KB) + L1i L#2 (32KB) + Core L#2
>>> PU L#4 (P#4)
>>> PU L#5 (P#16)
>>> L2 L#3 (256KB) + L1d L#3 (32KB) + L1i L#3 (32KB) + Core L#3
>>> PU L#6 (P#6)
>>> PU L#7 (P#18)
>>> L2 L#4 (256KB) + L1d L#4 (32KB) + L1i L#4 (32KB) + Core L#4
>>> PU L#8 (P#8)
>>> PU L#9 (P#20)
>>> L2 L#5 (256KB) + L1d L#5 (32KB) + L1i L#5 (32KB) + Core L#5
>>> PU L#10 (P#10)
>>> PU L#11 (P#22)
>>> NUMANode L#1 (P#1 32GB) + Package L#1 + L3 L#1 (12MB)
>>> L2 L#6 (256KB) + L1d L#6 (32KB) + L1i L#6 (32KB) + Core L#6
>>> PU L#12 (P#1)
>>> PU L#13 (P#13)
>>> L2 L#7 (256KB) + L1d L#7 (32KB) + L1i L#7 (32KB) + Core L#7
>>> PU L#14 (P#3)
>>> PU L#15 (P#15)
>>> L2 L#8 (256KB) + L1d L#8 (32KB) + L1i L#8 (32KB) + Core L#8
>>> PU L#16 (P#5)
>>> PU L#17 (P#17)
>>> L2 L#9 (256KB) + L1d L#9 (32KB) + L1i L#9 (32KB) + Core L#9
>>> PU L#18 (P#7)
>>> PU L#19 (P#19)
>>> L2 L#10 (256KB) + L1d L#10 (32KB) + L1i L#10 (32KB) + Core L#10
>>> PU L#20 (P#9)
>>> PU L#21 (P#21)
>>> L2 L#11 (256KB) + L1d L#11 (32KB) + L1i L#11 (32KB) + Core L#11
>>> PU L#22 (P#11)
>>> PU L#23 (P#23)
>>> Misc(MemoryModule)
>>> Misc(MemoryModule)
>>> Misc(MemoryModule)
>>> Misc(MemoryModule)
>>> Misc(MemoryModule)
>>> Misc(MemoryModule)
>>> Misc(MemoryModule)
>>> Misc(MemoryModule)
>>> HostBridge L#0
>>> PCIBridge
>>> PCI 14e4:163b
>>> Net L#0 "em1"
>>> PCI 14e4:163b
>>> Net L#1 "em2"
>>> PCIBridge
>>> PCI 1000:0079
>>> Block(Disk) L#2 "sda"
>>> PCIBridge
>>> PCIBridge
>>> PCIBridge
>>> PCI 8086:10e8
>>> Net L#3 "p2p1"
>>> PCI 8086:10e8
>>> Net L#4 "p2p2"
>>> PCIBridge
>>> PCI 8086:10e8
>>> Net L#5 "p2p3"
>>> PCI 8086:10e8
>>> Net L#6 "p2p4"
>>> PCIBridge
>>> PCI 8086:10fb
>>> Net L#7 "p1p1"
>>> PCI 8086:10fb
>>> Net L#8 "p1p2"
>>> PCIBridge
>>> PCI 102b:0532
>>> GPU L#9 "card0"
>>> GPU L#10 "controlD64"
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>> On Mon, Nov 25, 2019 at 4:11 PM Alfredo Cardigliano <cardigliano@ntop.org <mailto:cardigliano@ntop.org>> wrote:
>>> Hi
>>> please provide:
>>> - the pfcount command you are using
>>> - cat /proc/net/pf_ring/dev/<interface>/info
>>> - cat /proc/cpuinfo
>>> - lstopo
>>>
>>> Thank you
>>> Alfredo
>>>
>>>> On 24 Nov 2019, at 07:38, Yong Wang <cnwangyong@gmail.com <mailto:cnwangyong@gmail.com>> wrote:
>>>>
>>>>
>>>> Hi there, I am struggling with a weird packet dropping. My environment is pfring zc with intel x520 nic. I started a pfcount to listen to one of 10Gb port of this card. When a burst traffic up to 2Gb came in, ifconfig showed thousands packets were dropped. The reason I called it weird is when the traffic remained in 2Gb, no packet dropped any more.
>>>>
>>>> Any comment?
>>>> _______________________________________________
>>>> Ntop-misc mailing list
>>>> Ntop-misc@listgateway.unipi.it <mailto:Ntop-misc@listgateway.unipi.it>
>>>> http://listgateway.unipi.it/mailman/listinfo/ntop-misc <http://listgateway.unipi.it/mailman/listinfo/ntop-misc>
>>> _______________________________________________
>>> Ntop-misc mailing list
>>> Ntop-misc@listgateway.unipi.it <mailto:Ntop-misc@listgateway.unipi.it>
>>> http://listgateway.unipi.it/mailman/listinfo/ntop-misc <http://listgateway.unipi.it/mailman/listinfo/ntop-misc>_______________________________________________
>>> Ntop-misc mailing list
>>> Ntop-misc@listgateway.unipi.it <mailto:Ntop-misc@listgateway.unipi.it>
>>> http://listgateway.unipi.it/mailman/listinfo/ntop-misc <http://listgateway.unipi.it/mailman/listinfo/ntop-misc>
>> _______________________________________________
>> Ntop-misc mailing list
>> Ntop-misc@listgateway.unipi.it <mailto:Ntop-misc@listgateway.unipi.it>
>> http://listgateway.unipi.it/mailman/listinfo/ntop-misc <http://listgateway.unipi.it/mailman/listinfo/ntop-misc>_______________________________________________
> Ntop-misc mailing list
> Ntop-misc@listgateway.unipi.it <mailto:Ntop-misc@listgateway.unipi.it>
> http://listgateway.unipi.it/mailman/listinfo/ntop-misc <http://listgateway.unipi.it/mailman/listinfo/ntop-misc>