[tcpdump-workers] Test

2011-12-20 Thread Akos Vandra
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.


Re: [tcpdump-workers] Test

2011-12-20 Thread Nikola Ciprich
Hi,
can't tell about later emails (i'm subscribed few days only), but
I received this email now, so it certainly works ;)
n.



On Tue, Dec 20, 2011 at 09:31:27AM +0100, Akos Vandra wrote:
> 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.
> 

-- 
-
Ing. Nikola CIPRICH
LinuxBox.cz, s.r.o.
28. rijna 168, 709 01 Ostrava

tel.:   +420 596 603 142
fax:+420 596 621 273
mobil:  +420 777 093 799
www.linuxbox.cz

mobil servis: +420 737 238 656
email servis: ser...@linuxbox.cz
-


pgpZ44Z4qQDDu.pgp
Description: PGP signature


[tcpdump-workers] Fwd: New datasource implementation

2011-12-20 Thread Akos Vandra
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-workers@lists.tcpdump.org


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 order for it to work, I need to libusb-1.0 linked as
well.

At the moment I am using a script-generated code to load the library
run-time, and load all the symbols to the according function pointers.
I am not very familiar with how dynamic libraries are linked, and
didn't want to hack around the makefiles too much.

So my questions are:
 - What are the steps needed to 'nicely' add support to a new device?
What do I have to add to the configuration, makefiles, #ifdefs, to add
conditional building?
 - How can I commit my newly supported device to the libpcap tree?
 - How can this libusb dependency be solved? I don't think it would
be fair to require all libpcap users to need libusb, just for one
device that they might not even use - conditional building might solve
this though.

Regards,
 Ákos Vandra
-
This is the tcpdump-workers list.
Visit https://cod.sandelman.ca/ to unsubscribe.


Re: [tcpdump-workers] Fwd: New datasource implementation

2011-12-20 Thread Michael Richardson

> "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
Akos> function pointers.  I am not very familiar with how dynamic

uhm, okay, but why?

Akos> So my questions are:  - What are the steps needed to 'nicely'
Akos> add support to a new device?  What do I have to add to the
Akos> configuration, makefiles, #ifdefs, to add conditional
Akos> building?   - How can I commit my newly supported device to
Akos> the libpcap tree?   - How can this libusb dependency be
Akos> solved? I don't think it would be fair to require all libpcap
Akos> users to need libusb, just for one device that they might not
Akos> even use - conditional building might solve this though.

./configure takes care of this.  libusb (and your code) would get used
if the library exists.

Fork the code on github.com, and start patching, and ask us to review.

-- 
]   He who is tired of Weird Al is tired of life!   |  firewalls  [
]   Michael Richardson, Sandelman Software Works, Ottawa, ON|net architect[
] m...@sandelman.ottawa.on.ca http://www.sandelman.ottawa.on.ca/ |device driver[
   Kyoto Plus: watch the video 
   then sign the petition. 
-
This is the tcpdump-workers list.
Visit https://cod.sandelman.ca/ to unsubscribe.


Re: [tcpdump-workers] twice past the taps, thence out to net?

2011-12-20 Thread Wyborny, Carolyn


