OK! I don't need any explanation. So is this behaviour OK or not? (that is, wether my patch makes sense or not :)). Thanks, Gabor Fekete On Sunday 20 November 2005 20.42, feketgai@xxxxxxxx wrote: > > Hi, > > I realized that in route.c the inet6_rtm_new_route() function > the inet6_rtm_to_rtmsg() does not take into account the user > supplied flags. This way it seems to be not possible to set the > RTF_DEFAULT flag of a default route (dest address being "any"). > It is true that the new route will > end up in the default route list anyway but then the > ip6_route_output() function will not call rt6_best_dflt(). > I relaized it when I had to modify the default route selection > algorithm. The kernel rt6_add_dflt_router() function properly > sets the RTF_DEFAULT flag but user space functions cannot > set it using netlink (e.g. iproute does not set it either). > Is it the intended behaviour? If yes, why? > Attached is a one-liner patch that I use now to solve this for me. > It is against an usagi kernel but the issue is the same with stock > 2.6.x kernels. > > Thanks, > Gabor Fekete > - : send the line "unsubscribe linux-net" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
