-
Notifications
You must be signed in to change notification settings - Fork 128
INJECTION: recv: No buffer space available #33
Comments
You're probably injecting too many packets at too high a rate for the transmitter to keep up. Try adding an inter-packet delay or reducing the number or size of packets. See also #22 |
@dhalperi |
google "linux increase scheduling priority" – will probably find you the right thing injection has a delay parameter – please read the code for the program |
Thanks so much, I have work it out. |
Glad it worked! Separating out injected CSI from many transmitters is not something the code currently supports; you will need to be clever and perhaps modify the code to do. Maybe put some special bytes in the packet payload to identify each individual transmitter, for example? |
@Evangeline0 Hello , I met some problems when I use the injection mode. because I cannot download the LORCONv1 or maybe I ignore somethings Thank you very much! |
@dhalperi I generate some bytes and send through the transmitter, but I can not find these bytes in the receiver buffer, can you give me some advice about extracting the custom packet?
The csi data is in the netlink_buffer, however, there seems no my own packet. |
You need to record the packet payload (MPDU) in order to see which device transmitted the packet. |
Dear Daniel ,now I got the injection's scripts work correctly, but the receiver receive handreds of packets , then it stops and shows that: recv: No buffer space available .How to figure it out?
Looking for your favourite reply.
The text was updated successfully, but these errors were encountered: