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

Jump to bottom

gnrc: Provide generic netapi ping #3791

Closed
miri64 opened this issue Sep 7, 2015 · 11 comments
Closed

gnrc: Provide generic netapi ping #3791

miri64 opened this issue Sep 7, 2015 · 11 comments
Assignees
@OlegHahm
Labels
Area: network Area: Networking Type: new feature The issue requests / The PR implemements a new feature for RIOT

Comments

@miri64
Copy link
Member

miri64 commented Sep 7, 2015

In the spirit of #3389 and the old layer 2 ping a generic ping application/module for any gnrc_netapi enabled module might be of use for testing.
@miri64 miri64 added this to the Release NEXT MAJOR milestone Sep 7, 2015
@OlegHahm OlegHahm modified the milestones: Release 2015.12, Release 2016.03 Dec 8, 2015
@OlegHahm OlegHahm modified the milestone: Release 2016.04 Mar 17, 2016
@miri64
Copy link
Member Author

miri64 commented Oct 17, 2016

@OlegHahm didn't you work on something like this?

@OlegHahm
Copy link
Member

Hm, yes, it might be, but it's probably horribly outdated.

@miri64 miri64 added Type: new feature The issue requests / The PR implemements a new feature for RIOT and removed Feature Request labels Sep 30, 2018
@stale
Copy link

stale bot commented Aug 10, 2019

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. If you want me to ignore this issue, please mark it with the "State: don't stale" label. Thank you for your contributions.

@stale stale bot added the State: stale State: The issue / PR has no activity for >185 days label Aug 10, 2019
@stale stale bot closed this as completed Sep 10, 2019
@miri64
Copy link
Member Author

miri64 commented Sep 10, 2019

I think this feature could still be interesting. Let's give it another 6 months ;-).

@miri64 miri64 reopened this Sep 10, 2019
@stale stale bot removed the State: stale State: The issue / PR has no activity for >185 days label Sep 10, 2019
@stale
Copy link

stale bot commented Mar 13, 2020

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. If you want me to ignore this issue, please mark it with the "State: don't stale" label. Thank you for your contributions.

@stale stale bot added the State: stale State: The issue / PR has no activity for >185 days label Mar 13, 2020
@stale stale bot closed this as completed Jun 4, 2020
@miri64 miri64 reopened this Jun 4, 2020
@stale stale bot removed the State: stale State: The issue / PR has no activity for >185 days label Jun 4, 2020
@stale
Copy link

stale bot commented Dec 6, 2020

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. If you want me to ignore this issue, please mark it with the "State: don't stale" label. Thank you for your contributions.

@stale stale bot added the State: stale State: The issue / PR has no activity for >185 days label Dec 6, 2020
@miri64 miri64 removed the State: stale State: The issue / PR has no activity for >185 days label Dec 6, 2020
@stale
Copy link

stale bot commented Jun 11, 2021

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. If you want me to ignore this issue, please mark it with the "State: don't stale" label. Thank you for your contributions.

@stale stale bot added the State: stale State: The issue / PR has no activity for >185 days label Jun 11, 2021
@miri64 miri64 removed the State: stale State: The issue / PR has no activity for >185 days label Jun 11, 2021
@MrKevinWeiss MrKevinWeiss added this to the Release 2021.07 milestone Jun 22, 2021
@MrKevinWeiss MrKevinWeiss removed this from the Release 2021.07 milestone Jul 15, 2021
@stale
Copy link

stale bot commented Mar 2, 2022

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. If you want me to ignore this issue, please mark it with the "State: don't stale" label. Thank you for your contributions.

@stale stale bot added the State: stale State: The issue / PR has no activity for >185 days label Mar 2, 2022
@stale stale bot closed this as completed Apr 19, 2022
@miri64 miri64 reopened this Apr 19, 2022
@stale stale bot removed the State: stale State: The issue / PR has no activity for >185 days label Apr 19, 2022
@maribu
Copy link
Member

maribu commented May 17, 2023

I'm not sure if I understand the feature request correctly. Is it ping as in ICMPv6 echo request and reply? Or is it some generic mechanism to check if network stack component is still alive and responsive? Or something else completely?

@miri64
Copy link
Member Author

miri64 commented May 23, 2023

The first: the pre-GNRC network stack had the ability to do (non-standardized) ICMPv6-echo-like behavior on the link layer. The idea was, to provide something generic based on netapi for any (packet based) layer. Not sure if this is something we still want or need though... Especially since the link layer (which started this whole discussion) is technically not part of GNRC anymore...

@maribu
Copy link
Member

maribu commented May 23, 2023

OK, then lets close this and see if someone complaints :)

@maribu maribu closed this as completed May 23, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@OlegHahm OlegHahm

Labels
Area: network Area: Networking Type: new feature The issue requests / The PR implemements a new feature for RIOT
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@miri64 @OlegHahm @maribu @MrKevinWeiss