From: Ben Greear <greearb@candelatech.com>
To: "netdev@oss.sgi.com" <netdev@oss.sgi.com>
Subject: more on forcing traffic to route to local interface though another interface.
Date: Thu, 12 Sep 2002 21:31:45 -0700 [thread overview]
Message-ID: <3D816A31.3050401@candelatech.com> (raw)
I've been adding printk's to the linux routing code to try to figure
out how things are working...
It appears that at least one of the reasons why what I want to do will
not work is that this code in route.c:
/*
* Now we are ready to route packet.
*/
if ((err = fib_lookup(&key, &res)) != 0) {
if (!IN_DEV_FORWARD(in_dev))
goto e_inval;
goto no_route;
}
returns a 'res' that has the res.type == RTN_LOCAL.
So, does anyone know what part of the code populates
the fib tables? I need to convince that code to never (or rarely)
use any RTN_LOCAL type, at least for certain interfaces and/or sockets.
Other ideas are welcome, of course!
Ben
--
Ben Greear <greearb@candelatech.com> <Ben_Greear AT excite.com>
President of Candela Technologies Inc http://www.candelatech.com
ScryMUD: http://scry.wanfear.com http://scry.wanfear.com/~greear
reply other threads:[~2002-09-13 4:31 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=3D816A31.3050401@candelatech.com \
--to=greearb@candelatech.com \
--cc=netdev@oss.sgi.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 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).