From: Steffen Klassert <steffen.klassert@secunet.com>
To: Herbert Xu <herbert@gondor.apana.org.au>
Cc: "David S. Miller" <davem@davemloft.net>, netdev@vger.kernel.org
Subject: Re: Namespaces and inetpeer
Date: Mon, 12 Mar 2012 09:57:56 +0100 [thread overview]
Message-ID: <20120312085756.GL15404@secunet.com> (raw)
In-Reply-To: <20120310132529.GA3631@gondor.apana.org.au>
On Sun, Mar 11, 2012 at 12:25:29AM +1100, Herbert Xu wrote:
> Hi:
>
> While looking through the inetpeer code I noticed that there is
> no namespace support at all. This means that metric and other
> information will be leaking across namespaces. As IP addresses
> are meant to be independent between them, this is not a good thing.
>
Actually, it would be nice if we could have an inetpeer base per
fib table. This would imply namespace awareness and it would
handle the problem when we have mulitiple routes (with different
metrics etc.) to the same ip address on policy routing.
next prev parent reply other threads:[~2012-03-12 8:57 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-10 13:25 Namespaces and inetpeer Herbert Xu
2012-03-12 8:57 ` Steffen Klassert [this message]
2012-03-12 9:35 ` David Miller
2012-03-12 9:58 ` Steffen Klassert
2012-03-12 10:05 ` David Miller
2012-03-12 12:11 ` Herbert Xu
2012-03-13 9:41 ` Steffen Klassert
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=20120312085756.GL15404@secunet.com \
--to=steffen.klassert@secunet.com \
--cc=davem@davemloft.net \
--cc=herbert@gondor.apana.org.au \
--cc=netdev@vger.kernel.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).