All of lore.kernel.org
 help / color / mirror / Atom feed
From: bert hubert <ahu@ds9a.nl>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Forcing an "external" route
Date: Fri, 07 Dec 2001 22:27:51 +0000	[thread overview]
Message-ID: <marc-lartc-100776410016732@msgid-missing> (raw)
In-Reply-To: <marc-lartc-100776128506945@msgid-missing>

On Fri, Dec 07, 2001 at 03:38:48PM -0600, David Purves wrote:

>     I want to force packets from     eth0 <--> eth1     to take the path 
>     eth0 <--> p0 <--> p1<-->eth1.
> 
> What I have here is an appliance that I want to run some throughput tests.
> 
> The cables are set up eth0 <--> p0 and p1<-->eth1 and work (pings work 
> just fine)....
>     no matter what I try, the kernel is too smart for me  :-) , and it 
> routes internally (inside the linux box) instead of entering the outside 
> world.

I don't think that this is possible purely with iproute2. You will probably
need at least one extra machine to perform NAT.

Perhaps you can get away with UML (usermodelinux).

Regards,

bert

-- 
http://www.PowerDNS.com          Versatile DNS Software & Services
Trilab                                 The Technology People
Netherlabs BV / Rent-a-Nerd.nl           - Nerd Available -
'SYN! .. SYN|ACK! .. ACK!' - the mating call of the internet

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

  reply	other threads:[~2001-12-07 22:27 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-12-07 21:38 [LARTC] Forcing an "external" route David Purves
2001-12-07 22:27 ` bert hubert [this message]
2001-12-07 22:38 ` bert hubert
2001-12-07 22:46 ` Greg Scott

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-100776410016732@msgid-missing \
    --to=ahu@ds9a.nl \
    --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 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.