[Cerowrt-devel] MacBook Pro (Snow Leopard) constantly renaming

[Cerowrt-devel] MacBook Pro (Snow Leopard) constantly renaming

[William Allen Simpson]

I've only been running Sugarland for about a week now, but
something is causing my laptop to rename itself almost every
time I open the lid.  Is this a known issue?

I've not been keeping up with Ubuntu releases (we stopped at
10.04 LTS because of the desktop changes), so it could be an
issue with newer avahi releases?  Or is this newer dhcpd?

Anyway, it never used to happen, and I'm already up to
"Wastrel (1895)" and "wastrel-1877.local" -- they don't seem to
increment uniformly or together, it just went from 1805 to 1895.

I locked down the dhcpd config by MAC to wastrel.home.lan, it
was so annoying that it was changing all the time.

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.

Re: [Cerowrt-devel] MacBook Pro (Snow Leopard) constantly renaming

[Phil Pennock]

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

Re: [Cerowrt-devel] MacBook Pro (Snow Leopard) constantly renaming

[William Allen Simpson]

On 2/1/13 8:52 PM, Phil Pennock wrote:
> Something is re-broadcasting the announcements back onto a network.
> [...]
> Something similar may be happening?
>
No, I'm only using WiFi and the only device in the middle is cerowrt, and
it's supposed to be routing not bridging.  On the wired side, I do
have a 32" monitor/TV linked in -- and apparently running Linux (I had
them send me a CD with the open source, but haven't looked at it).  And
that's attached to a M$ Windows machine to run Quicken and Skyrim.

But as I'd mentioned earlier, this didn't happen until I replaced the
Netgear software with cerowrt.  Nothing else has changed in months.

I'll let folks know whether disconnecting the Insignia monitor/TV
changed anything, but I doubt it.

Re: [Cerowrt-devel] MacBook Pro (Snow Leopard) constantly renaming

[Alex Hulse]

Hi there

A while ago this problem was reported as happening and it was decided that it is to be blamed on avahi and the reflector functionality in it. I think Dave said that the bug had been reported but that nothing had been done about it 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, MacBook, airport express, time capsule and appletv). I think this points to something "wrong" in avahi's implementation of the spec or an apple specific (but not device specific) quirk in handling it. 

Alex

On 2 Feb 2013, at 01:52, Phil Pennock <cerowrt-devel+phil@spodhuis.org> wrote:

> 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
> _______________________________________________
> Cerowrt-devel mailing list
> Cerowrt-devel@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/cerowrt-devel