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

2011-12-22 Thread Gisle Vanem

"Guy Harris"  wrote:


Send us a patch, submit it on SourceForge, or do whatever the shiny new Git 
magic
is for that (Michael, how do people do that?).


This is what I do (and what the sourceforge page [1] states). 1st time 
checkout:

 git clone git://bpf.tcpdump.org/libpcap

Then  "git fetch" to update. But using Sourceforge to commit patches and
feature requests is not ideal IMHO (besides SF is so slow). Why not send
patches to this list so reach a larger audience of critical readers?

[1] http://www.tcpdump.org/#source

--gv

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


Re: [tcpdump-workers] tcpdump license and Nokia

2011-12-22 Thread Michael Richardson

> "Guy" == Guy Harris  writes:
>> I thought Berkley had made a general statement that some of those
>> clauses (esp. the advertising one) could be removed??

Guy> The statement made by the Directory of Technology Licensing at
Guy> UCB was:

Guy>
Guy> ftp://ftp.cs.berkeley.edu/pub/4bsd/README.Impt.License.Change

Assuming that this statement applied to everything that was on that web
site, and a version of tcpdump was included in that archive... 
it seems that we should reasonably be able to conclude that the
statement applies to it all.

Guy> So I'm not sure whether the letter from William Hoskins applies
Guy> or not.  I asked some people at the Technology Transfer
Guy> Division at LBL, but got no response.

Is there someone that lives in the right part of the Bay Area, that can
just walk into the right campus pub, and either find Mr.Hoskins, or the
relevant person?

-- 
]   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. 


pgpCFUp90hgrg.pgp
Description: PGP signature


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

2011-12-22 Thread Michael Richardson

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

A shared libpcap that was linked correctly would indicate it's
dependancy on that library and it would get loaded.  If the library
didn't exist, then there would be a problem, but that dependancy would
also be built into rpm/dpkg/pkg_add/etc. 

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

Basically, that 90% of the point of autoconf.

http://www.edwardrosten.com/code/autoconf/
seems to be a reasonable cheat sheet.

-- 
]   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] Fwd: New datasource implementation

2011-12-22 Thread Michael Richardson

Gisle> This is what I do (and what the sourceforge page [1]
Gisle> states). 1st time checkout: git clone
Gisle> git://bpf.tcpdump.org/libpcap

Alternatively, visit github, get an account, upload your ssh public key,
etc. 
Visit github.com/mcr/tcpdump, and fork the code.
Then use the github's URL, like:
 git clone g...@github.com:myname/tcpdump.git

and then push to that repo, and ask me to do a pullup.  

The two methods are *NOT* mutually exclusive.  Assuming that you already
git the clone from bpf.tcpdump,org,  you can do the github fork, and do:
cd libpcap 
git remote add github g...@github.com:myname/libpcap.git
git push github master

(that's how I get the merged code from github back onto
bpf.tcpdump.org...) 

Since git can publish over HTTP, you can even just tar/ssh, scp, or
symlink your repo into your web space, and say "here is the URL", but
there are some limitations of http: URLs relating to caches, and
compression and the like.

-- 
]   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] tcpdump license and Nokia

2011-12-22 Thread Chris Maynard
Tyson Key  gmail.com> writes:

> For what it's worth, you could try asking Petra Söderling (
> petra.soderling  nokia.com) - who happens to head some of the Open Source
> initiatives at Nokia.

For what it's worth, I e-mailed him.  Thanks again.
- Chris


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


Re: [tcpdump-workers] tcpdump license and Nokia

2011-12-22 Thread Guy Harris

On Dec 22, 2011, at 11:32 AM, Chris Maynard wrote:

> For what it's worth, I e-mailed him.  Thanks again.

I hope your e-mail didn't use any masculine pronouns when referring to Petra:

http://www.linkedin.com/in/petrasoderling

:-)

Not that it matters, as the Nokia unit whose appliances used IPSO was sold to 
Check Point:

http://www.checkpoint.com/nokia/welcome/index.html

so the mutant flavor of tcpdump (and probably of libpcap and possibly even the 
kernel BPF code) now belongs to them.-
This is the tcpdump-workers list.
Visit https://cod.sandelman.ca/ to unsubscribe.


