Hi All Can somebody point me in the correct direction for reporting this..... I have looked on the Wireshark-user mailing list (which I am just joining) but nothing is mentioned. I just received my new MBP today, and the first thing I did was install MP and selfupdate... Then installed wireshark, everything compiles fine (good job MP team). The interesting issue is that as soon as I do a "> sudo tshark -i en1" it kills my wireless association, and I have to reconnect after the capture to get back into my Apple Extreme wireless connection, all other devices on the network are unaffected. If I run Wireshark under X it has the same effect. Running " > sudo tcpdump -i en1 works fine as you would expect. When running Wireshark the wireless network dies as soon as you open a "List the available Capture Interface" window the wireless connection dies. The window shows the interface "wlt1", "ifconfig" shows the en1 as inactive. Performing an actual capture on this interface shows the 802.11 beacon frames from my AP. This is annoying as I often use Wireshark to capture on my en0 while remaining connected to my network via en1, but as soon as I open a capture dialog, my network connection drops. Has anyone else seen this on Intel Macs? Or is it perhaps a function of the drives for the "Pre-802.11n" Athereos chipset used in the newest Macs?? Thanks in advance for any help. Regards Mike On Aug 8, 2006, at 3:00 PM, Eric Hall wrote:
On Tue, Aug 08, 2006 at 02:33:13PM -0700, Mike Savory wrote:
The Ethereal packet sniffer is changing names and getting a new home.... Wireshark. http://www.wireshark.org/
Wireshark 0.99.2 was Released Jul 17, 2006
Is anyone looking at upgrading/replacing the current Ethereal port ??
The Wireshark 0.99.2 fixes some security issues over the last ethereal 0.99.0, Revision 1 that is in the current portfile.
Is there a way of coping with a port that changes name? should there just be a new port for Wireshark. how about invalidating the old ethereal port (with a UI_message to says its been replaced by wireshark....)
The wireshark port was added 2 weeks ago....
Ethereal will get some sort of notice that wireshark exists, haven't decided how that will happen yet.
-eric
On Sat, Oct 28, 2006 at 04:26:06PM -0700, Mike Savory wrote: [snip]
When running Wireshark the wireless network dies as soon as you open a "List the available Capture Interface" window the wireless connection dies. The window shows the interface "wlt1", "ifconfig" shows the en1 as inactive. Performing an actual capture on this interface shows the 802.11 beacon frames from my AP.
This is annoying as I often use Wireshark to capture on my en0 while remaining connected to my network via en1, but as soon as I open a capture dialog, my network connection drops.
Has anyone else seen this on Intel Macs? Or is it perhaps a function of the drives for the "Pre-802.11n" Athereos chipset used in the newest Macs??
'wlt1' is the passive wireless interface driver from KisMac (see http://wiki.wireshark.org/CaptureSetup/WLAN), perhaps this is getting activated when you bring up the dialog and is thus dropping your en1 connection. Do you have anything like KisMac installed? -eric
Actually, I've seen this happen on my MacBook Pro as well and I do not have KisMac installed. I didn't have much time to search or do anything about it but I was going to mention this on the list, but looks like Mike beat me to it. On Oct 29, 2006, at 7:51 AM, Eric Hall wrote:
On Sat, Oct 28, 2006 at 04:26:06PM -0700, Mike Savory wrote: [snip]
When running Wireshark the wireless network dies as soon as you open a "List the available Capture Interface" window the wireless connection dies. The window shows the interface "wlt1", "ifconfig" shows the en1 as inactive. Performing an actual capture on this interface shows the 802.11 beacon frames from my AP.
This is annoying as I often use Wireshark to capture on my en0 while remaining connected to my network via en1, but as soon as I open a capture dialog, my network connection drops.
Has anyone else seen this on Intel Macs? Or is it perhaps a function of the drives for the "Pre-802.11n" Athereos chipset used in the newest Macs??
'wlt1' is the passive wireless interface driver from KisMac (see http://wiki.wireshark.org/CaptureSetup/WLAN), perhaps this is getting activated when you bring up the dialog and is thus dropping your en1 connection. Do you have anything like KisMac installed?
-eric
_______________________________________________ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/macports-users
-- Takashi Yoshida tyoshida [at] mac [dot] com
On Sun, Oct 29, 2006 at 10:12:58AM +0800, Takashi Yoshida wrote:
Actually, I've seen this happen on my MacBook Pro as well and I do not have KisMac installed. I didn't have much time to search or do anything about it but I was going to mention this on the list, but looks like Mike beat me to it.
Anyone with another flavor of recent x86 Mac seeing this problem? I don't have one to test with.... -eric
I just did a quick search on google, and looks like this may be a known issue. http://www.mail-archive.com/wireshark-users@wireshark.org/msg00363.html According to the mail, tcpdump also will behave the same way and they are waiting for a fix from Apple (no fix time estimate is given). I suppose those of us who use Intel based Mac may need to shout at Apple... On Oct 29, 2006, at 11:13 AM, Eric Hall wrote:
On Sun, Oct 29, 2006 at 10:12:58AM +0800, Takashi Yoshida wrote:
Actually, I've seen this happen on my MacBook Pro as well and I do not have KisMac installed. I didn't have much time to search or do anything about it but I was going to mention this on the list, but looks like Mike beat me to it.
Anyone with another flavor of recent x86 Mac seeing this problem? I don't have one to test with....
-eric
_______________________________________________ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/macports-users
-- Takashi Yoshida tyoshida [at] mac [dot] com
Hi all Just to agree... I have KisMac installed on my PPC laptop, but it is not installed on The Intel Core 2 Duo Mac Book Pro that I have problems with. Thanks for confirming the problem Takashi ... Eric, is there any specific test I can perform for you?? Regards Mike On Oct 28, 2006, at 8:13 PM, Eric Hall wrote:
On Sun, Oct 29, 2006 at 10:12:58AM +0800, Takashi Yoshida wrote:
Actually, I've seen this happen on my MacBook Pro as well and I do not have KisMac installed. I didn't have much time to search or do anything about it but I was going to mention this on the list, but looks like Mike beat me to it.
Anyone with another flavor of recent x86 Mac seeing this problem? I don't have one to test with....
-eric
_______________________________________________ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/macports-users
While running ethereal for x11 from DP the wireless drops out. I have a suspicion it's something apple implemented to prevent promiscuous mode on their cards even though the atheros chip is the best hailed for wardriving and reliability. This is with atheros 802.11g in 17" macbook pro, tried it on 10.4.6, 10.4.7, 10.4.8 with various versions of ethereal. Also notice some sensitivity on KisMac. James Cornell On Oct 28, 2006, at 8:13 PM, Eric Hall wrote:
On Sun, Oct 29, 2006 at 10:12:58AM +0800, Takashi Yoshida wrote:
Actually, I've seen this happen on my MacBook Pro as well and I do not have KisMac installed. I didn't have much time to search or do anything about it but I was going to mention this on the list, but looks like Mike beat me to it.
Anyone with another flavor of recent x86 Mac seeing this problem? I don't have one to test with....
-eric
_______________________________________________ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/macports-users
On Sun, Oct 29, 2006 at 03:13:57AM +0000, Eric Hall wrote:
On Sun, Oct 29, 2006 at 10:12:58AM +0800, Takashi Yoshida wrote:
Actually, I've seen this happen on my MacBook Pro as well and I do not have KisMac installed. I didn't have much time to search or do anything about it but I was going to mention this on the list, but looks like Mike beat me to it.
Anyone with another flavor of recent x86 Mac seeing this problem?
yes ive seen this happen with tcpdump. annoying! but not always... -- hail eris http://rubberduck.com/
participants (5)
-
Charlie Allom
-
Eric Hall
-
James Cornell
-
Mike Savory
-
Takashi Yoshida