Linux Advanced Routing and Traffic Control list
 help / color / mirror / Atom feed
From: "Finney, Steve" <Steve.Finney@SpirentCom.COM>
To: lartc@vger.kernel.org
Subject: [LARTC] How to _not_ use loopback...
Date: Mon, 20 Jan 2003 19:55:29 +0000	[thread overview]
Message-ID: <marc-lartc-104309247822850@msgid-missing> (raw)

I'm not sure if this is the same thing as what the original poster was asking, 
but I have a similar issue: there are  two ethernet interfaces on a box, and
for HW diagnostic purposes I want to send IP traffic _over the wire_ from one to 
the other. In the
normal case, this would be handled via the loopback device and would not go over
the wire (since the internal routing code is smart enough, I believe, to check all
local interface addresses). I expect there is a way to do this with policy routing,
and I'll be looking into it,
but if someone already knows some answers, please share them.

Thanks,

sf

From: Eric Leblond <eric@regit.org>
To: LARTC <LARTC@mailman.ds9a.nl>
Date: 20 Jan 2003 08:58:54 +0100

Le dim 19/01/2003 à 17:35, Bernd Rudack a écrit :
> Hi there,
> in a specal case I want to send IP packets from one IP address to another IP 
> address on the same multihomed linux box. The problem is, that the packets 
> should leave the box by passing one ethernet interface, go through a 
> hub/switch and get back into the box via the second interface.
> Well, this sounds crazy.
> Anyway, does anyone know a solution?

Use Linux ;-) 
if the box has the IPs, it kows it and route it internally.

_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/

                 reply	other threads:[~2003-01-20 19:55 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=marc-lartc-104309247822850@msgid-missing \
    --to=steve.finney@spirentcom.com \
    --cc=lartc@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