Re: [tcpdump-workers] tcpdump license and Nokia

2011-12-22 Thread Chris Maynard
Guy Harris  alum.mit.edu> writes:

> On Dec 22, 2011, at 11:32 AM, Chris Maynard wrote:
> 
> > For what it's worth, I e-mailed him.  Thanks again.
> 
> I hope your e-mail didn't use any masculine pronouns when referring to Petra:
> 
>   http://www.linkedin.com/in/petrasoderling

Oops, thanks for pointing that out.  Luckily, I only used "you" in my e-mail to
her and no gender-specific pronouns.

> Not that it matters, as the Nokia unit whose appliances used IPSO was sold to
Check Point:
> 
>   http://www.checkpoint.com/nokia/welcome/index.html
> 
> so the mutant flavor of tcpdump (and probably of libpcap and possibly even the
kernel BPF code) now belongs
> to them.

Well, if she's no longer the person in charge of open source at Nokia, there
might be a chance she knows who is and can either let me know or forward my
request to that person.  I won't hold my breath though.
 

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


Re: [tcpdump-workers] tcpdump license and Nokia

2011-12-22 Thread Chris Maynard
Chris Maynard  gtech.com> writes:

> > Not that it matters, as the Nokia unit whose appliances used IPSO was sold 
> > to
> Check Point:
> > 
> > http://www.checkpoint.com/nokia/welcome/index.html
> > 
> > so the mutant flavor of tcpdump (and probably of libpcap and possibly even
> the kernel BPF code) now belongs
> > to them.
> 
> Well, if she's no longer the person in charge of open source at Nokia, there
> might be a chance she knows who is and can either let me know or forward my
> request to that person.  I won't hold my breath though.

OK, well I decided to open a checkpoint service request about this, basically
asking them for more information regarding the IPSO tcpdump/libpcap file format.
 I understand that they are under no obligation to release any of this
information, so it's doubtful I'll receive anything.  On the other hand, it's
certain that I won't receive anything if I don't even ask for it, so I figured
I'd take a chance.  In the unlikely event that they do share some information
with me, I'll be sure to pass it along.




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


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

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

Please check: axos88/libpcap.git

Regards,
  Ákos Vandra

P.S. Why are configure and config.h.in tracked? Shouldn't these be
generated by autoconf and autoheader?

On 22 December 2011 20:01, Michael Richardson  wrote:
>
>    Gisle> This is what I do (and what the sourceforge page [1]
>    Gisle> states). 1st time checkout: git clone
>    Gisle> git://bpf.tcpdump.org/libpcap
>
> Alternatively, visit github, get an account, upload your ssh public key,
> etc.
> Visit github.com/mcr/tcpdump, and fork the code.
> Then use the github's URL, like:
>     git clone g...@github.com:myname/tcpdump.git
>
> and then push to that repo, and ask me to do a pullup.
>
> The two methods are *NOT* mutually exclusive.  Assuming that you already
> git the clone from bpf.tcpdump,org,  you can do the github fork, and do:
>    cd libpcap
>    git remote add github g...@github.com:myname/libpcap.git
>    git push github master
>
> (that's how I get the merged code from github back onto
> bpf.tcpdump.org...)
>
> Since git can publish over HTTP, you can even just tar/ssh, scp, or
> symlink your repo into your web space, and say "here is the URL", but
> there are some limitations of http: URLs relating to caches, and
> compression and the like.
>
> --
> ]       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.


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

2011-12-22 Thread Guy Harris

On Dec 22, 2011, at 5:51 PM, Akos Vandra wrote:

> This is another project, that adds support for a canusb adapter,

So this adapter doesn't just show up as a regular SocketCAN network adapter 
when you plug it in?-
This is the tcpdump-workers list.
Visit https://cod.sandelman.ca/ to unsubscribe.


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

2011-12-22 Thread Akos Vandra
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 project, that adds support for a canusb adapter,
>
> So this adapter doesn't just show up as a regular SocketCAN network adapter 
> when you plug it in?-
> 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.