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

Handle graceful shudown #178

Open
christophefontaine opened this issue Mar 10, 2025 · 0 comments
Open

Handle graceful shudown #178

christophefontaine opened this issue Mar 10, 2025 · 0 comments
Labels
triage Needs review and proper triage

Comments

@christophefontaine
Copy link
Collaborator

Description

When we quit grout (with ctrl+c), the other network elements do not know that.
In order to be kind with our neighbor routers, we need a way to send packets when we quit.

A generic event could be added, and triggered when we quit grout.
+ EVENT_GRACEFUL_SHUTDOWN = EVENT_TYPE(GR_INFRA_MODULE, 0xf000),
And we'd have to wait for the registered callbacks to be triggered before quitting.

Context and Use Cases

[6.2.5](https://www.rfc-editor.org/rfc/rfc4861#section-6.2.5).  Ceasing To Be an Advertising Interface

      - shutting down the system.
   In such cases, the router SHOULD transmit one or more (but not more
   than MAX_FINAL_RTR_ADVERTISEMENTS) final multicast Router
   Advertisements on the interface with a Router Lifetime field of zero.

While we don't break any RFC (SHOULD, not MUST), we should comply with it :)

@christophefontaine christophefontaine added the triage Needs review and proper triage label Mar 10, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
triage Needs review and proper triage
Projects
None yet
Development

No branches or pull requests

1 participant