From owner-freebsd-wireless@freebsd.org Wed Oct 12 20:37:22 2016 Return-Path: Delivered-To: freebsd-wireless@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 A588BC0FF84 for ; Wed, 12 Oct 2016 20:37:22 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-it0-x22b.google.com (mail-it0-x22b.google.com [IPv6:2607:f8b0:4001:c0b::22b]) (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 6FBB4316 for ; Wed, 12 Oct 2016 20:37:22 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: by mail-it0-x22b.google.com with SMTP id z65so65992562itc.0 for ; Wed, 12 Oct 2016 13:37:22 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=fN6UtLiK5VKnQYmrqqjSibt/FKVEbelGQZjHKIO/QPs=; b=M81uR9FmAzT9b8+o5CnjRNQnMzyWwqlZVq50mIr2mIlWUzHMGraKt28rMlCkUOO2SF 4MP853tYzwy6n3xNI68HhU/EmIZBVXVI4NNRuIiQlSHCiya2P8auOgEH8xbJh37cQe+g IN+c8YunHQi1tiJblmWM6ufD43rOMDPiJNz4zWWH6VT5ib9vhnHWX5yPA3WQJWl1Pn+f He9ogHx0bmMffxNSC5OHwddNM36WmeLKyPvx9bKZJ2Te8W8hS/u56pjLGR+v1/j11/Tg XJnWoR4kf77aMZH+czKb43MoAv3M1H7LeM5eJHF0AEnJy/SIvZ5gG87Q8HrWFuwdfD2+ +WRw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=fN6UtLiK5VKnQYmrqqjSibt/FKVEbelGQZjHKIO/QPs=; b=TND2rkW+8O419/SfN4WqSm3WAN5jLoZ3Rd8PTdh3HQYSf5Nj6pqlmI8uxK1gFoxtzf y1aIRavZvoPrpqJ/XPOIKp5JJhq+7xvRW8sVICQWYMgU+5MdLkV5Rxt0WKenK1iQwRkl s+HcA/Xr3SM0isXQEne8FXA1HmqAXnfSdkOHi3uzSsh+gpb13xNQsY6e29j2aCoOFlH/ QcejtjWgVJeBSq2bTIa0t/0nDyvYsb1B2hmKccgrbiavt54VhgzM+FiM3zlWbCCzf+EV FZb7P7BeOW/O26jBX4CyTfb0VLgBUpr8uqd6BC+wi2MUTMKWuguSk392o1MNaaSO6Exm ObGQ== X-Gm-Message-State: AA6/9Rl+uLvmejP30Opz9E1mN3aZSNAzISwbQIVjGaKTFTxwuPINA6i461kAnEp6pxUPH1j9IkUYsegMjyigkA== X-Received: by 10.36.127.140 with SMTP id r134mr3299115itc.29.1476304641879; Wed, 12 Oct 2016 13:37:21 -0700 (PDT) MIME-Version: 1.0 Received: by 10.36.141.129 with HTTP; Wed, 12 Oct 2016 13:37:21 -0700 (PDT) In-Reply-To: <20161012213255.585a7278@shibato> References: <20161012171700.5b4f9ea8@shibato> <20161012213255.585a7278@shibato> From: Adrian Chadd Date: Wed, 12 Oct 2016 13:37:21 -0700 Message-ID: Subject: Re: Regression: ethernet + wireless/ath under lagg To: "J.R. Oldroyd" Cc: "freebsd-wireless@freebsd.org" Content-Type: text/plain; charset=UTF-8 X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 12 Oct 2016 20:37:22 -0000 On 12 October 2016 at 12:32, J.R. Oldroyd wrote: > On Wed, 12 Oct 2016 09:08:20 -0700 Adrian Chadd wrote: >> >> hiya, >> >> there should be a way to create a vap with a specific mac address upon >> creation time. Sorry, doing lagg+wlan is not something we've been >> collectively using. :( >> >> Thanks, >> >> >> -adrian >> >> > > PR#213207 appears to be discussing this same problem. > > I am truly amazed that this "is not something we've been collectively > using"! Here, we have all of Macs, Windows, Linux for which this > "just works" and it also worked fine (with the config I posted > earlier) on 9.x and 10.x. Your bog-standard, cheapo Linksys/Netgear/ > whatever, bridge their wireless network to their wired ports, and it > is common practice here to be using wireless and then to later plug > into a wired port on those routers and have connections continue > seamlessly. Sure, but the set of wifi developers and set of wifi users is as big as the smallest set, and the set of wifi developers is like what, 3? 4? None of us were bitten by this because I don't think any of the wifi developers (me included) use lagg and failover. > A way of determining the ath's MAC address so it can be used to set > the re's MAC, or a way of setting the ath's MAC address prior to wlan > creation is needed in 11.x. Andriy has proposed one way, which I like. We'd just have to do that method for all wifi drivers, as well as making sure drivers can fail the VAP creation if a MAC is again requested and the device doesn't support it. -a