summary refs log tree commit diff stats
path: root/mailinglist/output_launchpad/1903493
diff options
context:
space:
mode:
Diffstat (limited to 'mailinglist/output_launchpad/1903493')
-rw-r--r--mailinglist/output_launchpad/19034938
1 files changed, 8 insertions, 0 deletions
diff --git a/mailinglist/output_launchpad/1903493 b/mailinglist/output_launchpad/1903493
new file mode 100644
index 00000000..93a35337
--- /dev/null
+++ b/mailinglist/output_launchpad/1903493
@@ -0,0 +1,8 @@
+About wireless network card bridging
+
+As a rookie, I don’t know if I should ask this question here. If it’s not right, I hope people who see it can help submit it to the right place. Qemu-kvm can add wireless network card bridging, after all, now you see that vbox and vmware can directly choose wireless network card bridging, and even hyper-v can be easily set up, arp proxy is too difficult for us rookies . I hope that qemu or other links can add a function to bridge the wireless network card, which can be directly set in virt-manager (for so many years, it seems that I can only use bridge-utils to bridge the Ethernet)
+
+Sorry, but at least I have a hard time to understand what you exactly are requesting here? Why should bridging via a wireless card on the host be much different to bridging via an ethernet interface on the host? Or do you expect to see a wireless network card in the guest?
+
+[Expired for QEMU because there has been no activity for 60 days.]
+