On Fri, Feb 8, 2013 at 9:04 PM, Jan Engelhardt <jengelh@xxxxxxx> wrote: > On Friday 2013-02-08 11:48, Prashant Batra wrote: > >>I have a case wherein I have a route to a network connected to my >>linux machine via an interface, which I added like- >> >>route add -inet6 9aa::/16 gw 2001:db8:0:242::2 dev eth0 > > Forget net-tools already. It is not maintained. > There is no issue with iproute. > >>like this I get 10k routes >>#cat /proc/net/ipv6_route | wc -l >>10015 > > It is correct - it dumps routes (for some definition of "route"), in > particular all FIB entries. You will find the same for IPv4 in > /proc/net/rt_cache on kernels where the cache has not already been > removed. That said /proc/net only shows table 254, so the whole procfs > business is pretty useless. > So, if I understand correctly, the /proc/net/rt_cache and /proc/net/ipv6_route display the routing cache for v4 and v6 respectively, which the kernel maintains. And, in case my server is trying to send packets to millions of addresses, kernel will cache the routes for them, until "/proc/sys/net/ipv6/route/max_size" is reached after which it will flush some old entries to make room for new ones. So, any advice onto how the kernel configs specially under /proc/sys/net/ipv6/route/* should be controlled to get best performance. > Just use iproute2, really. -- Thanks -- To unsubscribe from this list: send the line "unsubscribe linux-newbie" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.linux-learn.org/faqs
