On Wednesday 14 June 2006 13:38, David Young wrote:
>
> I don't know how it works in Linux. In BSD, the taps are set up like
> this:
>
Thanks again. I solved my problem. I needed to do
echo '803' > /proc/sys/net/ath0/dev_type
on the device to switch it to radiotap header mode and also set up t
On Wed, Jun 14, 2006 at 01:04:05PM -0500, Matthew Belcher wrote:
> On Wednesday 14 June 2006 12:38, David Young wrote:
>
> > Are you sure this is a radiotap capture? Where it says "link-type
> > IEEE802_11," it should say "link-type IEEE802_11_RADIO". Perhaps the
> > driver is really creating a
Ury Segal wrote:
The buttom of the problem is this:
You excpect libpcap to call X::dumper in
the context of an instance of class X.
(The "real" first parameter of "X::dumper"
is a variable named "this" of the type "X*".)
But the libpcap API is not defining a
`void (X::)(u_char*, const pcap_
On Wednesday 14 June 2006 12:38, David Young wrote:
> Are you sure this is a radiotap capture? Where it says "link-type
> IEEE802_11," it should say "link-type IEEE802_11_RADIO". Perhaps the
> driver is really creating a radiotap capture, but it uses the wrong DLT?
Thanks Dave. Is there somethi
On Wed, Jun 14, 2006 at 04:48:02PM +0200, David Rosal wrote:
> I'm writing a packet sniffer in C++ using libpcap-0.9.4.
>
> I've tried to use a class function member as a callback for
> pcap_loop(), but the compiler complains that arguments don't
> match. The code is something like this (I have
On Wed, Jun 14, 2006 at 11:56:24AM -0500, Matthew Belcher wrote:
>
> > Are you running it with -s0 (or some larger-than-default capture size)?
> > A full RT header can be bigger than the 32 or 64 or whatever the default
> > # of bytes is for tcpdump to process.
>
> Thanks for your suggestion. I t
> Are you running it with -s0 (or some larger-than-default capture size)?
> A full RT header can be bigger than the 32 or 64 or whatever the default
> # of bytes is for tcpdump to process.
Thanks for your suggestion. I tried it with -s0 to see if that would help.
Here's what I get now:
(none):~
The buttom of the problem is this:
You excpect libpcap to call X::dumper in
the context of an instance of class X.
(The "real" first parameter of "X::dumper"
is a variable named "this" of the type "X*".)
But the libpcap API is not defining a
>`void (X::)(u_char*, const pcap_pkthdr*, const
> u_
David Rosal wrote:
I've tried to use a class function member as a callback for pcap_loop(),
but the compiler complains that arguments don't match. The code is
something like this (I have simplified it):
...
Should I avoid C++ and use C instead (don't say that please...)
Should you
Hello.
I'm writing a packet sniffer in C++ using libpcap-0.9.4.
I've tried to use a class function member as a callback for
pcap_loop(), but the compiler complains that arguments don't
match. The code is something like this (I have simplified it):
8<-
class X
{
10 matches
Mail list logo
