[Xen-users] non-standard bridging

["Mike Schiller" <mdschiller@xxxxxxxxx>]

I'm running Fedora 6 (64) with the xen kernel as domain 0, and Windows
XP (32) as the in the (hardware) virtual machine. In addition, I'm
running this on a notebook computer. Consequently, eth0 is rarely if
ever connected to a network, and the drivers for rausb0 (my wireless
card) are not compatible with xen's method of bridging.

The default method of bridging is:

dom0: fake eth0 -> vif0.0  -+
                                      |
                                   bridge -> real eth0 -> The network
                                      |
domU: fake eth0 -> vifU.0 -+


I'd instead like to setup one of the following methods...

alternate method a:

dom0: real rausb0 -> The Network
                  |
               bridge
                  |
domU: fake eth0

I have no idea how to go about alternate method a. Does anyone have
any insight as to how to do this?

alternate method b:

dom0: real rausb0 -> The Network
                     |
             ipv4 forwarding
                     |
fake eth0 -> vif0.0 -----------------+
                                           |
                                        bridge -> real eth0 -> NO
Network connection
                                           |
domU: fake eth0 -> vifU.0 ------+

I've tried method b by doing the following:
                configure rausb0 as ip 192.168.1.16, nm 255.255.255.0,
                                             gw 192.168.1.1, dns 192.168.1.1
                configure Dom0 fake eth0 as ip 192.168.2.1, nm 255.255.255.0
                                             gw not set , dns not set
                configure DomU fake eth0 as ip 192.168.2.2, nm 255.255.255.0
                                             gw 192.168.2.1, dns 192.168.1.1
I then did...
echo 1 > /proc/sys/net/ipv4/ip_forward

... thinking that this would set up forwarding between my 192.168.1.*
and 192.168.2.* subnet on the laptop, but that didn't quite cut it.
The virtualized Windows OS can ping 192.168.2.1, and 192.168.1.16, but
not or 192.168.1.1 or anything else on the 192.168.1.* subnet. I also
tried setting the VM's gateway to 192.168.1.16, and separately,
shutting off iptables. Neither helped. I think I'm close with this
method, but missing something obvious. Can anyone point me in the
right direction here?

Much thanks in advance,
Mike

_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users