From: Grant Taylor <gtaylor@riverviewtech.net>
To: Mail List - Netfilter <netfilter@vger.kernel.org>
Subject: Re: Forwarding packets received on bridged interfaces -regarding
Date: Wed, 28 May 2008 22:07:30 -0500 [thread overview]
Message-ID: <483E1DF2.3080304@riverviewtech.net> (raw)
In-Reply-To: <69fec4520805281536t15dd5e5dq289799693263371b@mail.gmail.com>
On 05/28/08 17:36, Knight Tiger wrote:
> I have a Linux box with two interfaces, eth0 and eth1. eth1 is a
> wireless interface with connects to a network and receives a DHCP
> address. eth0 connects to a AP (with a cross over cable) and provides
> Internet connection to a bunch of clients. The setup looks like this
> AP1 <--> eth0 eth1 <---> AP2<---> DHCP server.
Let's redraw this up a little bit.
+--------------+
| Bridge |
("Net 0") AP0---+ eth0 eth1 +---AP1 ("Net 1") DHCP server
+--------------+
Is a client on "Net 0" suppose to have an IP in the same subnet as
clients on "Net 1"? Or is the "Bridge" system going to be routing for
all the clients on "Net 0" and hiding them as one IP to "Net 1"?
I ask this because you are starting to sound like the "Bridge" system is
suppose to act like a SOHO router like you would use on your DSL / cable
modem to connect your home LAN to your internet connection. However
your original question implied that you wanted "Net 0" and "Net 1" to be
joined together as one big network where everything on both sides could
see everything else.
<snip>
Please clarify the above before going further.
Grant. . . .
next prev parent reply other threads:[~2008-05-29 3:07 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-28 22:36 Forwarding packets received on bridged interfaces -regarding Knight Tiger
2008-05-29 3:07 ` Grant Taylor [this message]
2008-05-29 4:55 ` Knight Tiger
2008-05-29 5:17 ` Grant Taylor
2008-05-30 22:32 ` Knight Tiger
2008-05-30 22:57 ` Grant Taylor
2008-06-04 18:22 ` Knight Tiger
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=483E1DF2.3080304@riverviewtech.net \
--to=gtaylor@riverviewtech.net \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox