From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mx.spodhuis.org (smtp.spodhuis.org [IPv6:2a02:898:31:0:48:4558:736d:7470]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by huchra.bufferbloat.net (Postfix) with ESMTPS id 2D50421F115 for ; Fri, 1 Feb 2013 17:52:33 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=spodhuis.org; s=d201210; h=In-Reply-To:Content-Type:MIME-Version:References:Message-ID:Subject:Cc:To:From:Date; bh=haMuhspDSbp8TwqMOBM/AfS7AeiK9BKtFAXeNoCQT+M=; b=P9PY2JU6N12OsKM03HcBrp2n8o0Nf7NvPr20EREiWkf+XOJXMeP8RZ2JChKBqONZzfozLoDFGI3bM4GzOTnrS1MpHB5THuLVlWAW1j7bQ3tEuYnZ1gKLFMd56y4iBbHQpujbepjo+Jto5rnlMzrlyYb2NNxiXXqhazEGAMdXTMc=; Received: from authenticated user by smtp.spodhuis.org with esmtpsa (TLSv1.2:DHE-RSA-AES256-GCM-SHA384:256) id 1U1SHN-0001iB-VJ; Sat, 02 Feb 2013 01:52:30 +0000 Date: Fri, 1 Feb 2013 20:52:28 -0500 From: Phil Pennock To: William Allen Simpson Message-ID: <20130202015228.GA6468@redoubt.spodhuis.org> Mail-Followup-To: William Allen Simpson , cerowrt-devel References: <510C3214.2010001@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <510C3214.2010001@gmail.com> Cc: cerowrt-devel Subject: Re: [Cerowrt-devel] MacBook Pro (Snow Leopard) constantly renaming X-BeenThere: cerowrt-devel@lists.bufferbloat.net X-Mailman-Version: 2.1.13 Precedence: list List-Id: Development issues regarding the cerowrt test router project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 02 Feb 2013 01:52:33 -0000 On 2013-02-01 at 16:22 -0500, William Allen Simpson wrote: > Anyway, it's probably a simple bug where they don't properly > check the MAC address as they decide whether a machine of the > same name is already present on the lan. If anybody has an > idea where to look, I'll try fixing it. Something is re-broadcasting the announcements back onto a network. I wasn't involved in diagnosis, so going from what I was told: At work, they had this exact same problem in the SF office and they discovered that Sonos music players automatically bridge together any networks they find and join, so there's a bridge built into a player device, which caused packets from MacOS on wifi to go out on wifi, be bridged onto the wired VLAN on the Sonos, then come back into the laptops; from this, it seems it would only affect machines plugged into a wired network. (At which point, one of them suddenly remembered that $previous_employer had banned these devices and now knew why). Something similar may be happening? -Phil