Hi all!
I have just written a trace port analyzer for ARMv7-M architecture
microcontrollers. The trace datastream is sent over a serial port to
the PC, where it is packed into frames and decoded.
I'd like to present these data packets to the user using wireshark, as
it already has a very nice and
Hi!
I have just written support for one of my CAN->USB adapter gadgets, so
that it would work with libpcap and thus with wireshark. I would love
to see support for my device as an option in future releases.
This is a USB adapter, and I am using libusb-1.0 to communicate with
the device. So in ord
Hi!
As I have not received any response to my last 3-4 emails to the list,
can someone please confirm that my emails are getting in?
Thanks,
Ákos
-
This is the tcpdump-workers list.
Visit https://cod.sandelman.ca/ to unsubscribe.
I might have had some email-difficulitites, I am not sure if my email
got to the list, so I am sending it in.
Please help me, if possible.
Regards,
Ákos
-- Forwarded message --
From: Akos Vandra
Date: 17 December 2011 17:54
Subject: New datasource implementation
To: tcpdump
Hi,
On 20 December 2011 15:36, Michael Richardson wrote:
>
>>>>>> "Akos" == Akos Vandra writes:
> Akos> At the moment I am using a script-generated code to load the
> Akos> library run-time, and load all the symbols to the according
> Ak
Mkay, I think I did it... Although I'm not sure :)
@Guy Harris: I dropped the ARM trace thing, it turned out that
wireshark is not really suitable for what I want to do. This is
another project, that adds support for a canusb adapter, and uses
DLT_SOCKETCAN, so there is no need for a new DLT.
Ple
No, it doesn't. It's a device designed by myself, I just adjusted its
output format to be the same as DLT_SOCKETCAN expects.
Regards,
Ákos Vandr
On 23 December 2011 03:58, Guy Harris wrote:
>
> On Dec 22, 2011, at 5:51 PM, Akos Vandra wrote:
>
>> This is another proje
Hi!
I just wrote a little guide, based on my own experiences on how to add
a new datasource and how to contribute code to the libpcap project,
because I found this information quite hard to figure out by myself.
I added a new file named HACKING, and pushed it to my github port,
axos88/libpcap.git
Yeah, I forgot to push it to the remote repo, now it should be there.
Ákos
On 28 December 2011 00:07, Guy Harris wrote:
>
> On Dec 27, 2011, at 12:53 PM, Michael Richardson wrote:
>
>> I plan to let a 4.1.2 (perhaps a 4.2) out tomorrow.
>
> Do you mean "4.1.2" or "4.2.1"? 4.2.0, and libpcap 1.2
later on. Also I'm not
sure if m$ windows supports socketcan?
Regards,
Ákos
On 28 December 2011 12:23, Felix Obenhuber wrote:
> Hi,
>
> On Sat, 2011-12-17 at 17:54 +0100, Akos Vandra wrote:
>> I have just written support for one of my CAN->USB adapter gadgets, so
>&
Hi!
When opening a capture device, is it possible to hand off some
initialization data to the libpcap handler?
For example, I have just added a handler for a canusb device. When
opening the device, it would be nice if it was possible to set the
baud rate, etc.
Would it be possible to use the BPF
t can be used
for as many interfaces as possible, but you guys decide! :)
Regards,
Ákos Vandra
On 5 January 2012 01:36, Guy Harris wrote:
>
> On Jan 4, 2012, at 4:10 PM, Akos Vandra wrote:
>
>> When opening a capture device, is it possible to hand off some
>> initialization data
Hi!
I have read through the threads you mentioned, it's nice to see that
something similar has already been suggested, I would like to present
a few new arguments in favor of them.
On 6 January 2012 12:15, Guy Harris wrote:
>
> On Jan 5, 2012, at 1:40 AM, Akos Vandra wrote:
>
On 6 January 2012 17:16, Jakub Zawadzki wrote:
> On Fri, Jan 06, 2012 at 04:47:09PM +0100, Akos Vandra wrote:
>> Another reason why this is not a good approach: Let's get wireshark in
>> the picture. Let's say the user selected a canusb device. The only way
>
necessary... Either that, or the interface has to be
changed to somehow accomodate multiple type input parameters...
Varargs maybe?
Regards,
Ákos
On 11 January 2012 10:24, Guy Harris wrote:
>
> On Jan 6, 2012, at 2:16 PM, Akos Vandra wrote:
>
>> On 6 January 2012 17:16, Jakub
On 12 January 2012 10:38, Guy Harris wrote:
>
> On Jan 12, 2012, at 1:06 AM, Akos Vandra wrote:
>
>> We could put a limit - say 32 or 64 chars - to the max length of the
>> param, and then allocate in on the stack, but it would still require
>> printf.
>
> Where w
Hi!
What's your opinions on this? If you aggree, I would start doing some
initial coding sometime in the next few days, and then we can continue
the debate from there - unless I missed that it was dismissed.
Regards,
Ákos Vandra
On 12 January 2012 11:43, Akos Vandra wrote:
> On 12
17 matches
Mail list logo
