tcpick-project

[Tcpick-project] Problem on MacOSX 10.3

[cirrus <ci...@gm...>]

Although the application does compile, when run it displays an error:

Starting tcpick 0.1.24 at 2004-09-07 01:38 BST
tcpick: listening on en0
SUICIDE: [main] BIOCSRTIMEOUT: Invalid argument

It seems that the problem is on line 156 of the tcpick.c file.
descr = pcap_open_live( dev, BUFSIZ, flags.notpromisc ? 0 : 1 , -1,
(char *)errbuf );
When changing the -1 (time to wait value) to something else, the
program compiles and runs, however it does not seem to capture any
packets. I've played with various values, but nothing seems to work
properly.

Any ideas/solutions?

Thanks,
cirrus

Please CC me, I'm not subscribed

Re: [Tcpick-project] Problem on MacOSX 10.3

[Francesco S. <dus...@in...>]

On Tue, 7 Sep 2004 02:15:51 +0100
cirrus <ci...@gm...> wrote:

> Starting tcpick 0.1.24 at 2004-09-07 01:38 BST
> tcpick: listening on en0
> SUICIDE: [main] BIOCSRTIMEOUT: Invalid argument

Thank you for reporting this bug!

> It seems that the problem is on line 156 of the tcpick.c file.
> descr = pcap_open_live( dev, BUFSIZ, flags.notpromisc ? 0 : 1 ,
> -1,(char *)errbuf );
> When changing the -1 (time to wait value) to something else,
> the program compiles and runs, however it does not seem to
> capture any packets. I've played with various values, but
> nothing seems to work properly.
> 
> Any ideas/solutions?

I am sorry. I don't' own a Mac and so I can only pray for
somebody that can hack tcpick source code to resolve these
platform-dependent problems.
I have googled around and I found this:
http://forums.devshed.com/archive/t-114659
It explains really deeply the problem, but doesn't seem to give a
solution.
Have you tested tcpick on other network interfaces? Does it work?

Thanks,
-Francesco

Re: [Tcpick-project] Problem on MacOSX 10.3

[cirrus <ci...@gm...>]

On Tue, 7 Sep 2004 23:51:30 +0000, Francesco Stablum
<dus...@in...> wrote:
> I am sorry. I don't' own a Mac and so I can only pray for
> somebody that can hack tcpick source code to resolve these
> platform-dependent problems.
> I have googled around and I found this:
> http://forums.devshed.com/archive/t-114659
> It explains really deeply the problem, but doesn't seem to give a
> solution.
> Have you tested tcpick on other network interfaces? Does it work?
> 
Yea i found that page, when I was looking around as well.
Unfortunately my programming skills are not very good at the moment so
I can't resolve the problem myself:).
I've tried it on both my ethernet interface and the airport wireless
one, but the results are the same.
The problem is most probably a platform-dependent one, with the
libpcap library. I've also been playing with sample libpcap packet
capture code (from
http://www.cet.nau.edu/~mc8/Socket/Tutorials/testpcap1.c), and I get
the same problem, however playing with the timeout variable on the
pcap_open_live function, it seemed it managed to dump some packets,
while the same doesn't work with tcpick.
Anyway if you need any testing done on MacOSX feel free to send me an
email whenever you want.

> Thanks,
> -Francesco

Thanks,
Cirrus