libwireshark for continuous capture?

[Javi Gallart]

Hello all

I started this thread some months ago :
http://www.wireshark.org/lists/wireshark-users/201310/msg00001.html.
According to it, usage of Lua scripts is not suitable for continuous
packet capture, dumpcap is recommended for that. Does the same hold for
a C application that captures network data and used libwireshark (as
nextexpect does) for packet dissection?

Thanks in advance

Regards
Javi
___________________________________________________________________________
Sent via: Wireshark-users mailing list <wireshark-users-IZ8446WsY0/***@public.gmane.org>
Archives: http://www.wireshark.org/lists/wireshark-users
Unsubscribe: https://wireshark.org/mailman/options/wireshark-users
mailto:wireshark-users-request-IZ8446WsY0/***@public.gmane.org?subject=unsubscribe

[Guy Harris]

I started this thread some months ago : http://www.wireshark.org/lists/wireshark-users/201310/msg00001.html. According to it, usage of Lua scripts is not suitable for continuous packet capture, dumpcap is recommended for that. Does the same hold for a C application that captures network data and used libwireshark (as nextexpect does) for packet dissection?

Yes - the Lua support isn't the only part of the Wireshark dissection engine that allocates persistent data structures.

(Note that even *tcpdump*, if you're capturing-and-printing rather than capturing-and-writing-to-a-file, will, by default, allocate persistent data structures to, for example, print relative sequence numbers for TCP.)
___________________________________________________________________________
Sent via: Wireshark-users mailing list <wireshark-users-IZ8446WsY0/***@public.gmane.org>
Archives: http://www.wireshark.org/lists/wireshark-users
Unsubscribe: https://wireshark.org/mailman/options/wireshark-users
mailto:wireshark-users-request-IZ8446WsY0/***@public.gmane.org?subject=unsubscribe