Quote from: divinesnail01 on April 05, 2014, 05:25:06 PM

Quote from: DanZaph on April 05, 2014, 11:42:48 AM

Quote from: divinesnail01 on April 05, 2014, 02:14:39 AM

Really short version: The more you can isolate these on the network the happier they'll be...

[snip]

Longer version: I didn't think the Android issue would apply to me...

The issue with Android is using IP addresses after the DHCP lease expires, not traffic. See DHCP client ignores lease time: https://code.google.com/p/android/issues/detail?id=11236.

So, a good solution is to put the Android devices on a separate logical network. If the primary network is 192.168.1.x then create a second network such as 192.168.2.x (both with a net mask of 255.255.255.0). Unfortunately that means two routers.

Is this what you did with the second router?

And that was exactly some of my reasoning for not worrying about the Androids: Though on the same logical network, the Android device addresses were assigned in a different part of the address space than the addresses I was using for the cubes and the proxies; I have my DHCP leases set for 7 days; my DHCP server pings the address as it's being assigned to be sure that there isn't a "squatter" on the address before offering it. It's pretty difficult for a lease to expire and create an address conflict under those circumstances. Further, I saw the same behavior with the proxies in my DHCP space as I did with them assigned statically outside of the DHCP pool.

I haven't spent the time, and probably won't, to dive deeper into what's going on on the network, but I can say with some confidence that it's not an issue of IP address conflicts, unless the android devices are "making up" addresses to use elsewhere in the address space, and managing to do that without causing other devices to squawk about an address conflict. Ultimately, however, that turns into a Quixotic discussion - there definitely IS something about having cubes on the same network with other devices, likely Androids, and the solution is the same regardless of the root cause: get them isolated from each other.

My solution has been to create a completely separate physical network. I've used different IP addressing for that network, but since they aren't interconnected, it really doesn't matter. It's a little bit of an extreme solution, but very effective.

A follow up seems in order.

Since moving the cubes and proxy machines to a separate network, I have had no / none / zero / not any of the communication problems I was seeing, and it has been 13 days.
Whatever the reason (I'm still not buying the IP address conflict theory, but I'm not going to go back and run a network sniffer to prove it) these little monsters really like being on their own network.

Perhaps that will help someone else who may struggle.

'snail