Skip to content

fix NULL pointer dereference, backport A-MSDU fixes for Raspberry Pi, RSSI, Frame Control, Phy Bits, etc #46

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
wants to merge 0 commits into from

Conversation

mzakharo
Copy link
Contributor

After I added the NULL pointer check, I monitored the log, and indeed, this check is happening sometimes. Also, A-MSDU skip helps Raspberry pi stay up without trapping.

@289536718 289536718 mentioned this pull request Apr 23, 2020
@mzakharo mzakharo closed this Jun 15, 2020
@mzakharo mzakharo changed the title fix NULL pointer dereference, backport A-MSDU fixes for Raspberry Pi fix NULL pointer dereference, backport A-MSDU fixes for Raspberry Pi, RSSI, Frame Control, Phy Bits, etc Jun 15, 2020
@mzakharo mzakharo reopened this Jun 15, 2020
@Gi-z Gi-z mentioned this pull request Oct 5, 2020
@tweigel-dev
Copy link
Contributor

great work! why this PR don't get any attention ?

@maurovm
Copy link

maurovm commented Feb 4, 2021

Excellent work Mikhail. Your changes fixed my problems. Check #177.

I vote for the authors of nexmon_csi to merge your pull request.

@Guolin-Yin
Copy link

Hi @mzakharo

I am using your pull request to obtain the RSSI value using Raspberry pi, but I found some problem with my data, the CSI value of the subcarrier from 28 to 35 are constant. (The subcarrier index range from 0 to 63)
image
I am not sure where this problem comes from, have you got the same problem?

@mzakharo
Copy link
Contributor Author

mzakharo commented Jun 9, 2021

Hi @mzakharo

I am using your pull request to obtain the RSSI value using Raspberry pi, but I found some problem with my data, the CSI value of the subcarrier from 28 to 35 are constant. (The subcarrier index range from 0 to 63)
image
I am not sure where this problem comes from, have you got the same problem?

I am assuming bandwidth of your capture is 20Mhz. For whatever reason, on 20MHz bandwidth, carriers 28-35 have no valid data, this behaviour has nothing to do with this patch, and occurs on master branch. if you inspect data more closely, you still get the expected valid 52 complex values from other points in the CSI vector.

@Guolin-Yin
Copy link

Hi @mzakharo
I am using your pull request to obtain the RSSI value using Raspberry pi, but I found some problem with my data, the CSI value of the subcarrier from 28 to 35 are constant. (The subcarrier index range from 0 to 63)
image
I am not sure where this problem comes from, have you got the same problem?

I am assuming bandwidth of your capture is 20Mhz. For whatever reason, on 20MHz bandwidth, carriers 28-35 have no valid data, this behaviour has nothing to do with this patch, and occurs on master branch. if you inspect data more closely, you still get the expected valid 52 complex values from other points in the CSI vector.

Thanks for replying, I have checked the data from the master branch, indeed, the carriers 28-35 have no valid data. I just realised that they are corresponding to the null subcarrier in OFDM.

@haochenku
Copy link

Hi @mzakharo The frame control information from my side does not look good. It changes a lot. Also I was expecting frame control from different cores should be same, but actually they are not. Could you have a look?
image

@mzakharo
Copy link
Contributor Author

mzakharo commented Jul 10, 2021 via email

@haochenku
Copy link

haochenku commented Jul 11, 2021 via email

@mzakharo
Copy link
Contributor Author

mzakharo commented Jul 11, 2021 via email

@haochenku
Copy link

haochenku commented Jul 11, 2021 via email

@mzakharo
Copy link
Contributor Author

mzakharo commented Jul 11, 2021 via email

@haochenku
Copy link

haochenku commented Jul 12, 2021 via email

@mzakharo
Copy link
Contributor Author

mzakharo commented Jul 12, 2021 via email

@CDeLeon94
Copy link

The reference file mentioned for decoding the phybits has been removed
(https://github.com/MerlinRdev/86u-merlin/blob/master/release/src-rt-5.02hnd/bcmdrivers/broadcom/net/wl/impl51/4365/src/include/d11.h#L2935)

Is there any other source that has this information?

@mzakharo
Copy link
Contributor Author

The reference file mentioned for decoding the phybits has been removed (https://github.com/MerlinRdev/86u-merlin/blob/master/release/src-rt-5.02hnd/bcmdrivers/broadcom/net/wl/impl51/4365/src/include/d11.h#L2935)

Is there any other source that has this information?

https://github.com/RMerl/asuswrt-merlin.ng/blob/6b60627c8c9c5c0271e956c914afb5277f81f9c4/release/src-rt-6.x.4708/include/d11.h#L2517
Most useful for CSI decoding is PRXS0_ACPHY_SUBBAND_MASK

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants