Hello! > First part (prefixlist) seems ok to me. The same is here. It looks good. > Second part does not. I do not like the latest version a lot. :-) Actually, previous one was quite acceptable, but I think Yoshfuji's suggestion is so good that it makes lots of sense to complete it. I could make this in IPv4 part, actually, I started to make it as demo for Krishna, but two questions remained unaswered: 1. How to allocate new attributes? It is bad just to add them to existing IFLA_* ones or override them. I would suggest to create new attribute IFLA_PROTINFO and to embed new protocol dependant attributes as subattributes a la RTA_METRICS. Another suggestions? 2. IFLA_INET6_CONF (and IFLA_INET_CONF). How to encode the values? Array of int's is simple, compact and looks good. But I have some problem with it. What if one day we want to implement changing the values? It will be nasty. To forget about such perspective? Or to leave it to use for "atomic" load of all the parameters? Alexey - : send the line "unsubscribe linux-net" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
