From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-04-ewr.dyndns.com (mxout-044-ewr.mailhop.org [216.146.33.44]) by lists.bufferbloat.net (Postfix) with ESMTP id 839C62E0419 for ; Sun, 17 Apr 2011 07:46:28 -0700 (PDT) Received: from scan-02-ewr.mailhop.org (scan-02-ewr.local [10.0.141.224]) by mail-04-ewr.dyndns.com (Postfix) with ESMTP id 352267E9143 for ; Sun, 17 Apr 2011 14:46:27 +0000 (UTC) X-Spam-Score: 0.0 () X-Mail-Handler: MailHop by DynDNS X-Originating-IP: 149.20.54.64 Received: from mainmail.teklibre.com (toutatis.isc.org [149.20.54.64]) by mail-04-ewr.dyndns.com (Postfix) with ESMTP id 717777E39F4 for ; Sun, 17 Apr 2011 14:46:25 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by mainmail.teklibre.com (Postfix) with ESMTP id 47BB712B74A for ; Sun, 17 Apr 2011 08:20:55 -0700 (PDT) Received: from mainmail.teklibre.com ([127.0.0.1]) by localhost (toutatis.sql1.isc.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Og2P39lTkQZU for ; Sun, 17 Apr 2011 08:20:55 -0700 (PDT) Received: from [192.168.1.4] (c-68-39-173-20.hsd1.nj.comcast.net [68.39.173.20]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) (Authenticated sender: d) by mainmail.teklibre.com (Postfix) with ESMTPSA id 7D69D12B6AB for ; Sun, 17 Apr 2011 08:20:54 -0700 (PDT) Message-ID: <4DAAFD3E.1050509@taht.net> Date: Sun, 17 Apr 2011 08:46:22 -0600 From: Dave Taht User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.14) Gecko/20110223 Thunderbird/3.1.8 MIME-Version: 1.0 To: bismark-devel@lists.bufferbloat.net References: <97EDD940-729E-4700-92B1-04DD7121CAB2@cc.gatech.edu> In-Reply-To: <97EDD940-729E-4700-92B1-04DD7121CAB2@cc.gatech.edu> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit 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:46:28 -0000 On 04/17/2011 08:36 AM, Nick Feamster wrote: > when I ping my server from the openwrt box, I can see it: > > root@OpenWrt:~# ping 172.16.0.159 > PING 172.16.0.159 (172.16.0.159): 56 data bytes > 64 bytes from 172.16.0.159: seq=0 ttl=64 time=1.326 ms > 64 bytes from 172.16.0.159: seq=1 ttl=64 time=1.365 ms > > > but when I associate to the SSID of the OpenWRT box and try to ping my server's IP address, I can't. > > Strangely, when I associate to an access point that is *downstream* of the OpenWRT box (i.e., a second access point that is actually connected to one of the switch ports on the OpenWRT box), pinging also works. It is only when I associate directly to the OpenWRT box that (1) upnp names (e.g., back-bay.local), and (2) pinging the .159 address do not work. > Multicast DNS (.local) addresses need a mdnsresponder installed. By default you are using pure dnsmasq, which defaults to naming various machines whatever.lan, (and can be configured to "do the right thing for real internet connections" by setting up For example, in my case, my main dns server out on the internet for taht.net delegates the subdomain "co.teklibre.org" to my gateway there (or it did, before I left colorado) and my router would assign names and addresses inside of that space, (after setting it up to use co.teklibre.org and not .lan) example: cruithne.co.teklibre.org is my laptop. > Any ideas what is going on here? > I'm mildly confused as to your topology here. Diagram? 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 HATE AP isolation personally, but it exists to virus proof public wireless lans) Ping me on #bismark if you need further aid. > Thanks! > -Nick > _______________________________________________ > Bismark-devel mailing list > Bismark-devel@lists.bufferbloat.net > https://lists.bufferbloat.net/listinfo/bismark-devel