You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
After some time at86rf215 stops receiving frames. It's unclear yet what triggers this, but it happens when running as a border router with gnrc_netif_pktq and handling fragmented frames.
In this state, the driver will ignore all incoming traffic until it has sent out a frame on it's own. After that, normal operation continues for some time until the problem occurs again.
Steps to reproduce the issue
???
Expected results
at86rf215 is always ready to receive frames.
Actual results
at86rf215 can get into a state where it stops receiving frames until it has sent out a frame on it's own.
Workaround
Periodically trigger a frame send to a non-existing address when operating as a border router.
Versions
The text was updated successfully, but these errors were encountered:
Description
After some time
at86rf215
stops receiving frames. It's unclear yet what triggers this, but it happens when running as a border router withgnrc_netif_pktq
and handling fragmented frames.In this state, the driver will ignore all incoming traffic until it has sent out a frame on it's own. After that, normal operation continues for some time until the problem occurs again.
Steps to reproduce the issue
???
Expected results
at86rf215
is always ready to receive frames.Actual results
at86rf215
can get into a state where it stops receiving frames until it has sent out a frame on it's own.Workaround
Periodically trigger a frame send to a non-existing address when operating as a border router.
Versions
The text was updated successfully, but these errors were encountered: