From owner-freebsd-doc@freebsd.org Sun May 22 22:57:17 2016 Return-Path: Delivered-To: freebsd-doc@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 2F232B3B1A1 for ; Sun, 22 May 2016 22:57:17 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 2029F19BB for ; Sun, 22 May 2016 22:57:17 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id u4MMvGqP033138 for ; Sun, 22 May 2016 22:57:16 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-doc@FreeBSD.org Subject: [Bug 209479] Incorrect PF NAT rule set in bhyve wiki page Date: Sun, 22 May 2016 22:57:17 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Documentation X-Bugzilla-Component: Documentation X-Bugzilla-Version: Latest X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: fnoyanisi@yahoo.com X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-doc@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-doc@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Documentation project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 22 May 2016 22:57:17 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D209479 --- Comment #4 from fehmi noyan isi --- 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.=20 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 Inte= rnet from people having similar/same issues)=20 [1] https://lists.freebsd.org/pipermail/freebsd-virtualization/2016-May/004465.= html [2] https://forums.freebsd.org/threads/56285/ --=20 You are receiving this mail because: You are the assignee for the bug.=