From: Nicholas Lee <nic-lists@plumtree.co.nz>
To: Matthieu <matxen@matws.net>
Cc: xen-devel@lists.sourceforge.net
Subject: Re: Bridging firewall?
Date: Wed, 26 Jan 2005 08:42:02 +1300 [thread overview]
Message-ID: <20050125194202.GA10646@stateless> (raw)
In-Reply-To: <095254807073ef9097cb71b1ba4d8116@matws.net>
On Tue, Jan 25, 2005 at 06:27:09PM +0100, Matthieu wrote:
> > So in a sense you've put your virtual servers on the same network as
> > some of your internal machines.
> >
> Yes, that's right but is it a problem ?
No, only if you don't have a physical internal network. Like a machine
in a colo.
> Quite complicated ? it seems that you 're relying on the fact your inbound
> traffic will go to the eth0 trought you're firewall (trough dom1 in fact).
> I'm quite afraid about the fact that some packet cleverly forged can go
> trough dom0 without going trough dom1.
Relying on the way briding works. The internal hosts are on a seperate
bridge from the the external dom0. The domU1 bridge will need to be
tranversed for traffice to go from the external bridge to the internal
bridge.
If it doesn't work like that, then bridging is broken. Think of each
bridge as a switch, with domU1 being a smart switch. Connecting a host
to each switch by adding one of its interfaces to the bridge is like
joining two switch by a crossover cable. If there is no direct cable
between the external and internal bridges, but they have to instead
tranverse the bridging firewall switch then everything is as it should
be.
Nicholas
-------------------------------------------------------
This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting
Tool for open source databases. Create drag-&-drop reports. Save time
by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc.
Download a FREE copy at http://www.intelliview.com/go/osdn_nl
next prev parent reply other threads:[~2005-01-25 19:42 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-21 10:49 Bridging firewall? Nicholas Lee
2005-01-21 13:55 ` Grzegorz Milos
2005-01-21 14:11 ` Felipe Alfaro Solana
2005-01-21 15:02 ` Jan Kundrát
2005-01-21 15:08 ` Jan Kundrát
2005-01-21 15:30 ` Georgios Portokalidis
2005-01-23 23:12 ` Matthieu PATOU
2005-01-24 1:21 ` Nicholas Lee
2005-01-25 17:27 ` Matthieu
2005-01-25 19:42 ` Nicholas Lee [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-01-23 23:15 Ian Pratt
2005-01-26 21:11 ` Matthieu PATOU
2005-01-26 21:56 Ian Pratt
2005-01-26 22:06 ` Matthieu PATOU
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=20050125194202.GA10646@stateless \
--to=nic-lists@plumtree.co.nz \
--cc=matxen@matws.net \
--cc=xen-devel@lists.sourceforge.net \
/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.