discuss-gnuradio
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Discuss-gnuradio] gr-ieee802.11 Questions


From: Cinaed Simson
Subject: Re: [Discuss-gnuradio] gr-ieee802.11 Questions
Date: Thu, 15 Dec 2016 20:04:08 -0800
User-agent: Mozilla/5.0 (X11; Linux i686; rv:45.0) Gecko/20100101 Thunderbird/45.5.1

On 12/13/2016 01:45 AM, Manolis Surligas wrote:
> Are you sure? Last time I checked, the RPi3 could not perform realtime
> (quite simple) filtering at 10 MHz. I doubt it can handle the 20 MSPS of
> the 802.11.
> 

Does this software work with the HackRF or BladeRF?

I was able to install the gr-ieee802.11-next without any problems but I
wasn't able to install gr-foo - or the wireshark connector - because I
don't have the UHD drivers or libraries installed.


> 
> On 12/12/2016 09:01 PM, Eric Yates wrote:
>> Hi Paul,
>>
>> Thanks for the quick response. The RPi 3 had enough processing power
>> to receive a message using gr-ieee802.15.4 from a ZigBee chip in
>> real-time. I believe I'm running the Wifi also in real-time, is there
>> a way to do it in non-real time instead?
>>
>> Thanks,
>>
>> Eric Yates
>>
>> On Mon, Dec 12, 2016 at 12:58 PM, Garver, Paul W <address@hidden
>> <mailto:address@hidden>> wrote:
>>
>>     I would be shocked if the Raspberry Pi 3 has the processing power
>>     to run gr-ieee80211. Are you attempting to do this real-time?
>>
>>     PWG
>>>     On Dec 12, 2016, at 10:31 AM, Eric Yates <address@hidden
>>>     <mailto:address@hidden>> wrote:
>>>
>>>     Hello,
>>>
>>>     I'm running gr-ieee802.11 on a Raspberry Pi 3 running Raspbian.
>>>     I'm connected to a bladeRF and running GRC 3.7.10. At this point,
>>>     I want to sniff WiFi packets to demonstrate the bladeRF working
>>>     with receiving WiFi from say a router or laptop (no transmission
>>>     yet). I'm using the 2.4GHz band with 20MHz bandwidth because
>>>     bladeRF does not go up to the 5GHz band.
>>>
>>>     In the WiFi RX example, I only changed the USRP Source to a
>>>     Osmocom Source block. In this example, it appears Wireshark has
>>>     been connecting to GRC via the /tmp/wifi.pcap pipe because the
>>>     Wireshark capture session closes when I kill the WiFi RX script.
>>>     The constellation and time graphs both work, but I do not see any
>>>     packets in Wireshark no matter the channel. Executing the script
>>>     produces no errors, it just doesn't capture packets.
>>>
>>>     I thought the FFT block might be to blame because it had no
>>>     documentation for it while all the other blocks did. I
>>>     reinstalled fftw3 (v. >3) and it didn't update the documentation.
>>>     osmocom_fft also works, so I don't think the FFT block is the
>>>     problem but I wonder why it's missing documentation. Then, I
>>>     reinstalled gnuradio and gr-ieee802.11 both after making sure the
>>>     necessary dependencies were met for both. Still no changes.
>>>     Wireshark receives packets from the WiFi Loopback example sent by
>>>     the message strobe perfectly fine. 
>>>
>>>     I would greatly appreciate any insights you have into why
>>>     Wireshark is not receiving any WiFi packets from the bladeRF
>>>     using the WiFi RX example. Do you have any ideas of what's going
>>>     on or would you need any more information?
>>>
>>>     Thank you,
>>>
>>>     Eric Yates
>>>     _______________________________________________
>>>     Discuss-gnuradio mailing list
>>>     address@hidden <mailto:address@hidden>
>>>     https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
>>>     <https://lists.gnu.org/mailman/listinfo/discuss-gnuradio>
>>
>>
>>
>>
>> _______________________________________________
>> Discuss-gnuradio mailing list
>> address@hidden
>> https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
> 
> -- 
> /* Code is the Law */
> 
> 
> 
> _______________________________________________
> Discuss-gnuradio mailing list
> address@hidden
> https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
> 




reply via email to

[Prev in Thread] Current Thread [Next in Thread]