Date: Tue, 14 Jun 2016 08:17:38 +0200 From: Bernd Walter <ticso@cicely7.cicely.de> To: Fehmi Noyan ISI <fnoyanisi@yahoo.com> Cc: "freebsd-virtualization@freebsd.org" <freebsd-virtualization@freebsd.org> Subject: Re: Cannot forward traffic over wlan0 with bhyve Message-ID: <20160614061738.GB50738@cicely7.cicely.de> In-Reply-To: <231368807.5153885.1463691015944.JavaMail.yahoo@mail.yahoo.com> References: <231368807.5153885.1463691015944.JavaMail.yahoo.ref@mail.yahoo.com> <231368807.5153885.1463691015944.JavaMail.yahoo@mail.yahoo.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, May 19, 2016 at 08:50:15PM +0000, Fehmi Noyan ISI via freebsd-virtualization wrote: > Hi there, > > As I mentioned in this forum post [1], I am having issues with getting my FreeBSD-CURRENT VM connected to the Internet via wlan0 interface. > > I created tap0 and bridge0 interfaces, and edited configuration files to keep changes permanent as suggested by the handbook [2]. > > I also set the pf rules to enable NAT between tap0 and wlan0 interfaces as described here [3]. > > > When I monitor tap0 and wlan0 interfaces with tcpdump while running "dhclient vtnet0" in the guest OS, I noticed that tap0 forwards packets to wlan0 and wlan0 recevies them (some tcpdump output is in [1]). But nothing happens after this... > > I also noticed that the pf fails to start with the ruleset given in [3], and having paranhtesis around (bridge0:network) solves the issue, so I filed a bug report for this [4]. > > I need assistance with my VM internet access and will appreciate you guidance on the matter. It's been a few weeks old, but still unanswered. The problem is that as a wifi client only a single MAC address is registered with the AP. The systems behind the bridge have their own MAC addresses, which the AP doesn't know. You either need to setup your wifi with mesh support, run the bridge on the AP instead of the client side, or run dirty tricks with proxy ARP. The best option would be to avoid bridging from wifi completely and route a different net to your vm host or use a cable. -- B.Walter <bernd@bwct.de> http://www.bwct.de Modbus/TCP Ethernet I/O Baugruppen, ARM basierte FreeBSD Rechner uvm.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20160614061738.GB50738>