[tcpdump-workers] Libpcap++

[CaoPeng]

Hi all
First:
 How do I write a program with libpcap++.
(Libpcap++ can be download :http://libpcappp.sourceforge.net/)
and,I need some  examples.

Second:
There are some question about C++.
The Class Pcap in library libpcap++，I want to creat a Pcap object,but its
constructor is protected or private.
and,I need some example too.


o(∩_∩)o  I‘m sorry to my poor English，but，I really hope anyone can help me
-
This is the tcpdump-workers list.
Visit https://cod.sandelman.ca/ to unsubscribe.

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

[Michael Richardson]

> "Akos" == Akos Vandra  writes:
Akos> Mkay, I think I did it... Although I'm not sure :)

Akos> @Guy Harris: I dropped the ARM trace thing, it turned out that
Akos> wireshark is not really suitable for what I want to do. This
Akos> is another project, that adds support for a canusb adapter,
Akos> and uses DLT_SOCKETCAN, so there is no need for a new DLT.

Akos> Please check: axos88/libpcap.git

Akos> Regards, Ákos Vandra

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

In theory, yes.  In practice, end users never have the exact *right*
version of those utilities installed, and only people hacking that part
of the code need it.

If you "touch .devel" in the directory, configure does some more things,
including running "make depend".  Hmm. I thought it also assumed
autoconf existed, and would regenerate things, but I don't see that in 
./configure.

-- 
]   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] Wrote a little guide for people getting started.

[Michael Richardson]

> "Akos" == Akos Vandra  writes:
Akos> Hi!

Akos> I just wrote a little guide, based on my own experiences on
Akos> how to add a new datasource and how to contribute code to the
Akos> libpcap project, because I found this information quite hard
Akos> to figure out by myself.

Akos> I added a new file named HACKING, and pushed it to my github
Akos> port, axos88/libpcap.git.

Awsome!
I like all your text, but I didn't see it in your git tree?

I plan to let a 4.1.2 (perhaps a 4.2) out tomorrow.

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

[Guy Harris]

On Dec 27, 2011, at 12:58 PM, Michael Richardson wrote:

>> "Akos" == Akos Vandra  writes:
> 
>Akos> P.S. Why are configure and config.h.in tracked? Shouldn't
>Akos> these be generated by autoconf and autoheader?
> 
> In theory, yes.  In practice, end users never have the exact *right*
> version of those utilities installed, and only people hacking that part
> of the code need it.

The distribution tarballs should definitely include configure and config.h.in - 
but they could be generated by the process of making the release tarball; 
that's how Wireshark does it.  That way, end users don't need to have autoconf 
or autoheader installed at all, much less having the right version installed; 
as you note, the people hacking on the configure scripts would need to have 
them installed anyway.

> If you "touch .devel" in the directory, configure does some more things,
> including running "make depend".  Hmm. I thought it also assumed
> autoconf existed, and would regenerate things, but I don't see that in 
> ./configure.

Yes, we'd want Makefile rules to generate the configure script, and make the 
release tarball depend on configure so that those rules are run when you do 
"make releasetar".-
This is the tcpdump-workers list.
Visit https://cod.sandelman.ca/ to unsubscribe.

Re: [tcpdump-workers] Wrote a little guide for people getting started.

[Guy Harris]

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.0, are the current 
release, according to the Web site.  Both of them have significant bugs that 
are fixed in the current 4.2 and 1.2 branches.

Presumably they'll be announced on tcpdump-announce - I missed the 4.2.0/1.2.0 
releases as there wasn't an announcement.-
This is the tcpdump-workers list.
Visit https://cod.sandelman.ca/ to unsubscribe.