Mailing List Archive

Using the "any" interface and getting the real if_index
When using pfring_open() with the device name "any", will the extended
pf_ring headers have the correct value set for the if_index field? E.g. if
a packet comes in on "eth0" which has index 2, will this packets extended
header have if_index = 2?

I have read some of the libs and it looks like the device name "any" ends
up in the socketaddr field sa_addr, but after this I don't know where to
look to see what PF_RING does with it.

Lars
Re: Using the "any" interface and getting the real if_index [ In reply to ]
Hi Lars
the if_index field should contain the actual ifindex even when capturing from any, please let us know if this is not the case with your configuration.

Alfredo

> On 23 Mar 2016, at 14:06, Lars Kulseng <larskulseng@gmail.com> wrote:
>
> When using pfring_open() with the device name "any", will the extended pf_ring headers have the correct value set for the if_index field? E.g. if a packet comes in on "eth0" which has index 2, will this packets extended header have if_index = 2?
>
> I have read some of the libs and it looks like the device name "any" ends up in the socketaddr field sa_addr, but after this I don't know where to look to see what PF_RING does with it.
>
> Lars
> _______________________________________________
> Ntop-misc mailing list
> Ntop-misc@listgateway.unipi.it
> http://listgateway.unipi.it/mailman/listinfo/ntop-misc