From: Jan Engelhardt <jengelh@inai.de>
To: Prashant Batra <prashant0100@gmail.com>
Cc: linux-newbie@vger.kernel.org, netfilter@vger.kernel.org
Subject: Re: IPv6 routes too much
Date: Fri, 8 Feb 2013 16:34:24 +0100 (CET) [thread overview]
Message-ID: <alpine.LNX.2.01.1302081615450.10125@nerf07.vanv.qr> (raw)
In-Reply-To: <CAG+XuE7FaAwwSq98JTSr3SOxSP2rN1hxFYQ7O=0L_3E=9kVreg@mail.gmail.com>
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.
Just use iproute2, really.
--
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs
next prev parent reply other threads:[~2013-02-08 15:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-08 10:48 IPv6 routes too much Prashant Batra
2013-02-08 15:34 ` Jan Engelhardt [this message]
2013-02-08 17:38 ` Prashant Batra
[not found] ` <CAG+XuE5g9jJTP4uu5ymQfzvx-O6U9SfK85XGoK+H7yqtVA6A0A@mail.gmail.com>
2013-02-09 3:31 ` Jan Engelhardt
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=alpine.LNX.2.01.1302081615450.10125@nerf07.vanv.qr \
--to=jengelh@inai.de \
--cc=linux-newbie@vger.kernel.org \
--cc=netfilter@vger.kernel.org \
--cc=prashant0100@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.