All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg Scott <GregScott@InfraSupportEtc.com>
To: lartc@vger.kernel.org
Subject: RE: [LARTC] Forcing an "external" route
Date: Fri, 07 Dec 2001 22:46:00 +0000	[thread overview]
Message-ID: <marc-lartc-100776433517753@msgid-missing> (raw)
In-Reply-To: <marc-lartc-100776128506945@msgid-missing>

What if you used some iptables rules to DENY packets from eth0 with
destination ip address 172.16.1.100?  I'm thinking you might have to put in
the rules in the OUTPUT table and catch them on the way out from
192.168.1.100.  No clue whether or not that will work, but worth a try.

- Greg



-----Original Message-----
From: David Purves [mailto:davidpurves@mindspring.com]
Sent: Friday, December 07, 2001 3:39 PM
To: lartc@mailman.ds9a.nl
Subject: [LARTC] Forcing an "external" route


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/

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

      parent reply	other threads:[~2001-12-07 22:46 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
2001-12-07 22:38 ` bert hubert
2001-12-07 22:46 ` Greg Scott [this message]

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-100776433517753@msgid-missing \
    --to=gregscott@infrasupportetc.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 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.