Re: Equivalent to Wireshark for wireless adapters?

On Tue, 04 Aug 2009 23:34:04 +0100, Colin Wilson wrote:

>> As per the title really.
>
> Won't wireshark listen to wifi ?

Yes - it will listen to any interface it does not care. Caveat - the
interface supports;
WIRED: promiscuous
WIRELESS: monitor

However, that may not be what he wants to do and Airsnort / aircrack may
be the tools he needs for the job. Of course, he won't see this reply as
he killfiled me (with outlook express ? really ?) ages ago. Still, there
you go - he may see a 'follow up'.

On Tue, 04 Aug 2009 17:53:22 -0700, bod43 wrote:

> Well, maybe the OP is using Windows. In this case you need to buy the
> wireless PCAP shim since the free one will not work with wireless cards.

I overlooked 'Windows' - you tend to forget the people who live in the
slums of the operating system world ;-) - the Outlook Express was really
the cue there - I posted it myself, I joked about the killfile and then
directed the OP to O/S Linux Software. I must pay more attention.

On Wed, 05 Aug 2009 08:51:32 +0100, Peter Crosland waxed with flowery
words of wisdom:

> "bod43" <(E-Mail Removed)> wrote in message
> news:1a3e8ed5-b41e-4845-b8b3-(E-Mail Removed)...
> On 5 Aug, 00:16, R Johnson <bou...@null.invalid> wrote:
>> On Tue, 04 Aug 2009 23:34:04 +0100, Colin Wilson wrote:
>> >> As per the title really.
>>
>> > Won't wireshark listen to wifi ?
>>
>> Yes - it will listen to any interface it does not care. Caveat - the
>> interface supports;
>> WIRED: promiscuous
>> WIRELESS: monitor
>>
>> However, that may not be what he wants to do and Airsnort / aircrack
>> may be the tools he needs for the job. Of course, he won't see this
>> reply as he killfiled me (with outlook express ? really ?) ages ago.
>> Still, there you go - he may see a 'follow up'.
>
> Well, maybe the OP is using Windows. In this case you need to buy the
> wireless PCAP shim since the free one will not work with wireless cards.
>
> An alternative for troubleshooting is to use the Microsoft Network
> Moinitor
> which does work on Wireless interfaces. Of course some adaptors/drivers
> won't work in promiscuous mode. It's a free download.
> http://www.microsoft.com/downloads/details.aspx?
FamilyID=983b941d-06cb-4658-b7f6-3088333d062f&displaylang=en
>
> If possible you should probably go the linux route since that will be
> more flexible in the long run. Or buy the PCAP shim. [Warning - I have
> no experience of this]
>
> http://www.cacetech.com/products/
>
> Obviously you need to check for compatibility with your wireless
> interface - in all cases.
>
> Thanks for all that. Quite a lot of the software I use daily has no
> LINUX alternative whatsoever so using it is not a viable option for me.

But a bootable linux cd or usb key may just hold the answer. Cost, under
10p ;-)

On Wed, 05 Aug 2009 10:19:06 +0100, Peter Crosland waxed with flowery
words of wisdom:

> "Dave Devnull" <(E-Mail Removed)> wrote in message
> news:4a79407e$0$2535$(E-Mail Removed)...
>> On Wed, 05 Aug 2009 08:51:32 +0100, Peter Crosland waxed with flowery
>> words of wisdom:
>>
>>> "bod43" <(E-Mail Removed)> wrote in message
>>> news:1a3e8ed5-b41e-4845-b8b3-
(E-Mail Removed)...
>>> On 5 Aug, 00:16, R Johnson <bou...@null.invalid> wrote:
>>>> On Tue, 04 Aug 2009 23:34:04 +0100, Colin Wilson wrote:
>>>> >> As per the title really.
>>>>
>>>> > Won't wireshark listen to wifi ?
>>>>
>>>> Yes - it will listen to any interface it does not care. Caveat - the
>>>> interface supports;
>>>> WIRED: promiscuous
>>>> WIRELESS: monitor
>>>>
>>>> However, that may not be what he wants to do and Airsnort / aircrack
>>>> may be the tools he needs for the job. Of course, he won't see this
>>>> reply as he killfiled me (with outlook express ? really ?) ages ago.
>>>> Still, there you go - he may see a 'follow up'.
>>>
>>> Well, maybe the OP is using Windows. In this case you need to buy the
>>> wireless PCAP shim since the free one will not work with wireless
>>> cards.
>>>
>>> An alternative for troubleshooting is to use the Microsoft Network
>>> Moinitor
>>> which does work on Wireless interfaces. Of course some
>>> adaptors/drivers won't work in promiscuous mode. It's a free download.
>>> http://www.microsoft.com/downloads/details.aspx?
>> FamilyID=983b941d-06cb-4658-b7f6-3088333d062f&displaylang=en
>>>
>>> If possible you should probably go the linux route since that will be
>>> more flexible in the long run. Or buy the PCAP shim. [Warning - I have
>>> no experience of this]
>>>
>>> http://www.cacetech.com/products/
>>>
>>> Obviously you need to check for compatibility with your wireless
>>> interface - in all cases.
>>>
>>> Thanks for all that. Quite a lot of the software I use daily has no
>>> LINUX alternative whatsoever so using it is not a viable option for
>>> me.
>>
>> But a bootable linux cd or usb key may just hold the answer. Cost,
>> under 10p ;-)
>
>
> Good idea but sadly this will not work as the problem is with some
> non-LINUX software for which there is no LINUX equivalent.
>
> Peter Crosland

