From owner-freebsd-current@freebsd.org Sat Jul 30 00:27:17 2016 Return-Path: Delivered-To: freebsd-current@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 3638CBA8CB2 for ; Sat, 30 Jul 2016 00:27:17 +0000 (UTC) (envelope-from rwestlun@gmail.com) Received: from mail-qk0-x234.google.com (mail-qk0-x234.google.com [IPv6:2607:f8b0:400d:c09::234]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id E16B61374 for ; Sat, 30 Jul 2016 00:27:16 +0000 (UTC) (envelope-from rwestlun@gmail.com) Received: by mail-qk0-x234.google.com with SMTP id s63so105254132qkb.2 for ; Fri, 29 Jul 2016 17:27:16 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=date:from:to:cc:subject:message-id:references:mime-version :content-disposition:in-reply-to:user-agent; bh=IN2vx66q/fH1/w6AgkNUF5QvWdau/1N/Hf8LCJZZqpg=; b=E2McrkwMFfSIligZGKSk/lxhlJGn23vcSXbSfk53GHS2vlicfj+rzapkIiwYA8laiv 6m88cle4n56nd8ZrqUlZnYqMp0ohABmGeJuD+Gt67bODTJpT8kOivBdkArDmV36btTor Lx+1IejTrlZCLSAdfaOap/7LNWvaWe9xU3pQMIRtQc/ULGCrlApBAK7dKDkUlmS0jOOS bFYce5k3aGi3JDvU6c7WVT7e37R1TSG6hJc/BapEFwgTBsnzJqKH0HBL8Jqh85Wqyc9Y 8aNXv0aXIFCHGDt+RkaKSiPGouGfzzuqq/B8SD7Wya0faQ4qj23V9NHUe4B06PmtCHA2 fbQQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-disposition:in-reply-to:user-agent; bh=IN2vx66q/fH1/w6AgkNUF5QvWdau/1N/Hf8LCJZZqpg=; b=ZzA2lbkRY+TihmKFWzq9CH28j3GmpKTaL5PI2ijRkx3X1HJBiYRFG66rL/uCPVuMfr MPHkUMb28+EFt5vglIyghC7ieEaoqw1UHwRzQHDeFRQPWbldOqvQFwK8UinEuI39Mb8M q1EMiba4hAUfPDsX8ZJwhfum26/9q9ydwXUCPWmPR37te+1E2hXyaZiHZuwh75My21u4 zxRt/bU6DyG1Fh40RugrQU9BheOTmT++cl3Z7T6iry+uiNetdabkV60Oa5wg4PfgjS8j p/mhxhJWGmnAfM/NslOznPbYEd1gW4y7kIIZwPMdomm9jSgXrBiM8bvrtdAUhu0hms7V 3cnQ== X-Gm-Message-State: AEkoouuwtwiKTg6qvFtHARVODjPtT2f6eW/XCzOuKr1tFYZy34mRwU12muF+0bPVFBYtSQ== X-Received: by 10.55.81.9 with SMTP id f9mr52043991qkb.194.1469838435881; Fri, 29 Jul 2016 17:27:15 -0700 (PDT) Received: from gmail.com (c-98-216-247-110.hsd1.ma.comcast.net. [98.216.247.110]) by smtp.gmail.com with ESMTPSA id a67sm11401103qkc.24.2016.07.29.17.26.57 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 29 Jul 2016 17:26:57 -0700 (PDT) Date: Fri, 29 Jul 2016 20:26:56 -0400 From: Randy Westlund To: John Nielsen Cc: freebsd-current@freebsd.org Subject: Re: bhyve with lagg failover doesn't work on wifi Message-ID: <20160730002656.GK26793@gmail.com> References: <20160729045652.GJ26793@gmail.com> <14F7DC55-3072-452F-AA70-1EA8701327E7@jnielsen.net> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="CqfQkoYPE/jGoa5Q" Content-Disposition: inline In-Reply-To: <14F7DC55-3072-452F-AA70-1EA8701327E7@jnielsen.net> User-Agent: Mutt/1.6.1 (2016-04-27) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 30 Jul 2016 00:27:17 -0000 --CqfQkoYPE/jGoa5Q Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Fri, Jul 29, 2016 at 01:06:52PM -0600, John Nielsen wrote: > Generally speaking, you can't bridge the station side of a wireless link.= The access point will only accept frames with the station's MAC address. S= o what you are seeing is expected, unfortunately. >=20 > Your best bet is probably to do NAT. Take lagg0 out of the bridge and use= it as your "public" interface. Assign a local IP to the bridge. Run a DHCP= server on your host (or in another VM on the bridge if you like) or just u= se static internal IPs on your VMs. Enable IP forwarding (gateway_enable=3D= yes in rc.conf). Configure your firewall to NAT your private range out lagg= 0. >=20 > You can do other things with tunneling, etc. but you'll need a remote end= point for the tunnel. (If your access point runs FreeBSD you can use either= vxlan or gif+EtherIP and just use the wireless link to carry the tunnel tr= affic, but I suspect that you want to roam between arbitrary access points.) Thanks for the explanation, that makes perfect sense. I hadn't considered the implications of a layer 2 bridge to a wireless link. --CqfQkoYPE/jGoa5Q Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQEcBAEBCAAGBQJXm/RQAAoJEGaweXjzNsmpbPIH/3xv5Kby7gtseHJAsTeOCewm OhtfOLrOlLAfMJ+kjxmpMWit5s/GtO2g33UgTV+is6kD2jkJpOdmW/Fx2bpEp+5k hkgEBvKWNFfEIWIl6Pyuy2Kdl7tsGtajEOulPYJiRLWGtBthE6RdKoEQI8o02E4v MRAhDdIhMT0gTK1MiTAHlPAmtAXV6J9AUmpZI283auY2aphfQ66liqPtkd+9hxUG 4xFNIrzca4K2Z7dC/lyYPqZH/NrjiGNb/ginqtTFxMLw2rfiw6SQn3Nf2YdQmI1R Z6/74poO5jYxMQZ3LzpJwKrZWI17M8ycAVYYZhojPXWCbLHJcnogX5oY3ZiH80w= =I7Lm -----END PGP SIGNATURE----- --CqfQkoYPE/jGoa5Q--