-
Notifications
You must be signed in to change notification settings - Fork 106
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
deprecate prefix on prefix removal from interface #85
Comments
Hmmmmm... challenge accepted.
…Sent from my iPhone
On Feb 11, 2018, at 10:51 AM, mhanor ***@***.***> wrote:
Hello,
This issue is a continuation of the second part of the discussion we made in issue #36.
Currently, radvd is able to be notified of an address prefix being added or removed from an interface, but I'm still interested that its clients receive a RA to deprecate the prefix being removed from the interface, which radvd doesn't do.
Here's my radvd.conf
interface enp0s8
{
AdvSendAdvert on;
AdvManagedFlag off;
AdvOtherConfigFlag on;
prefix ::/64
{
AdvOnLink on;
AdvAutonomous on;
AdvRouterAddr on;
DeprecatePrefix on;
};
};
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.
|
I'm also interested in this. I noticed this dynamic after my network prefix changed. Clients continued to use addresses that should have been deprecated until the valid lifetime was exceeded. |
Any news? |
2 tasks
any updates? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hello,
This issue is a continuation of the second part of the discussion we made in issue #36. And issue #39 is related
Currently, radvd is able to be notified of an address prefix being added or removed from an interface, but I'm still interested that its clients receive a RA to deprecate the prefix being removed from the interface, which radvd doesn't do.
Here's my radvd.conf
The text was updated successfully, but these errors were encountered: