-
Notifications
You must be signed in to change notification settings - Fork 27
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
Issue of not receiving packets during csi extraction #56
Comments
Hi! Good to hear from you again! Nexmon_csi itself has some instability, the driver crashes after some time. I was able to run it overnight, for about 16 hours, without crashes, but I've never tried running it for longer than that. Maybe you can have two Pi's setup very close to each other, and collect data on both of them. And have a script running which detects nexmon_csi crash and restarts the Pi. When one pi has crashed and is restarting, use data from the other pi. You can detect crashes by listening to nexmon crash messages in dmesg, or by running |
@zeroby0 Hi, I still haven't solved this problem. I'm using your nexmon csi bin, so I'll ask you again because I think I should ask you rather than asking seemoo nexmon. The logs below are output from dmesg. There seems to be no problem, but have you never experienced this? As you can see from the picture, I ran a repetition script. Sometimes I could do repetitions for a very long time, other times I got 514 packets during tcpdump after the 14th csi data extraction like this picture and was stopped in this state. After arbitrarily ending this state, even if I set chanspec and MAC again, csi packets will never be extracted again. Only reboot is the solution. Is the code to reboot raspberry pi valid in such cases as you told me above? I don't know if this state is because the tcpdump command stopped or if it doesn't capture csi packets. |
Hi, it's been a while since I wrote to you!
I'm using your tool well, but I have a question.
I installed the 5.10.92 kernel version of the nexmon extractor on Raspi 4B through your 'nexmon_csi_bin'. Sometimes the extraction goes well until the end, and sometimes the extraction stops in the middle. I thought this phenomenon was due to the instability of Raspi. But when I bought a few new raspberry pies and experimented with them, I found this phenomenon in the new Raspi 4B. Is there any instability in the nexmon extractor program itself?
Of course, it was useful to extract learning data because it is more often extracted, but I have to prepare for a situation where data extraction stops in the middle to extract 24 hours of test data a day. The sampling rates are 25Hz, and I'm extracting them with 5 minutes of extraction and 5 minutes of term for fear of overheating the device. I wonder if you have this experience. Or do you know anything about any instability in nexmon extractor?
The text was updated successfully, but these errors were encountered: