From: "Jan Kundrát" <jan.kundrat@fzu.cz>
To: Felipe Alfaro Solana <lkml@mac.com>
Cc: Grzegorz Milos <gm281@hermes.cam.ac.uk>, xen-devel@lists.sourceforge.net
Subject: Re: Bridging firewall?
Date: Fri, 21 Jan 2005 16:02:22 +0100 [thread overview]
Message-ID: <41F1197E.7020308@fzu.cz> (raw)
In-Reply-To: <55EB5E24-6BB6-11D9-86B4-000D9352858E@mac.com>
Felipe Alfaro Solana wrote:
> How? I thought all network traffic must pass through domain0 in first
> instance. How do you give a domainU instance direct access to a network
> interface, like eth1? I'm currently using a bridge, xen-br0, attached to
> eth1, and domainU attached to xen-br0. How can I configure domainU to
> attach to eth1 directly?
You have to give domU permission to access your phisical NIC device.
It's described somewhere in the manual, iirc.
-jkt
--
cd /local/pub && more beer > /dev/mouth
-------------------------------------------------------
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-21 15:02 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 [this message]
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=41F1197E.7020308@fzu.cz \
--to=jan.kundrat@fzu.cz \
--cc=gm281@hermes.cam.ac.uk \
--cc=lkml@mac.com \
--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.