Hi Andrew
great, thank you for the update.

Regards
Alfredo

> On 21 Feb 2019, at 10:10, Andrew Howard <a...@andrew-howard.me.uk> wrote:
> 
> 
> Hi Alfredo,
> 
> Forget this - I've realisrf what the problem is. The distribution function 
> signature has changed from an int32 return to an int64 return. All is now 
> well.
> 
> Thanks & regards,
> A.
> 
> --
> Andrew Howard
> a...@andrew-howard.me.uk
> 
> ----- Reply message -----
> From: "Andrew Howard" <a...@andrew-howard.me.uk>
> To: <ntop@listgateway.unipi.it>
> Subject: SIGSEGV in __pfring_zc_balancer_worker_thread_bursts
> Date: Wed, Feb 20, 2019 15:52
> 
> 
> Hi Alfredo,
> 
> Should the pcap file be emailed to your ntop.org address?
> 
> I'm unclear on what configuration you require from zbalancer_ipc. Could you 
> elaborate?
> 
> Thanks and regards,
> A.
> 
> --
> Andrew Howard
> a...@andrew-howard.me.uk
> 
> ----- Reply message -----
> From: "Andrew Howard" <a...@andrew-howard.me.uk>
> To: <ntop@listgateway.unipi.it>
> Subject: SIGSEGV in __pfring_zc_balancer_worker_thread_bursts
> Date: Tue, Feb 19, 2019 10:58
> 
> 
> Apologies for the poor formatting - was written on a phone.
> A.
> 
> --
> Andrew Howard
> a...@andrew-howard.me.uk
> 
> ----- Reply message -----
> From: "Andrew Howard" <a...@andrew-howard.me.uk>
> To: <ntop@listgateway.unipi.it>
> Subject: SIGSEGV in __pfring_zc_balancer_worker_thread_bursts
> Date: Tue, Feb 19, 2019 10:56
> 
> 
> Hi,
>  
> We are currently using the following hardware and software combinations:-
>  
> 1.     PF_RING 7.4.0 on Centos7 (Linux 3.10.0), i40e driver on Intel X710
> 
> 2.     PF_RING 7.4.0 on RHEL 6.10 (Linux 2.6.32), i40e driver on Intel X710
> 
> 3.     Our own snapshot of PF_RING 7.0.0 branch taken 14-Feb-2018 on RHEL 
> 6.10, i40e on X710
> 
> 4.     PF_RING v6.4.1 on RHEL 6.10, ixgbe driver on Intel 82599
>  
>  
> We are successfully receiving traffic via the ZC API (i.e. calling 
> pfring_zc_open_device() with a device name of the format “zc:eth0”) on 
> platforms 1, 3 and 4.
>  
> We can successfully write traffic via the ZC API on platform 1 and 4, but an 
> attempt to do this on platform 3 produces “Socket type not supported”.
>  
> Prior to trying writes on platform 2, we attempted reads, which produces 
> signal 11 in __pfring_zc_balancer_worker_thread_bursts().
>  
> Thoughts?
> 
> Regards,
> A.
> --
> Andrew Howard
> a...@andrew-howard.me.uk
> _______________________________________________
> Ntop mailing list
> Ntop@listgateway.unipi.it
> http://listgateway.unipi.it/mailman/listinfo/ntop

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

Reply via email to