On (04/24/09 09:22), Peter Memishian wrote: > > > Overloading IFF_UP seems to create a lot of confusion here. > > I agree it's confusing. However, it is a flag that applications account > for and even have been known to get right :-) If we go invent some new
I think the right answer here is to have libipadm interfaces that do all the mangling needed to figure out the address and interface flags, and relieve apps like quagga from this burden. As Erik pointed out, as long as the libipadm interface return enums that match rfc4293 as closely as we can, the implementation itself can be changed as/when we are ready. > > went up or down. Shouldn't the model be IFA_INVALID (for the address), > > IFF_UP (for the interface), and IFA_DISABLE (for an address that has > > been administratively disabled- though I still don't see why a simple > > address-delete is not sufficient). > > If I'm an admin and I've configured an address to my liking (flags, > zoneid, whatever), why should I have to delete it and then recreate it > later just because I want the system to stop using it for a few minutes? What if you could create/save persistent configuration for your address and have that recovered as the address appears? Would you still need this up/down flag? --Sowmini _______________________________________________ networking-discuss mailing list [email protected]
