From: Ben Greear <greearb@candelatech.com>
To: jamal <hadi@cyberus.ca>
Cc: "Bloch, Jack" <Jack.Bloch@icn.siemens.com>,
"'netdev@oss.sgi.com'" <netdev@oss.sgi.com>
Subject: Re: IP stack question (how to force pkts to not route locally, but go out interfaces regardless of destination)
Date: Tue, 27 Aug 2002 23:25:58 -0700 [thread overview]
Message-ID: <3D6C6CF6.9040002@candelatech.com> (raw)
In-Reply-To: Pine.GSO.4.30.0206241450330.13908-100000@shell.cyberus.ca
jamal wrote:
> Ben Wrote:
>>I would actually like to be able to force a machine to not do local
>>routing as well, and force packets out over an interface even if
>>the destination is a local IP, using source-based-routing,
>>or something similar. There is no way to do this currently?
>>
>
>
> Try that SO_DONTROUTE and see if solves your problem; you probably have to
> bind the socket to a specific device as well;
> For all that trouble, i would suggest you may just as well write a sock
> packet based app.
I am back to trying to figure out how to make this work. I'm tried source
based routing, and it does not work (it routes internally).
I read the help on SO_DONTROUTE, but it seems to make the kernel not able
to send to a router. I would like to be able to route, ie port a -> router -> port b
I already bind to a particular port and IP, and use policy based routing
(source based routing) to make sure the packet is sent out the correct
local interface.
I just need to find the routing logic that notices the destination IP is local
and tell it to quit looking (probably for a particular socket, as I can
see how this could break applications who didn't expect it)
I dug through the code once before looking for this, and didn't find
what I needed. Can anyone suggest the right files and/or methods to
look in?
Thanks,
Ben
>
> cheers,
> jamal
>
--
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
next prev parent reply other threads:[~2002-08-28 6:25 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-24 11:39 IP stack question Bloch, Jack
2002-06-24 13:34 ` jamal
2002-06-24 17:48 ` Ben Greear
2002-06-24 18:59 ` jamal
2002-06-24 19:27 ` Ben Greear
2002-08-28 6:25 ` Ben Greear [this message]
2002-08-28 12:41 ` IP stack question (how to force pkts to not route locally, but go out interfaces regardless of destination) James R. Leu
2002-08-29 10:17 ` A question on RTT estimation of SACKed packet Xiaoliang (David) Wei
2002-08-29 19:01 ` kuznet
2002-08-29 22:19 ` Xiaoliang (David) Wei
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=3D6C6CF6.9040002@candelatech.com \
--to=greearb@candelatech.com \
--cc=Jack.Bloch@icn.siemens.com \
--cc=hadi@cyberus.ca \
--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 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.