Take the 2-minute tour ×
Server Fault is a question and answer site for professional system and network administrators. It's 100% free, no registration required.

Why does KVM not support wireless bridge networking mode, whereas VirtualBox and do it very well? parprouted doesn't help.

I want to allow KVM guests to act as if they have a bridged network interface rather then NAT. As it turns out you can not simply bridge your wireless card with brctl as you do with a wired NIC.

share|improve this question
    
Huh? Could you provide details as to why you're saying this? –  sybreon Feb 14 '11 at 5:12

1 Answer 1

Because 802.11 looks just enough like Ethernet to make you think that it is Ethernet, whereas it's really not. Things like bridging don't Just Work with 802.11, which is why putting a wireless interface into a brctl bridge doesn't work as expected. VirtualBox and VMware have implemented specific wireless bridging in order to make this work (they just don't make a distinction to users).

The solution is to use parprouted, which essentially bridges at layer 3 instead of layer 2. The caveat is that this only works for unicast traffic -- broadcast traffic is not relayed across the bridge. This is a problem for DHCP, which requires broadcast. If the VM needs to DHCP across the bridge, you need to setup dhcrelay as well in order to get this working.

share|improve this answer

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.