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 MacOS X. So its not wireshark  
> being at fault.

tcpdump works fine for me on Intel MacBook.  DarwinPorts Wireshark not so fine.

Wireshark-users mailing list

Reply via email to