[Wireshark-dev] Cannot get external capture (extcap) interface to work with my new plugin.

2018-12-30 Thread hdv
Hello, I'm developing a new extcap interface as described in chapter 8.2.1 of the developers guide. The goal is to implement a plugin so I can directly attach it to a CAN bus sniffing device called "AnaGate CAN" (see http://www.anagate.de/) Until now all went well, I can see my new interface in

Re: [Wireshark-dev] Cannot get external capture (extcap) interface to work with my new plugin.

2019-01-02 Thread hdv
every packet. Otherwise, without the code nothing much can be said. kind regards Roland Am So., 30. Dez. 2018 um 17:39 Uhr schrieb hdv mailto:henri.de.v...@gmail.com>>: Hello, I'm developing a new extcap interface as described in chapter 8.2.1 of the developers guide. The go

Re: [Wireshark-dev] Cannot get external capture (extcap) interface to work with my new plugin.

2019-01-03 Thread hdv
(I still have some questions and remarks etc. about testing and documentation for example) Note: I have seen all documentation on the development process. I did not find anything about the mailing list about any membership. On Wed, Jan 2, 2019, 17:40 hdv <mailto:henri.de.v...@gmail.com&g

Re: [Wireshark-dev] Cannot get external capture (extcap) interface to work with my new plugin.

2019-01-04 Thread hdv
On 4-1-2019 00:10, Dario Lombardo wrote: On Thu, Jan 3, 2019 at 5:36 PM hdv <mailto:henri.de.v...@gmail.com>> wrote: On 2-1-2019 18:30, Dario Lombardo wrote: You cannot trace your code using prints because they're handled by the caller (dumpcap). Have a loo

Re: [Wireshark-dev] Cannot get external capture (extcap) interface to work with my new plugin.

2019-01-04 Thread hdv
On 4-1-2019 10:39, hdv wrote: On 4-1-2019 00:10, Dario Lombardo wrote: On Thu, Jan 3, 2019 at 5:36 PM hdv <mailto:henri.de.v...@gmail.com>> wrote: On 2-1-2019 18:30, Dario Lombardo wrote: You cannot trace your code using prints because they're handled by the c

[Wireshark-dev] Function getaddrinfo() vanished in one of the later commits.

2019-01-04 Thread hdv
Hi, In the extcap plugin I'm developing I used the getaddrinfo() call to resolve hostnames. This should be favorable over gethostname() which is actually deprecated AFAIK. The previous commit I was developing on was around june 14th, 2018 (27a1906c582b..) where it still worked, now after reb

Re: [Wireshark-dev] Function getaddrinfo() vanished in one of the later commits.

2019-01-04 Thread hdv
On 4-1-2019 12:59, hdv wrote: Hi, In the extcap plugin I'm developing I used the getaddrinfo() call to resolve hostnames. This should be favorable over gethostname() which is actually deprecated AFAIK. Ofcourse I mean: gethostbyname(). The previous commit I was developing on was a

Re: [Wireshark-dev] Cannot get external capture (extcap) interface to work with my new plugin.

2019-01-04 Thread hdv
't have it in my code tree. Any idea if it is related to this issue? Henri On 4-1-2019 00:10, Dario Lombardo wrote: On Thu, Jan 3, 2019 at 5:36 PM hdv mailto:henri.de.v...@gmail.com>> wrote: On 2-1-2019 18:30, Dario Lombardo wrote: You cannot trace your code using prints

Re: [Wireshark-dev] Function getaddrinfo() vanished in one of the later commits.

2019-01-04 Thread hdv
On 4-1-2019 21:53, Guy Harris wrote: On Jan 4, 2019, at 3:59 AM, hdv wrote: In the extcap plugin I'm developing I used the getaddrinfo() call to resolve hostnames. This should be favorable over gethostname() which is actually deprecated AFAIK. The previous commit I was developing o

Re: [Wireshark-dev] Function getaddrinfo() vanished in one of the later commits.

2019-01-05 Thread hdv
On 5-1-2019 00:05, Guy Harris wrote: On Jan 4, 2019, at 2:38 PM, hdv wrote: I'm not a guru on CMake, so no idea if the libraries are binary loaded (probably) or built locally. I even don't know in which lib it was before, it just worked and now this surprises me. I followed the in

Re: [Wireshark-dev] Function getaddrinfo() vanished in one of the later commits.

2019-01-05 Thread hdv
On 5-1-2019 18:56, Guy Harris wrote: On Jan 5, 2019, at 7:29 AM, hdv wrote: Ok, I assume there *could* be a binary (static) lib distributed with Wireshark, so it is not the case apparently. So I don't have to search for the problem there. The makefiles refer to "GLIB2_LIBRARIES&

Re: [Wireshark-dev] Function getaddrinfo() vanished in one of the later commits. -> solved.

2019-01-05 Thread hdv
On 5-1-2019 22:20, Guy Harris wrote: On Jan 5, 2019, at 1:08 PM, hdv wrote: wsutil is already in the dependency list. So its not in there. Please send us your modified version of extcap/CMakeLists.txt. I fixed it: the function is in 'ws2_32' and I added it conditionally as fo

Re: [Wireshark-dev] Function getaddrinfo() vanished in one of the later commits. -> solved.

2019-01-06 Thread hdv
des a functionality only available on a specific platform, but then the inclusion in the build itself can be conditional (aka only build it, if you are on the correct platform). cheers Roland Am Sa., 5. Jan. 2019 um 22:35 Uhr schrieb hdv <mailto:henri.de.v...@gmail.com>>: On 5-1-2019 22:

Re: [Wireshark-dev] Cannot get external capture (extcap) interface to work with my new plugin.

2019-01-09 Thread hdv
On 4-1-2019 00:10, Dario Lombardo wrote: On Thu, Jan 3, 2019 at 5:36 PM hdv <mailto:henri.de.v...@gmail.com>> wrote: I really would expect that the stderr channel could be used to report errors in some way. Tested it, does not display anything until you stop the capture.

Re: [Wireshark-dev] Input plugin for PEAK Systems CAN interfaces

2021-03-27 Thread hdv
On 26-3-2021 13:32, Miklós Márton wrote: Hello all! I would like to create a Wireshark plugin for the PEAK CAN devices. Wireshark works fine with these devices on Linux over SocketCAN, however on Windows I did not found any way to utilize them. Is there any open source CAN input plugins out in