From mboxrd@z Thu Jan  1 00:00:00 1970
From: David Purves <davidpurves@mindspring.com>
Date: Fri, 07 Dec 2001 21:38:48 +0000
Subject: [LARTC] Forcing an "external" route
Message-Id: <marc-lartc-100776128506945@msgid-missing>
List-Id: <lartc.vger.kernel.org>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
To: lartc@vger.kernel.org

Here is as wacky a situation as you might find...

    Given a linux box with two ethernet cards:
        eth0  at ip 192.168.100
        eth1 at ip 172.16.1.100,
    and an internet "appliance" with two ethernet ports:
        p0 at ip 192.168.1.101
        p1 at ip 172.16.1.1,

    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.

Any ideas?

David Purves


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