mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Paul Jakma <paul@clubi.ie>
To: "Luesley, William" <william.luesley@amsjv.com>
Cc: "'linux-kernel@vger.kernel.org'" <linux-kernel@vger.kernel.org>
Subject: Re: Network routing issue
Date: Tue, 10 Aug 2004 19:46:48 +0100 (IST)	[thread overview]
Message-ID: <Pine.LNX.4.60.0408101944200.2622@fogarty.jakma.org> (raw)
In-Reply-To: <22CE8E75BE6AD3119A9800508B0FF7E9030BADD0@nmex02.nm.dsx.bae.co.uk>

On Tue, 10 Aug 2004, Luesley, William wrote:

> In order to help testing, I have been asked to place a third machine between
> these two which will be capable of intercepting and modifying any messages.

> My initial plan was to have a device which could mimic both ends of the
> connection (as I already have code to do this); with each connection being
> on a separate NIC, leading to a setup as shown below:
>
>          A ------------ C  C  ---------- B
> 192.168.1.1    192.168.1.2  192.168.1.1   192.168.1.2
>                    (eth0)  (eth1)

> Can I use IP Tables, how?
>
> Or, am I on totally the wrong track?

You're on the wrong track. C doesnt even need IP addresses, two 
choices:

- C as bridge and use ebtables (C doesnt even need addresses 
theoretically)

- C as router, use iptables. C needs one or more addresses which must 
be different.

regards,
-- 
Paul Jakma	paul@clubi.ie	paul@jakma.org	Key ID: 64A2FF6A
Fortune:
Violence is a sword that has no handle -- you have to hold the blade.

  reply	other threads:[~2004-08-10 18:57 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-10 17:45 Luesley, William
2004-08-10 18:46 ` Paul Jakma [this message]
2004-08-10 18:54 ` Richard B. Johnson
2004-08-10 19:15 Luesley, William
2004-08-10 19:48 Luesley, William
2004-08-10 21:54 ` David Greaves
2004-08-10 23:14 ` Paul Jakma

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=Pine.LNX.4.60.0408101944200.2622@fogarty.jakma.org \
    --to=paul@clubi.ie \
    --cc=linux-kernel@vger.kernel.org \
    --cc=william.luesley@amsjv.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

all inboxes | Powered by JetHome®