From owner-freebsd-net@FreeBSD.ORG Fri Aug 31 18:09:31 2012 Return-Path: Delivered-To: net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 64F23106564A; Fri, 31 Aug 2012 18:09:31 +0000 (UTC) (envelope-from kaltheat@zoho.com) Received: from sender1.zohomail.com (sender1.zohomail.com [72.5.230.95]) by mx1.freebsd.org (Postfix) with ESMTP id 486738FC1D; Fri, 31 Aug 2012 18:09:30 +0000 (UTC) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=zapps768; d=zoho.com; h=date:from:to:cc:subject:message-id:references:mime-version:content-type:in-reply-to:sender; b=qm1s5GOyKJt0TpoBV+vV9VQcLl9ROtXvPlmk2fyKPECa10aab0+FRVm4CKhleACAKzjnZ88DWsT3 ZkinZaRclb+xmPVyoQVQLTShQoQ8YlXI/RrQXrU5v2fqpVjyT/wu Received: from - (106-147-103-86.dynamic.dsl.tng.de [86.103.147.106]) by mx.zohomail.com with SMTPS id 1346436570207794.4817511890449; Fri, 31 Aug 2012 11:09:30 -0700 (PDT) Date: Fri, 31 Aug 2012 20:09:20 +0200 From: kaltheat@googlemail.com To: Adrian Chadd Message-ID: <20120831180920.GA8171@-> References: <20120830215147.GA2383@-> <20120831104532.GA1758@-> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Sender: kaltheat@zoho.com X-ZohoMailClient: External X-Zoho-Virus-Status: 2 Cc: net@freebsd.org Subject: Re: lagg failover issue X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 31 Aug 2012 18:09:31 -0000 On Fri, Aug 31, 2012 at 04:29:53AM -0700, Adrian Chadd wrote: > guys, > > You can't override set the outbound MAC address of a wireless station. > It associates with the MAC address of the card/vap/device. The AP > _will_ store that MAC address in its node table. > > When sending frames from a STA, the only available details are: > > * source address - STA MAC > * destination BSS - the destination BSS MAC address, ie which AP to send to > * destination address - the destnation MAC > > only in WDS (4-address) setups is there a fourth address, which is the > "actual original source MAC address". In this instance, the STA is > actually tunnelling traffic from other source MACs. > > I don't know who started that lagg hack, but let me just be really > really clear - if you try sending the source frames out a wifi > interface with a source MAC that isn't the STA mac, it won't work. By > design. If it does work - it's a fluke and it's not portable. > > What you really want is for the same IP to exist but only both > interfaces and have the source interface/MAC seamlessly change. > > There've been proposals in the past for the STA side code to "proxy > STA" a bunch of other MACs behind it - using 3 address frames( ie, not > WDS) but keeping state as to which IP traffic is going to which MAC > address. No, net80211 in our tree doesn't have that support. > > I hope that puts this all to rest. > > > > Adrian > -- cutted here --------- Hi Adrian, Maybe I don't understand you, but this summarizes what I think I understood: Changing the wireless NIC's MAC is not possible. Only in some cases, but those cases are exceptions and shouldn't exist. I don't understand how this is pushing me further to solve my problem. As I mentioned I'm now changing the MAC of the wired NIC to that one of the wireless NIC. So your remarks don't apply to this situation, I think. Am I right? By the way: Do you think the configuration examples (in handbook and manpage) I provided earlier in this thread are misleading and should be changed? kaltheat