public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: David Greaves <david@dgreaves.com>
To: "Luesley, William" <william.luesley@amsjv.com>
Cc: "'Paul Jakma'" <paul@clubi.ie>,
	"'linux-kernel@vger.kernel.org'" <linux-kernel@vger.kernel.org>
Subject: Re: Network routing issue
Date: Tue, 10 Aug 2004 22:54:57 +0100	[thread overview]
Message-ID: <41194431.6010300@dgreaves.com> (raw)
In-Reply-To: <22CE8E75BE6AD3119A9800508B0FF7E9030BADD7@nmex02.nm.dsx.bae.co.uk>


>>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.
>>    
>>
>My problem is I need to modify the messages before passing them on.  As far
>as I'm aware, bridges don't do that - but then I'm a newbie when it comes to
>bridging!
>  
>
http://www.spinics.net/lists/netfilter/msg13455.html

http://ebtables.sourceforge.net/documentation.html

I don't know if it will do what you want 'out of the box'

if not then the sensible thing to do would be to route and setup:

          A ------------ C  C  ---------- B
192.168.1.1    192.168.1.2  192.168.2.1   192.168.2.2

and use iptables to do user space packet filtering.

http://www.netfilter.org/documentation/HOWTO//netfilter-hacking-HOWTO-4.html#ss4.7
http://www.lowth.com/howto/iptables-treasures.php

I saw that ebtables can use iptables modules (with some hacking)

David


  reply	other threads:[~2004-08-10 21:54 UTC|newest]

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

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=41194431.6010300@dgreaves.com \
    --to=david@dgreaves.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=paul@clubi.ie \
    --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