Thank you for your reply.

I read somewhere that the xen routed configuration is far more complicated than the xen bridged configuration. I could be wrong.

I would like to keep the network configuration and firewalling simple at this time.I noticed that the network configuration that shipped with XenEnterprise 3.2.0 is also of a bridged type.

On 7/30/07, Tom Eastep < teastep@shorewall.net> wrote:
On Mon, 2007-07-30 at 17:17 +0800, Teo En Ming wrote:
> Hi
> I have a 64-bit server running RHEL 5 x86-84 Xen Virtualization. There
> are 6 NICs in this Xen Host.
> The interface names in Dom 0 are:
> eth0 - xenbr0 - reserved for Dom 0 Host Management Administration
> eth1 - xenbr1 - reserved for Virtual Machine #1
> eth2 - xenbr2 - reserved for Virtual Machine #2
> eth3 - xenbr3 - reserved for Virtual Machine #3
> eth4 - xenbr4 - reserved for Virtual Machine #4
> eth5 - xenbr5 - reserved for Virtual Machine #5
> How should I configure shorewall in this case of multiple nics, each
> nic being dedicated to a Virtual Machine?

I recommend that you use a routed Xen configuration rather than a
bridged configuration. Then follow (more or less)

Tom Eastep    \ Nothing is foolproof to a sufficiently talented fool
Shoreline,     \ http://shorewall.net
Washington USA  \ teastep@shorewall.net
PGP Public Key   \ https://lists.shorewall.net/teastep.pgp.key

This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >>  http://get.splunk.com/
Shorewall-users mailing list