Question

I'm using KVM to run a Windows virtual machine on my Linux box. Networking is accomplished through a tap device, hooked into a bridged Ethernet device, which allows the Windows VM to basically appear like a separate physical computer on my network. This is pretty nice.

However, my understanding is that most, if not all, wireless drivers can't support bridging. I'd really like to be able to roam a little more freely while I'm working -- does anyone know of an effective workaround?

User-mode networking won't work, as I have to use some Windows VPN software that wants lower-level networking access.

Was it helpful?

Solution 2

Other, related questions like this one seem to indicate it is simply a limitation of many wireless drivers. There are a few for Linux that will do bridging, but one would have to plan to build that into their system from day one.

OTHER TIPS

I assume that you could configure your Windows guest to use the host as its default gateway, and set up NAT via the wireless interface on the host. So the signal flow would look like this:

  1. Windows software opens connections to a host on the internets.
  2. Windows routes the packet via the default gateway, i.e. the host Linux system.
  3. Linux does NAT magic and routes the packet via its normal routing table (which should use a default gateway via the wireless interface).

I have never tried this in combination with bridging though.

Why it should be a problem to setup host linux system to use WLAN and then us this connection as default gateway for local/internal bridge and all VMs are pluged into it? Ok, simple NAT has to be configured but what ist actually the point?

Licensed under: CC-BY-SA with attribution
Not affiliated with StackOverflow
scroll top