From: Nicholas Lee <nic-lists@plumtree.co.nz>
To: xen-devel@lists.sourceforge.net
Subject: Bridging firewall?
Date: Fri, 21 Jan 2005 23:49:19 +1300 [thread overview]
Message-ID: <20050121104919.GF27277@stateless> (raw)
Is it possible with Xen to construct something like the following scenario.
Free/NetBSD (*) domU server running pf or Linux/iptables, acting as a
routing or bridging firewall for all the other domU guests? Further more
create virtual DMZ and internal services.
You'd probably keep the dom0 instance otherside this setup, with its own
filtering arrangement.
For instance, you have a subnet 192.168.1.0/24. Put the dom0 on 192.168.1.254.
Have the firewall router domU running on 192.168.1.1 and acting as the
gateway for all the other machines on the subnet.
(*) This is my dream, using pf for security and debian for serving the
applications. ;)
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 reply other threads:[~2005-01-21 10:49 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-21 10:49 Nicholas Lee [this message]
2005-01-21 13:55 ` Bridging firewall? 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
-- 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=20050121104919.GF27277@stateless \
--to=nic-lists@plumtree.co.nz \
--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.