>-Original Message-
>From: netdev-ow...@vger.kernel.org [mailto:netdev-ow...@vger.kernel.org]
>On Behalf Of Eric Dumazet
>Sent: Friday, December 16, 2011 11:45 AM
>To: Rick Jones
>Cc: Stephen Hemminger; Vijay Subramanian; tcpdump-
>work...@lists.tcpdump.org; net...@vger.kernel.org; Vick, Matthew;
>Kirsher, Jeffrey T
>Subject: Re: twice past the taps, thence out to net?
>
>Le vendredi 16 décembre 2011 à 11:35 -0800, Rick Jones a écrit :
>
>> I would *love* to.  All my accessible igb-driven hardware is in an
>> environment locked to the kernels already there :(  Not that it makes
>it
>> more possible for me to do it, but I suspect it does not require 30
>> receivers to reproduce the dups with netperf TCP_STREAM.  Particularly
>> if the tx queue len is at 256 it may only take 6 or 8. In fact let me
>> try that now...
>>
>> Yep, with just 8 destinations/concurrent TCP_STREAM tests from the one
>> system one can still see the duplicates in the packet trace taken on
>the
>> sender.
>>
>> Perhaps we can trouble the Intel guys to try to reproduce what I've
>seen?
>>
>
>I do have an igb card somewhere (in fact two dual ports), I'll do the
>test myself !
>
>Thanks
>
>
>--
>To unsubscribe from this list: send the line "unsubscribe netdev" in
>the body of a message to majord...@vger.kernel.org
>More majordomo info at  http://vger.kernel.org/majordomo-info.html

Let me know if I can do anything to assist.  Sorry to have overlooked this 
thread for a bit.

Thanks,

Carolyn

Carolyn Wyborny
Linux Development
LAN Access Division
Intel Corporation


-
This is the tcpdump-workers list.
Visit https://cod.sandelman.ca/ to unsubscribe.


Re: [tcpdump-workers] Fwd: New datasource implementation

2011-12-20 Thread Akos Vandra
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
>    Akos> function pointers.  I am not very familiar with how dynamic
>
> uhm, okay, but why?

When building wireshark based on the new libpcap with my module using
libusb-1.0, it didn't build, because it was missing symbols
(naturally, as wireshark didn't know it has to link libusb-1.0 as
well). So insted of digging into where I have to add them, it seemed
simpler to write a script.
Also it seems unnatural that only for my project wireshark, and any
other project using libpcap must use libusb-1.0...

>
>    Akos> So my questions are:  - What are the steps needed to 'nicely'
>    Akos> add support to a new device?  What do I have to add to the
>    Akos> configuration, makefiles, #ifdefs, to add conditional
>    Akos> building?   - How can I commit my newly supported device to
>    Akos> the libpcap tree?   - How can this libusb dependency be
>    Akos> solved? I don't think it would be fair to require all libpcap
>    Akos> users to need libusb, just for one device that they might not
>    Akos> even use - conditional building might solve this though.
>
> ./configure takes care of this.  libusb (and your code) would get used
> if the library exists.

I'm not quite sure I understand this. How would ./configure know that
that the libusb_claim_interface is in the libusb-1.0 library?
I'm sorry if I'm a bit slow here, I'm quite unfamiliar with autobuild
and autoconf, should look into them soon.

>
> Fork the code on github.com, and start patching, and ask us to review.
>

Allright, I started reading a tutorial on git and github, I only used
svn, and resisted git up until now. Don't really know why though.
But it seems more and more likely that if I will ever want to
contribute to an OS project, I must learn it, also it seems like a
nice tool...

Will get back to you as soon as I can create the commit.
Is there a how-to guide to how to add a new module to libpcap? Most OS
projects have a HACKING file, or something similar that would help me
get started on where to begin modifying...
My best guess would be to add a few lines to pcap-linux.c, to the
platfrom findalldevs function, between #ifdefs, but a guide would be
very nice to have.
If you can help me out with any nice documentation (on libpcap code
organization, or git/github) I would be very happy if you sent it to
me.

Regards,
  Ákos Vandra

> --
> ]       He who is tired of Weird Al is tired of life!           |  firewalls  
> [
> ]   Michael Richardson, Sandelman Software Works, Ottawa, ON    |net 
> architect[
> ] m...@sandelman.ottawa.on.ca http://www.sandelman.ottawa.on.ca/ |device 
> driver[
>   Kyoto Plus: watch the video 
>                       then sign the petition.
> -
> This is the tcpdump-workers list.
> Visit https://cod.sandelman.ca/ to unsubscribe.
-
This is the tcpdump-workers list.
Visit https://cod.sandelman.ca/ to unsubscribe.