From: Innocenti Maresin <qq@inCTV.ru>
To: LKML <linux-kernel@vger.kernel.org>
Subject: 2.4 - net/ipv4/route.c/ip_route_output_slow()
Date: Sun, 13 Aug 2006 15:17:09 +0000 [thread overview]
Message-ID: <44DF4275.8A68AAC@inCTV.ru> (raw)
In-Reply-To: LKML-nat-0.qq@inCTV.ru
Ok, my dear kernel coding gurus.
You have almost nothing to say about "internal IP addresses" and "connect() failures".
Let me swicth the question's language :)
Please, help with the function ip_route_output_slow() in net/ipv4/route.c.
There is such code as:
if (res.type == RTN_NAT)
goto e_inval;
In late 2.4 it is line 1922 (2.6 is irrelevant because of elimination of RTN_NAT).
I realize that this condition means, at least, an explicit ban
on all attempts to use RTN_NATted destination addresses in connect(),
so the kernel fails before the process (or the transport level) attempts to send any packet.
Please, tell me, what value should return this function by design
and what is the difference between it and a similar situation in ip_route_input_slow()
where fib_rules_map_destination() is called instead of just failing.
For what reasons (religious, I think) locally generated packets
may not be RTN_NATted in a manner similar to the routing of forwarding traffic?
Thank you for your attention.
--
qq~~~~\
/ /\ \
\ /_/ /
\____/
next prev parent reply other threads:[~2006-08-13 16:18 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-12 15:09 Q: remapping IP addresses for inbound and outbound traffic Innocenti Maresin
2006-08-12 15:42 ` R: " Giampaolo Tomassoni
2006-08-13 6:02 ` Innocenti Maresin
2006-08-12 17:22 ` Q: " Jan Engelhardt
2006-08-13 15:17 ` Innocenti Maresin [this message]
2006-08-14 0:00 ` 2.4 - net/ipv4/route.c/ip_route_output_slow() David Miller
2006-08-29 8:07 ` Q: remapping IP addresses for inbound and outbound traffic 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=44DF4275.8A68AAC@inCTV.ru \
--to=qq@inctv.ru \
--cc=linux-kernel@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