From: David Newall <davidn@davidnewall.com>
To: Lorenzo Colitti <lorenzo@google.com>
Cc: "netdev@vger.kernel.org" <netdev@vger.kernel.org>,
Hannes Frederic Sowa <hannes@stressinduktion.org>,
David Miller <davem@davemloft.net>, JP Abgrall <jpa@google.com>
Subject: Re: [RFC net-next 0/4] Support UID range routing.
Date: Wed, 30 Apr 2014 17:22:51 +0930 [thread overview]
Message-ID: <5360ABD3.2020506@davidnewall.com> (raw)
In-Reply-To: <CAKD1Yr2J-UgU+Ycu4pf3L51-1tN1fnxQxDo8fLj+9yb4jQuGZg@mail.gmail.com>
On 30/04/14 14:06, Lorenzo Colitti wrote:
> The use of NAT [...] makes it impossible for the app to know its
> real IP address and port
The original address *is* the real address. NAT breaks IP's design and
is a very mixed blessing. NAT isn't needed nor used with IPv6, and
being in IPv4's twilight years, an argument predicated on NAT is not
very convincing.
I feel that describing the patch as routing is misleading, as it
performs only outbound link selection. It fosters an expectation of
bi-directionality, and that is not the case. It will often result in
asymmetric routes.
Is it possible you are trying to solve a problem which has already been
solved, for example by IGP?
next prev parent reply other threads:[~2014-04-30 7:52 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-26 4:48 [RFC net-next 0/4] Support UID range routing Lorenzo Colitti
2014-04-26 4:48 ` [RFC net-next 1/4] net: ipv6: Introduce flowi6_init_output Lorenzo Colitti
2014-04-26 5:56 ` Julian Anastasov
2014-04-27 4:03 ` Lorenzo Colitti
2014-04-28 7:07 ` Julian Anastasov
2014-04-26 4:48 ` [RFC net-next 2/4] net: core: Add a UID range to fib rules Lorenzo Colitti
2014-04-26 4:48 ` [RFC net-next 3/4] net: core: Add the UID to flowi[46]_init_output Lorenzo Colitti
2014-04-26 4:48 ` [RFC net-next 4/4] net: core: Add a RTA_UID attribute to routes Lorenzo Colitti
2014-04-26 13:14 ` [RFC net-next 0/4] Support UID range routing David Newall
2014-04-28 14:38 ` Lorenzo Colitti
[not found] ` <20140428.125807.409036177577836732.davem@davemloft.net>
2014-04-28 19:01 ` Lorenzo Colitti
2014-05-02 19:15 ` Lorenzo Colitti
2014-05-02 19:24 ` David Miller
2014-05-07 3:59 ` Lorenzo Colitti
2014-05-07 9:24 ` Hannes Frederic Sowa
2014-05-07 10:58 ` Lorenzo Colitti
2014-05-11 21:45 ` Hannes Frederic Sowa
2014-05-12 20:25 ` Lorenzo Colitti
2014-04-30 4:36 ` Lorenzo Colitti
2014-04-30 7:52 ` David Newall [this message]
2014-04-30 8:04 ` Lorenzo Colitti
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=5360ABD3.2020506@davidnewall.com \
--to=davidn@davidnewall.com \
--cc=davem@davemloft.net \
--cc=hannes@stressinduktion.org \
--cc=jpa@google.com \
--cc=lorenzo@google.com \
--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).