the tcpdump which comes with the system from apple does work if you
specify the interface. (-i eth1)
if you dont, you hit a problem.
The wireshark installation I did (http://www.finkconsulting.com/
page7.php) was compiled with a newer version of libpcap and tcpdump
which dont have this probl
Andreas Fink <[EMAIL PROTECTED]> writes:
>
> This is a known bug. Shout at Apple about it. I opened a bug report
> about it long ago but Apple doesnt seem to care to fix it so far. And
> of course they leave you in the dark. You can reproduce the same
> problem with tcpdump which comes with
Thanks Andreas. Sure enough, tcpdump has the same behavior!Apple will probably fix it once enough people, especially their own developers, have MacBooks! -- JimPS: I'm not a subscriber so only just now checked the archives; this response will have to approved as well.From: Andreas Fink <[EMAIL P
Jim Forster wrote:
> Maybe I missed something as I'm not that up on installations,
> packages, etc, these day, but my Wireshark 0.99.3a-1011 on a MacBook
> w/ 10.4.7 causes my Airport interface to lose association as soon as
> I start a capture.
What happens if you start a capture with tcpdu
This is a known bug. Shout at Apple about it. I opened a bug report
about it long ago but Apple doesnt seem to care to fix it so far. And
of course they leave you in the dark. You can reproduce the same
problem with tcpdump which comes with MacOS X. So its not wireshark
being at fault.
On
Maybe I missed something as I'm not that up on installations,
packages, etc, these day, but my Wireshark 0.99.3a-1011 on a MacBook
w/ 10.4.7 causes my Airport interface to lose association as soon as
I start a capture. It did capture some outgoing SNPMP packets and
decoded them OK, so a l
