Re: [Wireshark-users] Problem with 0.99.3a-1011 on MacBook
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 problem anymore unless you monitor the wtl interface. Wireshark works with this fine if you do "Capture- >Options" but not if you do "Capture->interfaces". The reason for this is that wireshark opens all interfaces to show the current "traffic". This includes the monitoring pseudo interface wtl which puts the WLAN offline to do monitoring. On 20.01.2007, at 18:37, Todd Wease wrote: 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 Wireshark-users@wireshark.org http://www.wireshark.org/mailman/listinfo/wireshark-users Andreas Fink Fink Consulting GmbH Global Networks Schweiz AG BebbiCell AG --- Tel: +41-61-330 Fax: +41-61-331 Mobile: +41-79-2457333 Address: Clarastrasse 3, 4058 Basel, Switzerland E-Mail: [EMAIL PROTECTED] www.finkconsulting.com www.global-networks.ch www.bebbicell.ch --- ICQ: 8239353 MSN: [EMAIL PROTECTED] AIM: smsrelay Skype: andreasfink Yahoo: finkconsulting SMS: +41792457333 ___ Wireshark-users mailing list Wireshark-users@wireshark.org http://www.wireshark.org/mailman/listinfo/wireshark-users
Re: [Wireshark-users] Problem with 0.99.3a-1011 on MacBook
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 Wireshark-users@wireshark.org http://www.wireshark.org/mailman/listinfo/wireshark-users
Re: [Wireshark-users] Problem with 0.99.3a-1011 on MacBook
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 PROTECTED]>Date: Mon, 4 Sep 2006 06:29:38 +0200This 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 MacBookw/ 10.4.7 causes my Airport interface to lose association as soon asI start a capture. It did capture some outgoing SNPMP packets anddecoded them OK, so a lot of is working, but I can't capture wirelesspackets.Anyone else have this or have any ideas?Thanks, -- Jim___ Wireshark-users mailing list Wireshark-users@wireshark.org http://www.wireshark.org/mailman/listinfo/wireshark-users
Re: [Wireshark-users] Problem with 0.99.3a-1011 on MacBook
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 tcpdump? If the same thing happens, file a bug with Apple against the driver for the Airport interface on the MacBook. ___ Wireshark-users mailing list Wireshark-users@wireshark.org http://www.wireshark.org/mailman/listinfo/wireshark-users
Re: [Wireshark-users] Problem with 0.99.3a-1011 on MacBook
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 > > ___ > Wireshark-users mailing list > Wireshark-users@wireshark.org > http://www.wireshark.org/mailman/listinfo/wireshark-users ___ Wireshark-users mailing list Wireshark-users@wireshark.org http://www.wireshark.org/mailman/listinfo/wireshark-users
[Wireshark-users] Problem with 0.99.3a-1011 on MacBook
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 ___ Wireshark-users mailing list Wireshark-users@wireshark.org http://www.wireshark.org/mailman/listinfo/wireshark-users
