Hi.
Did you check the name of the wireshark file is the same in the flowgraph
and in the temp file (if you are using the .sh file into the app folder)?
Best regards,
Cristian
2017-05-09 4:26 GMT-05:00 Bastian Bloessl :
>
> > On 9. May 2017, at 08:26, LiLi
> On 9. May 2017, at 08:26, LiLi wrote:
>
> If we want to capture frames from a route, we should change the codes.
> The codes on github can capture frames which generate by the wifi_tx codes
> bacause the value of FCS is constant. After we change the value OF FCS to be
Hi,
On 04/13/2017 12:20 PM, LiLi wrote:
> Hi,
> We couldn't capture anything when we put wireshark connector after 'decode
> MAC'. When debug was enable of 'decode Mac', we found the packets were all
> dropped. We tried to read codes of decode MAC block. We got a question
>
My previous comment
Hi,
We couldn't capture anything when we put wireshark connector after 'decode
MAC'. When debug was enable of 'decode Mac', we found the packets were all
dropped. We tried to read codes of decode MAC block. We got a question
below:
code lines :
if(result.checksum() != 558161692) {
From my experience with QAM PHY, there are some basic debug tools to verify you
are locked on the received signal. Personally, I like the constellation plot,
it's an easy visual to see if your QAM symbols are "hitting" the right spot.
Typically you have Modulation Error Ratio, SNR etc. I
Hi,
LiLi writes:
> Hi, everyone
>
> I am using gr-ieee-80211 to recieve wifi packets on 2.4G.
> The operating system is Ubuntu.The version of GNU RADIO is 3.7.5, and we use
> USRP N210 with SBX daughterboard.
> Our purpose:
> Capture packets of 802.11 protocol on 2.4G
Hi, everyone
I am using gr-ieee-80211 to recieve wifi packets on 2.4G.
The operating system is Ubuntu.The version of GNU RADIO is 3.7.5, and we use
USRP N210 with SBX daughterboard.
Our purpose:
Capture packets of 802.11 protocol on 2.4G or the other band SBX
daughterboard
Our problems:
When