[Jim Forster <jrforster@xxxxxxx>]

Thanks Andreas.   Sure enough, tcpdump has the same behavior!

Apple will probably fix it once enough people, especially their own developers, have MacBooks!

  -- Jim

PS: I'm not a subscriber so only just now checked the archives; this response will have to approved as well.

From: Andreas Fink <andreas@xxxxxxxx>

Date: Mon, 4 Sep 2006 06:29:38 +0200

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 03.09.2006, at 07:46, 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.   It did capture some outgoing SNPMP packets and

decoded them OK, so a lot of is working, but I can't capture wireless

packets.

Anyone else have this or have any ideas?

Thanks,

   -- Jim