Mailing List Archive

Small correction: Jul-15, 2016. Sorry.

On Thu, Aug 17, 2017 at 5:04 PM, Amir Kaduri <akaduri75@gmail.com> wrote:

> I have an application written in the past, that heavily consists on bundle
> API in general, and on pfcount_bundle example application specifically.
> These APIs were deprecated on Jul-15, 2017 and don't exist anymore in
> pf_ring 6.6.0.
> What is the easiest way to adjust the existing code in order to be able to
> compile and run based on pf_ring 6.6.0?
>
> Thanks
>

Since its about 6 functions, a possible solution could be just copying them
to the application as static functions. Not a perfect solution, but
possible. If there is a better one (that is simple), I'll be glad to hear.
Anyway, another thing in the same context:
The (deprecated) pfcount_bundle.c example application, had a check "if
(h->extended_hdr.parsed_header_len > 0)". "parsed_header_len" has been also
removed from struct pfring_extended_pkthdr{} since pf_ring 6.6.0
(on Oct 19, 2016). I assume it was calculated during packet parsing. Could
you please suggest a simple alternative to this check, based on pf_ring
6.6.0?
Thanks

On Thu, Aug 17, 2017 at 5:11 PM, Amir Kaduri <akaduri75@gmail.com> wrote:

> Small correction: Jul-15, 2016. Sorry.
>
> On Thu, Aug 17, 2017 at 5:04 PM, Amir Kaduri <akaduri75@gmail.com> wrote:
>
>> I have an application written in the past, that heavily consists on
>> bundle API in general, and on pfcount_bundle example application
>> specifically. These APIs were deprecated on Jul-15, 2017 and don't exist
>> anymore in pf_ring 6.6.0.
>> What is the easiest way to adjust the existing code in order to be able
>> to compile and run based on pf_ring 6.6.0?
>>
>> Thanks
>>
>
>

Hi Amir
copying those function is definitely the simplest solution and it should work fine for you,
as of extended_hdr.parsed_header_len please just remove the if branch and delete any
occurrence as that was the length of metadata when using kernel plugins (deprecated).

Regards
Alfredo

> On 21 Aug 2017, at 12:31, Amir Kaduri <akaduri75@gmail.com> wrote:
>
> Since its about 6 functions, a possible solution could be just copying them to the application as static functions. Not a perfect solution, but possible. If there is a better one (that is simple), I'll be glad to hear.
> Anyway, another thing in the same context:
> The (deprecated) pfcount_bundle.c example application, had a check "if (h->extended_hdr.parsed_header_len > 0)". "parsed_header_len" has been also removed from struct pfring_extended_pkthdr{} since pf_ring 6.6.0
> (on Oct 19, 2016). I assume it was calculated during packet parsing. Could you please suggest a simple alternative to this check, based on pf_ring 6.6.0?
> Thanks
>
> On Thu, Aug 17, 2017 at 5:11 PM, Amir Kaduri <akaduri75@gmail.com <mailto:akaduri75@gmail.com>> wrote:
> Small correction: Jul-15, 2016. Sorry.
>
> On Thu, Aug 17, 2017 at 5:04 PM, Amir Kaduri <akaduri75@gmail.com <mailto:akaduri75@gmail.com>> wrote:
> I have an application written in the past, that heavily consists on bundle API in general, and on pfcount_bundle example application specifically. These APIs were deprecated on Jul-15, 2017 and don't exist anymore in pf_ring 6.6.0.
> What is the easiest way to adjust the existing code in order to be able to compile and run based on pf_ring 6.6.0?
>
> Thanks
>
>
> _______________________________________________
> Ntop-misc mailing list
> Ntop-misc@listgateway.unipi.it
> http://listgateway.unipi.it/mailman/listinfo/ntop-misc

Thanks

On Mon, Aug 21, 2017 at 2:00 PM, Alfredo Cardigliano <cardigliano@ntop.org>
wrote:

> Hi Amir
> copying those function is definitely the simplest solution and it should
> work fine for you,
> as of extended_hdr.parsed_header_len please just remove the if branch and
> delete any
> occurrence as that was the length of metadata when using kernel plugins
> (deprecated).
>
> Regards
> Alfredo
>
> On 21 Aug 2017, at 12:31, Amir Kaduri <akaduri75@gmail.com> wrote:
>
> Since its about 6 functions, a possible solution could be just copying
> them to the application as static functions. Not a perfect solution, but
> possible. If there is a better one (that is simple), I'll be glad to hear.
> Anyway, another thing in the same context:
> The (deprecated) pfcount_bundle.c example application, had a check "if
> (h->extended_hdr.parsed_header_len > 0)". "parsed_header_len" has been
> also removed from struct pfring_extended_pkthdr{} since pf_ring 6.6.0
> (on Oct 19, 2016). I assume it was calculated during packet parsing. Could
> you please suggest a simple alternative to this check, based on pf_ring
> 6.6.0?
> Thanks
>
> On Thu, Aug 17, 2017 at 5:11 PM, Amir Kaduri <akaduri75@gmail.com> wrote:
>
>> Small correction: Jul-15, 2016. Sorry.
>>
>> On Thu, Aug 17, 2017 at 5:04 PM, Amir Kaduri <akaduri75@gmail.com> wrote:
>>
>>> I have an application written in the past, that heavily consists on
>>> bundle API in general, and on pfcount_bundle example application
>>> specifically. These APIs were deprecated on Jul-15, 2017 and don't exist
>>> anymore in pf_ring 6.6.0.
>>> What is the easiest way to adjust the existing code in order to be able
>>> to compile and run based on pf_ring 6.6.0?
>>>
>>> Thanks
>>>
>>
>>
> _______________________________________________
> 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
>