From owner-freebsd-current@FreeBSD.ORG  Wed Dec 18 07:27:59 2013
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115])
 (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by hub.freebsd.org (Postfix) with ESMTPS id E88EFD95
 for <freebsd-current@freebsd.org>; Wed, 18 Dec 2013 07:27:59 +0000 (UTC)
Received: from mail.rdsor.ro (mail.rdsor.ro [193.231.238.10])
 by mx1.freebsd.org (Postfix) with ESMTP id A876D1F15
 for <freebsd-current@freebsd.org>; Wed, 18 Dec 2013 07:27:59 +0000 (UTC)
Received: from email.rdsor.ro (ftp.rdsor.ro [193.231.238.4])
 by mail.rdsor.ro (Postfix) with ESMTP id 691BE12ADB;
 Wed, 18 Dec 2013 09:27:58 +0200 (EET)
MIME-Version: 1.0
Content-Type: text/plain;
 charset=UTF-8
Content-Transfer-Encoding: 7bit
Date: Wed, 18 Dec 2013 09:28:04 +0200
From: dan_partelly <dan_partelly@rdsor.ro>
To: <d@delphij.net>
Subject: Re: 10-RC2 current wireless link aggregation not working correctly
In-Reply-To: <52B0F40B.7020501@delphij.net>
References: <80a9ff942e0bf413ceaf9aa469b50687@rdsor.ro>
 <CAJ-VmonwU6nySMPdtBcL2TpOH01av5sfvz=4Co28r+iWYH85Nw@mail.gmail.com>
 <52B08B28.6040402@allanjude.com> <52B0F40B.7020501@delphij.net>
Message-ID: <0906290ad6b5e6c9f9bd181130c606c3@rdsor.ro>
X-Sender: dan_partelly@rdsor.ro
User-Agent: RoundCube Webmail/0.4-beta
Cc: freebsd-current@freebsd.org
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
 <freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-current>, 
 <mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current/>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
 <mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 18 Dec 2013 07:28:00 -0000


What claims you do not "believe" ? Not important anyway. This is 
engineering, so you need not believe, you need to know. Go and replicate 
the bug. You will know then.


> 
> I don't really believe these claim.
> 
> I had similar issue in the past and found an 'arp -a -d' would "fix"
> it so I didn't pursued further but I think this would be an
> interesting problem to get addressed.
> 
> If I would take an guess, I would start from making lagg(4) interface
> to initiate one or a few gratuitous ARP broadcast when the active port
> changes.  Some switches could use this to kick out their (outdated)
> memory of where the port is.
> 
> Cheers,
> - -- 
> Xin LI <delphij@delphij.net>    https://www.delphij.net/
> FreeBSD - The Power to Serve!           Live free or die
> -----BEGIN PGP SIGNATURE-----
> 
> iQIcBAEBCgAGBQJSsPQLAAoJEJW2GBstM+nsyXoP/RCeHdu1PVCooIUxzjhqWMJG
> 3RyN9i85O1WYpgZwHCSC9mkFKM6GjEIiyaNKCvdYzN/k+d9aCQSXIShgIGutM6ie
> hFD4GCGrevjquHCddpULlUE+iwj0qIJWSyRMusUgo+ya+Bc/4H+szoxTndXaaamz
> CPkZMuzga8kEApXgMvImGfsqB8FqqFNtEELlRmISEHb04iAGqUv6HwoL1DhqEZ3I
> tQQi73JvuCU3Lfbp4CDI0IeTzlAoARBX/mWFjlDm7CA8clu4PzIVhdsRxRUhXIId
> ijI8432al9XXt0m4+4LIKmJa6DlyvQ3pIZDFodryQ1za3PAaF7IheILFKPi9BAwi
> Tn47X2+2XYXx7ZS2S22R7KRgeORZqj2uYZifs/xsNwkBCsyntYZgH+c5qYU7TWb/
> tWRi9c5uVFskoPx4JL4W3ctgPvN7TpvKeCBLZTBdLQjy9WT6sqhxChxS57SFT5AH
> kTOWNEA0PqWjrrqRlNO47TL/aTg3Js9S4KxIZ2+hHSkDAlMxGi9rHzyHYPQKxJ1V
> lLmLGN0ZRYGGKa4Yn2OBAy16q/I2jkLE0Nkb0u1V3EEMkKQWp6pcro/Kb9Hrirfe
> n6zrFVyzLTIgNpr9C1+By1CxAmJfg73cIoobJSjNDZ2+EpY+FRDdhKYip3xtpNfA
> QFmabonocmaEohNcC8me
> =mSYS
> -----END PGP SIGNATURE-----
> _______________________________________________
> freebsd-current@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-current
> To unsubscribe, send any mail to
"freebsd-current-unsubscribe@freebsd.org"