On Thu, Mar 19, 2009 at 8:05 PM, Fasiha Ashraf <
feehapk@xxxxxxxxxxx> wrote:
> It causes much overhead in case of virtualizing wireless networks thats why!
Ah, wireless :)
It's not simply
overhead, bridging a wireless interface (AFAIK) won't work.
One option is network-route
http://wiki.xensource.com/xenwiki/XenNetworking#head-740e3cf58c2ac48051f74c4f72cc6df52117e87eI believe you need to setup NAT manually to allow domU to access
outside world using this method.
The other option is go with what redhat does. Using libvrtd, they
create another bridge called virbr0. You can put domU's vif on that
bridge and it will behave similar to Vmware's NAT networking (NAT and
dhcp is configured automatically). Note that the bridge is on virbr0,
not on the wireless interface.
Regards,
Fajar
_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxxhttp://lists.xensource.com/xen-users