From: Mauro Condarelli <mc5686@mclink.it>
To: bridge@lists.linux-foundation.org
Subject: [Bridge] bridging problem
Date: Sun, 27 Mar 2011 15:23:54 +0200 [thread overview]
Message-ID: <4D8F3A6A.2080103@mclink.it> (raw)
Hi,
I have a small home-office network built like this:
Internet
|
Firewall(192.169.1.254) GREEN ---+-----------+----------+-----
(192.168.56.254) | | |
DMZ (192.168.1.5) PC1 PC2
| Server
WebServer (192.168.2.254)
WLAN
|
+-----------+----------+-----
| | |
PCa PCb PCc
Firewall is DHCP and DNS server for everyone else.
Firewall is default gateway for everybody.
This arrangement works but requires a static route on firewall and, for
machines on WLAN to talk with wired ones (and vice versa) requires going
to firewall and back.
Is there some way to bridge together the two LANs (GREEN and WLAN) so
they can act as a single subnet (192.168.1.0/24)?
I tried some configurations, but they simply didn't work and I know too
little about bridging to troubleshot them.
Can someone help me, please?
Mauro
next reply other threads:[~2011-03-27 13:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-27 13:23 Mauro Condarelli [this message]
2011-03-27 15:11 ` [Bridge] bridging problem Nicolas de Pesloüan
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=4D8F3A6A.2080103@mclink.it \
--to=mc5686@mclink.it \
--cc=bridge@lists.linux-foundation.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.