From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-03-ewr.dyndns.com (mxout-048-ewr.mailhop.org [216.146.33.48]) by lists.bufferbloat.net (Postfix) with ESMTP id A71002E07DF for ; Sun, 17 Apr 2011 19:19:49 -0700 (PDT) Received: from scan-01-ewr.mailhop.org (scanner [10.0.141.223]) by mail-03-ewr.dyndns.com (Postfix) with ESMTP id C35C2787441 for ; Mon, 18 Apr 2011 02:19:45 +0000 (UTC) X-Spam-Score: 0.0 () X-Mail-Handler: MailHop by DynDNS X-Originating-IP: 130.207.160.71 Received: from deliverator6.gatech.edu (deliverator6.gatech.edu [130.207.160.71]) by mail-03-ewr.dyndns.com (Postfix) with ESMTP id 2CE1B787047 for ; Mon, 18 Apr 2011 02:19:44 +0000 (UTC) Received: from deliverator6.gatech.edu (localhost [127.0.0.1]) by localhost (Postfix) with SMTP id A09C720C1D1; Sun, 17 Apr 2011 22:19:43 -0400 (EDT) Received: from mail3.gatech.edu (mail3.gatech.edu [130.207.185.163]) by deliverator6.gatech.edu (Postfix) with ESMTP id 4601B20C1CE; Sun, 17 Apr 2011 22:19:43 -0400 (EDT) Received: from kenmore-square.lan (adsl-145-176-102.asm.bellsouth.net [72.145.176.102]) (Authenticated sender: nf21@mail.gatech.edu) by mail3.gatech.edu (Postfix) with ESMTPSA id 28A0E149284; Sun, 17 Apr 2011 22:19:43 -0400 (EDT) Mime-Version: 1.0 (Apple Message framework v1082) Content-Type: text/plain; charset=us-ascii From: Nick Feamster In-Reply-To: <4DAB840F.3070903@hawtin.net.au> Date: Sun, 17 Apr 2011 22:19:41 -0400 Content-Transfer-Encoding: quoted-printable Message-Id: References: <97EDD940-729E-4700-92B1-04DD7121CAB2@cc.gatech.edu> <4DAAFD3E.1050509@taht.net> <4DAB840F.3070903@hawtin.net.au> To: Kim Hawtin X-Mailer: Apple Mail (2.1082) Cc: bismark-devel@lists.bufferbloat.net Subject: Re: [Bismark-devel] switching issue on device X-BeenThere: bismark-devel@lists.bufferbloat.net X-Mailman-Version: 2.1.13 Precedence: list List-Id: BISMark related software development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 18 Apr 2011 02:19:49 -0000 On Apr 17, 2011, at 8:21 PM, Kim Hawtin wrote: > Perhaps the AP is building an internal table using mdns to = allow/identify traffic across its interfaces? Yes, I also initially suspected an mdns issue, but it turned out to be = the AP isolation point that Dave mentioned. Both Dave and Srikanth insist that this option is disabled by default, = but I'm pretty sure I would not have blindly disabled this option, = especially since I had no idea what it was, or that it even existed, = before today. Hmm... maybe I'm becoming senile. -Nick=