[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]
Re: PATCH to only announce RTM_NEWADDR once IPv6 DAD completes
On 15/05/2013 14:15, christos%astron.com@localhost wrote:
In article <b18662cb2f9eb1c8b4ede6b6b31e9235%mail.marples.name@localhost>,
Roy Marples <roy%marples.name@localhost> wrote:
On 15/05/2013 12:07, Greg Troxel wrote:
Basically, I'd like a spec of how to take a stream of NEW/DEL and a
of current addresses and say if the behavior is right. I don't
suggest that you've done anything that breaks what the spec ought
but it feels tricky.
You mean what happens when a conflict is detected?
I'm not sure that generating DELADDR is the right thing to do as it
does exist within the kernel.
Maybe a new message, RTM_DUPADDR? That suffers from the same possible
crash for badly written programs though.
Doesn't the tentative bit get passed in the rtm message? Why not pass
the full information to userland and let it do what it wishes?
As the kernel (currently) doesn't set the tentative bit before sending
RTM_NEWADDR I don't see
how this helps solve the initial issue as I doubt any userland
application currently checks for the tentative flag.
I could be wrong though.
Main Index |
Thread Index |