From: Rick Jones <rick.jones2@hp.com>
To: bsilva <bsilva@sonic.net>
Cc: "Kārlis Repsons" <karlis.repsons@gmail.com>,
'netfilter' <netfilter@vger.kernel.org>
Subject: Re: Forward packets from one interface to another?
Date: Tue, 03 Feb 2009 13:37:49 -0800 [thread overview]
Message-ID: <4988B92D.8040201@hp.com> (raw)
In-Reply-To: <Pine.LNX.4.58.0902031205200.13208@bolt.sonic.net>
bsilva wrote:
> You can use either routing/forwarding or bridging for this problem,
> however, bridging is simpler in many ways. If you use bridging, there is
> are fewer impacts on the design of the rest of your network. If you use
> routing, then the router that connects the PC with two interfaces to the
> Internet needs to know about the network on the other side of the PC
> (in a small network this can be done by adding a static route).
>
> So, in this example:
>
> ----------- ----------- -----------
> | Router/ | | PC | | PC |
> | Firewall|.1 Net A .10| with 2 |.10 Net B .11| with 1 |
> | to |----------------| NICs |------------------| NIC |
> | Internet| 192.168.1.0 ----------- 192.168.2.0 -----------
> -----------
> Each network is /24 (netmask of 255.255.255.0)
>
If instead, you further subnettted 192.168.1 with a /25 on the PCs (but still a
/24 on the router), the Router/Firewall wouldn't have to know about the other
subnet. It could just blythly ass-u-me that the end-PC was on the same network
segment as the middle PC. So long as the middle PC was configured with a static,
public ARP entry for the IP of the end PC, and had ip_forwarding enabled, it
would "front" for the end PC.
rickjones
next prev parent reply other threads:[~2009-02-03 21:37 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-03 17:53 Forward packets from one interface to another? Kārlis Repsons
2009-02-03 19:21 ` Gilad Benjamini
2009-02-03 19:40 ` Kārlis Repsons
2009-02-03 19:49 ` Gilad Benjamini
2009-02-03 20:04 ` Kārlis Repsons
2009-02-03 20:24 ` bsilva
2009-02-03 21:37 ` Rick Jones [this message]
2009-02-03 21:48 ` bsilva
2009-02-03 22:13 ` Mike Wright
2009-02-03 22:24 ` Rick Jones
2009-02-04 11:18 ` Pascal Hambourg
2009-02-03 21:32 ` Gilad Benjamini
2009-02-03 20:45 ` Rick Jones
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=4988B92D.8040201@hp.com \
--to=rick.jones2@hp.com \
--cc=bsilva@sonic.net \
--cc=karlis.repsons@gmail.com \
--cc=netfilter@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.