All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jim Laurino <nfcan.x.jimlaur@dfgh.net>
To: netfilter@lists.netfilter.org
Subject: Re: non-masquerade routing (nfcan: addressed to exclusive sender for this address)
Date: Sat, 4 Feb 2006 11:26:03 -0500	[thread overview]
Message-ID: <20060204162603.GA26094@salty> (raw)
In-Reply-To: <af2c99310602040722g71cc5491i51fa411e47bcd02f@mail.gmail.com> (from +nfcan+jimlaur+fb897d0c5f.bangular#gmail.com@spamgourmet.com on Sat, Feb 04, 2006 at 10:22:33 -0500)

On 2006.02.04 10:22, Chris Baechle - bangular@gmail.com wrote:
> I'm trying to setup a linux router for routing of public addresses
> (non-nat / non-masquerade). I really don't know what this is called
> (so googling hasn't helped much).
>

Um, perhaps this is called 'routing'.

Once the route is set up,
and routing is turned on - something like:

echo 1 > /proc/sys/net/ipv4/ip_forward

all the *firewall* needs is permission to forward the packets
from one network/interface to the other.

> Example:
> 
> [Box A] ( 72.14.207.2)  <--->  (72.14.207.1) [Linux Router]
> (66.94.234.1)  <---> (66.94.234.2) [Box B]
> 
> Box A eth0 = 72.14.207.2
> Linux Router eth0 = 72.14.207.1
> Linux Router eth1 = 66.94.234.1
> Box B eth0 = 66.94.234.2
> 
> I want to be able to connect from [Box A] to [Box B] and Box B web
> server logs to show Box A's ip address (no natting); and if I do a
> traceroute have the linux router show up as a hop (no bridging).
> 
> So is this something for iptables or am I barking up the wrong tree? I
> checked out regular old route and iproute2 and didn't get much
> further. Any point in the right general direction would be greatly
> appreciated.
> 
> 
> 
>

-- 
Jim Laurino
nfcan.x.jimlaur@dfgh.net
Please reply to the list.
Only mail from the listserver reaches this address.


  reply	other threads:[~2006-02-04 16:26 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-04 15:22 non-masquerade routing Chris Baechle
2006-02-04 16:26 ` Jim Laurino [this message]
2006-02-04 18:11   ` non-masquerade routing (nfcan: addressed to exclusive sender for this address) Chris Baechle

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=20060204162603.GA26094@salty \
    --to=nfcan.x.jimlaur@dfgh.net \
    --cc=netfilter@lists.netfilter.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.