Date: Sun, 22 May 2016 22:57:17 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-doc@FreeBSD.org Subject: [Bug 209479] Incorrect PF NAT rule set in bhyve wiki page Message-ID: <bug-209479-9-4oRyDATnbN@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-209479-9@https.bugs.freebsd.org/bugzilla/> References: <bug-209479-9@https.bugs.freebsd.org/bugzilla/>
index | next in thread | previous in thread | raw e-mail
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=209479 --- Comment #4 from fehmi noyan isi <fnoyanisi@yahoo.com> --- I managed to get my VM's network connection fixed by using an indirect approach. This email [1] and this forum thread [2] have all details. In short, what I did was; - assigning an static IP address to tap0 on the host machine - assigning an static IP address to vtnet0 on the guest machine - use tap0 IP address as the defaultrouter in rc.conf - use pf(4) to forward traffic from tap0 to wlan0 (contents of relevant configration files are give in [2]) I did not use the bridge0 interface, in fact I removed it completely. Using static IP addresses and PF rules to redirect/NAT the traffic were all needed for me to get it working. However, as you have more VMs around, this configuration might get hard to manage.... I still think that bhyve wiki should be updated with more information on the usage of wlan0 interface with bhyve (have seen some other posts in the Internet from people having similar/same issues) [1] https://lists.freebsd.org/pipermail/freebsd-virtualization/2016-May/004465.html [2] https://forums.freebsd.org/threads/56285/ -- You are receiving this mail because: You are the assignee for the bug.help
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-209479-9-4oRyDATnbN>