This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
Home Products Support Community News


Re: [Xen-devel] Re: nfsroot and brige

> So, tell me: I have a dom0 with eth0 at, eth1 at
>, and I want to bridge a domU at to the dom0 such
> that domU can go out over my 802.11 network to the world. How will my
> xen-br0 and vif1.0 configuration look? I never got this to work correctly.
> What I really want is domU to DHCP to, and I never saw that
> work correctly either. But, if the bridge is really a bridge, that should
> "just happen" (or did on real hardware bridges).

That is a situation where you will want to use routing, not bridging. The 
reason is that you would need to have domU on the same network as eth0 in 
dom0 (so or something like that) in order to use the bridge. 
But probably you:
1) cannot request another IP on this network
2) don't want to give direct access to your domU from the outside world.

Instead use routing and iptables (masquerade) as follows:
dom0 eth0 stays with
dom0 eth1 stays with
dom0 acts as a NAT for unpriviledged domains

domU eth0 gets an IP on 192.168.0.* subnet (I am not quite sure how would be 
able to get if from using DHCP. Dynamic IPs would be also cause 
some problems with setting up the routing table in dom0).
Routing in domU has as its default gateway.

I've tested it once - it worked with IP addresses statically assigned to domUs 
(remember to echo 1 >/proc/sys/net/ipv4/ip_forward, took me some time to work 
out why dom0 doesn't route anything :) ).


Quidquid latine dictum sit, altum viditur --- Anon

The SF.Net email is sponsored by: Beat the post-holiday blues
Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek.
It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt
Xen-devel mailing list