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

gnrc_sixlowpan_nd: Implement 6LoWPAN multihop DAD #208

Closed
miri64 opened this issue Sep 18, 2013 · 7 comments
Closed

gnrc_sixlowpan_nd: Implement 6LoWPAN multihop DAD #208

miri64 opened this issue Sep 18, 2013 · 7 comments
Assignees
Labels
Area: network Area: Networking Impact: major The PR changes a significant part of the code base. It should be reviewed carefully Type: enhancement The issue suggests enhanceable parts / The PR enhances parts of the codebase / documentation

Comments

@miri64
Copy link
Member

miri64 commented Sep 18, 2013

Until now a duplicate address detection according to RFC 6775 is missing. This includes:

@ghost ghost assigned miri64 Jan 19, 2014
@miri64 miri64 modified the milestones: Release NEXT MAJOR, Release 2014.04 Apr 7, 2014
@miri64
Copy link
Member Author

miri64 commented Apr 7, 2014

Depends on #861

@OlegHahm OlegHahm added the major label Jun 3, 2014
@OlegHahm OlegHahm modified the milestones: FIX ME FIRST, Release NEXT MAJOR Jun 3, 2014
@miri64 miri64 changed the title Implement 6LoWPAN duplicate address detection (DAD) Implement 6LoWPAN multihop duplicate address detection (DAD) Oct 13, 2016
@miri64 miri64 changed the title Implement 6LoWPAN multihop duplicate address detection (DAD) gnrc_sixlowpan_nd: Implement 6LoWPAN multihop DAD Oct 13, 2016
@miri64
Copy link
Member Author

miri64 commented Oct 13, 2016

Updated the title a little bit.

@kaspar030 kaspar030 removed this from the FIX ME FIRST milestone Oct 24, 2017
@danpetry
Copy link
Contributor

@miri64 still an issue?

@miri64
Copy link
Member Author

miri64 commented Mar 11, 2019

Yep, just very low on the priority list sadly... :(

@stale
Copy link

stale bot commented Sep 12, 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 Sep 12, 2019
@miri64 miri64 removed the State: stale State: The issue / PR has no activity for >185 days label Sep 12, 2019
@stale
Copy link

stale bot commented Mar 15, 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 15, 2020
@miri64 miri64 removed the State: stale State: The issue / PR has no activity for >185 days label Mar 15, 2020
@miri64
Copy link
Member Author

miri64 commented Jun 30, 2020

This is part of #3052 I just noticed. So let's close this as #3052 is more holistic

@miri64 miri64 closed this as completed Jun 30, 2020
@miri64 miri64 added this to the Release 2020.07 milestone Jul 6, 2020
CW-75 pushed a commit to CW-75/RIOT that referenced this issue Jul 1, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Area: network Area: Networking Impact: major The PR changes a significant part of the code base. It should be reviewed carefully Type: enhancement The issue suggests enhanceable parts / The PR enhances parts of the codebase / documentation
Projects
None yet
Development

No branches or pull requests

4 participants