Skip to content
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

at86rf215 stops receiving until sending a packet #19653

Open
benpicco opened this issue May 23, 2023 · 0 comments
Open

at86rf215 stops receiving until sending a packet #19653

benpicco opened this issue May 23, 2023 · 0 comments
Labels
Type: bug The issue reports a bug / The PR fixes a bug (including spelling errors)

Comments

@benpicco
Copy link
Contributor

Description

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

@benpicco benpicco added the Type: bug The issue reports a bug / The PR fixes a bug (including spelling errors) label May 23, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Type: bug The issue reports a bug / The PR fixes a bug (including spelling errors)
Projects
None yet
Development

No branches or pull requests

1 participant