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
Date: Mon, 24 Jun 2002 10:48:15 -0700 [thread overview]
Message-ID: <3D175B5F.5050403@candelatech.com> (raw)
In-Reply-To: Pine.GSO.4.30.0206240922230.12806-100000@shell.cyberus.ca
jamal wrote:
> I tried to explain to you in private mail:
> Both 10.1.1.4 and 10.1.1.5 are recognized to be local addresses
> by the IP stack. It is legit that the stack limits the scope
> to just that i.e _local_
> The only way to do what you want to do is bypass the IP stack.
> Use packet socket to write your test app.
> (which actually probably defetas the whole purpose of what you may
> be trying to do -- HA).
It would not defeat the purpose of detecting at least one bad network
link of the two.
I wonder if a ping -I eth1 255.255.255.255 would accomplish the
goal as well?
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?
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
next prev parent reply other threads:[~2002-06-24 17:48 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 [this message]
2002-06-24 18:59 ` jamal
2002-06-24 19:27 ` Ben Greear
2002-08-28 6:25 ` IP stack question (how to force pkts to not route locally, but go out interfaces regardless of destination) Ben Greear
2002-08-28 12:41 ` 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=3D175B5F.5050403@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 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).