[tcpdump-workers] RadioTap Parsing as seperate library

2024-04-15 Thread Ravi chandra
Hi All experts,

I am planning to create an ieee 802.11 packet RadioTap parsing
code/library [offlines processing of pcap-ng files. Decoding each and
every field and write it to a .csv file].

Meanwhile, before asking [did my homework] of going through source
code and found the following.

[1] Compared to the Wireshark library, RadioTap library files are NOT
updated in the radiotap-library. so it looks like I have to use/ the
wireshark code
[2] I see RadioTap headers/files/parsing functions have additional
arguments [which are specific to wireshark]. In other words, there is
NO direct way to call RadioTap headers easily to integrate with
libpcap_open_offline and pcap_next.
[3] Is there any easy way to isolate RadioTap files as a separate
library or set of files with NO dependencies on wireshark files [via
build].
[4] do I have to manually go through each function & file and build it
as separate library?

plz let me know the best and easiest approach.

Thanks
___
tcpdump-workers mailing list -- tcpdump-workers@lists.tcpdump.org
To unsubscribe send an email to tcpdump-workers-le...@lists.tcpdump.org
%(web_page_url)slistinfo%(cgiext)s/%(_internal_name)s


[tcpdump-workers] Re: RadioTap Parsing as seperate library

2024-04-19 Thread Ravi chandra
Hi Guy,

[1] Thanks for the quick response. I went through the examples of
t-shark and some codebase. Looks like it does help in my case.
[2] regarding others, RadioTap library is updated in wireshark and
have more additions in terms of header parsing compared to RadioTap
library standalone
[3] "Note that tcpdump has its own code to parse radiotap headers, and
that code doesn't use the Radiotap library.". Thanks for confirmation.

Thanks

On Mon, Apr 15, 2024 at 7:23 PM Guy Harris  wrote:
>
> On Apr 15, 2024, at 3:47 PM, Ravi chandra  wrote:
>
> > I am planning to create an ieee 802.11 packet RadioTap parsing
> > code/library [offlines processing of pcap-ng files. Decoding each and
> > every field and write it to a .csv file].
>
> If that's all you're doing, is there some reason why you don't just use 
> TShark and do
>
> tshark -T fields -E separator=, -E quote=d -e {radiotap field} -e 
> {another radiotap field} ...
>
> > Meanwhile, before asking [did my homework] of going through source
> > code and found the following.
> >
> > [1] Compared to the Wireshark library, RadioTap library files
>
> By "Radiotap library files" do you mean this library:
>
> https://github.com/radiotap/radiotap-library
>
> > are NOT updated in the radiotap-library.
>
> What do you mean by "NOT updated"?  Do you mean that the recent commits 
> haven't significantly changed the library?  If so, maybe there's not much 
> that needs changing.
>
> > [2] I see RadioTap headers/files/parsing functions have additional
> > arguments [which are specific to wireshark]. In other words, there is
> > NO direct way to call RadioTap headers easily to integrate with
> > libpcap_open_offline and pcap_next.
>
> Note that tcpdump has its own code to parse radiotap headers, and that code 
> doesn't use the Radiotap library.



-- 
god is always great and his miracles are enormous
___
tcpdump-workers mailing list -- tcpdump-workers@lists.tcpdump.org
To unsubscribe send an email to tcpdump-workers-le...@lists.tcpdump.org
%(web_page_url)slistinfo%(cgiext)s/%(_internal_name)s

[tcpdump-workers] like to support tcp dump

2012-08-19 Thread sadineni ravi chandra
hi guys,
 I am new to the community. I want to support tcp dump by fixing a bug or
developing a feature.
i will be very happy if you guys can guide me ..
thanks and regards,
ravi
___
tcpdump-workers mailing list
tcpdump-workers@lists.tcpdump.org
https://lists.sandelman.ca/mailman/listinfo/tcpdump-workers