From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-24-ewr.dyndns.com (mxout-024-ewr.mailhop.org [216.146.33.24]) by lists.bufferbloat.net (Postfix) with ESMTP id 8A8032E07DF for ; Sun, 17 Apr 2011 07:52:31 -0700 (PDT) Received: from scan-22-ewr.mailhop.org (scan-22-ewr.local [10.0.141.244]) by mail-24-ewr.dyndns.com (Postfix) with ESMTP id C94645D2D79 for ; Sun, 17 Apr 2011 14:52:29 +0000 (UTC) X-Spam-Score: 0.0 () X-Mail-Handler: MailHop by DynDNS X-Originating-IP: 130.207.160.69 Received: from deliverator2.gatech.edu (deliverator2.gatech.edu [130.207.160.69]) by mail-24-ewr.dyndns.com (Postfix) with ESMTP id 71B305D2855 for ; Sun, 17 Apr 2011 14:52:25 +0000 (UTC) Received: from deliverator2.gatech.edu (localhost [127.0.0.1]) by localhost (Postfix) with SMTP id 50DD4481007; Sun, 17 Apr 2011 10:52:24 -0400 (EDT) Received: from mail1.gatech.edu (mail1.gatech.edu [130.207.185.161]) by deliverator2.gatech.edu (Postfix) with ESMTP id D7692481006; Sun, 17 Apr 2011 10:52:23 -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 mail1.gatech.edu (Postfix) with ESMTPSA id B2041C2EFF; Sun, 17 Apr 2011 10:52:23 -0400 (EDT) Mime-Version: 1.0 (Apple Message framework v1082) Content-Type: text/plain; charset=us-ascii From: Nick Feamster In-Reply-To: <4DAAFD3E.1050509@taht.net> Date: Sun, 17 Apr 2011 10:52:22 -0400 Content-Transfer-Encoding: quoted-printable Message-Id: References: <97EDD940-729E-4700-92B1-04DD7121CAB2@cc.gatech.edu> <4DAAFD3E.1050509@taht.net> To: Dave Taht 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: Sun, 17 Apr 2011 14:52:31 -0000 On Apr 17, 2011, at 10:46 AM, Dave Taht wrote: > I'm mildly confused as to your topology here. Diagram? >=20 > You are behind NAT by default, so if you try to ping through the WAN = port to something anything inside the LAN, those machines will be = unreachable. You should however, be able to ping from the wireless to = anywhere wired, LAN or WAN port. If you have AP isolation turned on in = the wireless side, you cannot ping any other wireless connection, and = I'm unsure what the behavior is for wired to wireless in that case. I'm just talking about my LAN here: SERVER <----(2.4 GHz wireless, SSID "foo") ----> = WNDR3700 <---- (wired LAN port) ----> Access Point 2=20 * When I associate to AP2, I can ping SERVER, and resolve MDNS names. * When I log into WNDR, I can ping SERVER * When I associate to the WNDR3700, I can neither ping the server, nor = resolve MDNS names. So, isn't it strange that everything works when I'm connected via AP2, = but not via the WNDR? By my reasoning, all of the traffic that I'm = sending when I'm connected via AP2 would have to go through the WNDR = anyhow... -Nick=