There will be a tool in Linux to do what you want to do - but it may not
do it the way you want it to :-)

What is it you are trying to do, if I may be as bold as to ask?

On Wed, 05 Aug 2009 11:05:57 +0100, Peter Crosland waxed with flowery
words of wisdom:

> "Dave Devnull" <(E-Mail Removed)> wrote in message
> news:4a795406$0$2489$(E-Mail Removed)...
>> On Wed, 05 Aug 2009 10:19:06 +0100, Peter Crosland waxed with flowery
>> words of wisdom:
>>
>>> "Dave Devnull" <(E-Mail Removed)> wrote in message
>>> news:4a79407e$0$2535$(E-Mail Removed)...
>>>> On Wed, 05 Aug 2009 08:51:32 +0100, Peter Crosland waxed with flowery
>>>> words of wisdom:
>>>>
>>>>> "bod43" <(E-Mail Removed)> wrote in message
>>>>> news:1a3e8ed5-b41e-4845-b8b3-
>> (E-Mail Removed)...
>>>>> On 5 Aug, 00:16, R Johnson <bou...@null.invalid> wrote:
>>>>>> On Tue, 04 Aug 2009 23:34:04 +0100, Colin Wilson wrote:
>>>>>> >> As per the title really.
>>>>>>
>>>>>> > Won't wireshark listen to wifi ?
>>>>>>
>>>>>> Yes - it will listen to any interface it does not care. Caveat -
>>>>>> the interface supports;
>>>>>> WIRED: promiscuous
>>>>>> WIRELESS: monitor
>>>>>>
>>>>>> However, that may not be what he wants to do and Airsnort /
>>>>>> aircrack may be the tools he needs for the job. Of course, he won't
>>>>>> see this reply as he killfiled me (with outlook express ? really ?)
>>>>>> ages ago. Still, there you go - he may see a 'follow up'.
>>>>>
>>>>> Well, maybe the OP is using Windows. In this case you need to buy
>>>>> the wireless PCAP shim since the free one will not work with
>>>>> wireless cards.
>>>>>
>>>>> An alternative for troubleshooting is to use the Microsoft Network
>>>>> Moinitor
>>>>> which does work on Wireless interfaces. Of course some
>>>>> adaptors/drivers won't work in promiscuous mode. It's a free
>>>>> download. http://www.microsoft.com/downloads/details.aspx?
>>>> FamilyID=983b941d-06cb-4658-b7f6-3088333d062f&displaylang=en
>>>>>
>>>>> If possible you should probably go the linux route since that will
>>>>> be more flexible in the long run. Or buy the PCAP shim. [Warning - I
>>>>> have no experience of this]
>>>>>
>>>>> http://www.cacetech.com/products/
>>>>>
>>>>> Obviously you need to check for compatibility with your wireless
>>>>> interface - in all cases.
>>>>>
>>>>> Thanks for all that. Quite a lot of the software I use daily has no
>>>>> LINUX alternative whatsoever so using it is not a viable option for
>>>>> me.
>>>>
>>>> But a bootable linux cd or usb key may just hold the answer. Cost,
>>>> under 10p ;-)
>>>
>>>
>>> Good idea but sadly this will not work as the problem is with some
>>> non-LINUX software for which there is no LINUX equivalent.
>>>
>>> Peter Crosland
>>
>> There will be a tool in Linux to do what you want to do - but it may
>> not do it the way you want it to :-)
>>
>> What is it you are trying to do, if I may be as bold as to ask?
>
>
> I am trying to establish why a proprietary piece of Windows software,
> that will not run under LINUX, is not communicating correctly.
>
> Peter Crosland
Now you see, if it were open source, you'd probably be able to find out
why without jumping through all those hoops :-)

Peter Crosland wrote:

> I am trying to establish why a proprietary piece of Windows software, that
> will not run under LINUX, is not communicating correctly.

Tried it under Wine?

--
Adrian C