From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from b.painless.aa.net.uk (b.painless.aa.net.uk [IPv6:2001:8b0:0:30::51bb:1e34]) (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 2CD1421F14E for ; Sun, 3 Feb 2013 03:34:46 -0800 (PST) Received: from f.f.d.f.3.9.d.f.f.3.f.b.a.d.9.8.1.0.0.0.d.9.f.f.0.b.8.0.1.0.0.2.ip6.arpa ([2001:8b0:ff9d:1:89da:bf3f:fd93:fdff]) by b.painless.aa.net.uk with esmtps (TLSv1:AES128-SHA:128) (Exim 4.72) (envelope-from ) id 1U1xqL-00060E-Un; Sun, 03 Feb 2013 11:34:43 +0000 References: <510C3214.2010001@gmail.com> <20130202015228.GA6468@redoubt.spodhuis.org> Mime-Version: 1.0 (1.0) In-Reply-To: <20130202015228.GA6468@redoubt.spodhuis.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Message-Id: <90C20247-4E2C-4AA3-98CF-8F82B9806209@amch.net> X-Mailer: iPad Mail (10B141) From: Alex Hulse Date: Sun, 3 Feb 2013 11:34:42 +0000 To: Phil Pennock 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: Sun, 03 Feb 2013 11:34:47 -0000 Hi there A while ago this problem was reported as happening and it was decided that i= t is to be blamed on avahi and the reflector functionality in it. I think Da= ve said that the bug had been reported but that nothing had been done about i= t upstream - I looked but couldn't find a specific bug on avahi's trac. When I had a cero like set up with plain openwrt (routed rather than bridged= ) with avahi running I had the same happen to my apple devices (iMac, MacBoo= k, airport express, time capsule and appletv). I think this points to someth= ing "wrong" in avahi's implementation of the spec or an apple specific (but n= ot device specific) quirk in handling it.=20 Alex On 2 Feb 2013, at 01:52, Phil Pennock wrot= e: > 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. >=20 > Something is re-broadcasting the announcements back onto a network. >=20 > 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. >=20 > (At which point, one of them suddenly remembered that $previous_employer > had banned these devices and now knew why). >=20 > Something similar may be happening? >=20 > -Phil > _______________________________________________ > Cerowrt-devel mailing list > Cerowrt-devel@lists.bufferbloat.net > https://lists.bufferbloat.net/listinfo/cerowrt-devel