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 start the trace, and all works as expected
(until the next trace, at which time you see the problem again).
If you don't need to watch in real time I suppose you can:
% sudo tcpdump -i en1 -s0 -w qq.cap
% wireshark qq.cap
If anyone else has a better way, I sure would like to hear it.
Doc
On Nov 1, 2006, at 2:23 AM, Andreas Fink wrote:
>> On 29.10.2006, at 02:35, Mike Savory wrote:
>> The interesting issue is that as soon as I do a "> sudo tshark -i
>> en1" it kills my wireless association
>
> This is a known problem on MacBook Pro.
> If you have access to Apples Bugreporting system, open a bug about
> that.
> Maybe one day apple will fix that *sight*.
> It also happens when you simply type "tcpdump".
_______________________________________________
Wireshark-users mailing list
Wireshark-users@wireshark.org
http://www.wireshark.org/mailman/listinfo/wireshark-users
