I have found that I can reconnect to my wireless access point after I
start the trace, and all works as expected (until the next trace, at
which time you see the problem again). The only other workaround I
have found is to run the capture from the command line, and then use
wireshark to
Since your MacBook Pro is new, Mike, you can actually call Apple for
support if you do not have access to their bug reporting system.
Maybe if enough people complain, Apple will eventually fix this.
In the mean time, I have found that I can reconnect to my wireless
access point after I
I see the same behavior on my MacBook Pro.
I spoke with Apple a couple times, and they were able to reproduce
the problem with tcpdump on an Intel machine. They confirmed it's a
bug, but said they don't support command-line utilities, and
finished off saying that they may or may not
