Help IP address range

[CarLoad]

I've been using the IP address range 169.254.77.xxx for years for my home network with no problems. It's one of the less frequently used private network ranges.
I fought my new nook-color(s) for 2 days, trying 2 different routers plus a Windows DHCP server before figuring out that androids just don't like that address range. My kids all have android phones (my work gives me a crackberry) and have always had a lot of problems getting an IP address (the NCs try obtaining IP address for about 30 seconds before giving up).
Finally figured out that they'll hook right up to a 2nd router running the more usual 192.168.1.xxx address range. So now I'm using both because I have several devices running static IPs in the problem range, and I'd rather not reconfigure all of them. But it's not a good permanent situation either because the android devices can't see the media servers on the main network.
Anyone have any bright ideas on overcoming this? Thanks...

 

[colchiro]

Most routers come with 192.168.1.1 by default so I went to the 10.1 for home. I hate default settings since that's a security hole IMO.

 

[CarLoad]

Colchiro, Thanks for putting this in the right forum. I realized too late I was still in the rooting area.
I assume the 10.1 range works ok for you...
anyone know why the 169.254.77.xxx range seems to be unusable on the droids?
anything in the code that looks for specific ranges etc?
thanks again...

 

[colchiro]

Did you try assigning it an address in the phone?

Did you try rebooting the router?

 

[lunatic59]

It could be that the 169.254.0.0/16 subnet is generally used for local-link addresses. I would guess that your router is blocking that subnet from resolving because you have DHCP enabled.

 

[CarLoad]

Thanks, but I think it's not the routers, since I tried 3 different ones (and yes, I power cycled them as part of testing).
I did try setting a static address (on one NC, in Phiremod) without success. It still gave the same 'Obtaining IP address' message until timeout.
And, on both the routers I tested extensively, laptops, iphones, and crackberries have no problems getting a DCHP assignment.
Strange. And seemingly android specific (our kids' droid phones don't connect either when they visit here... I always thought it was just them!)

 

[wayrad]

Sounds rather like the problem I recently had getting my NC and Android phone to work with a Wiflyer (default IP address 192.168.7.77), except setting a static IP fixed that (after much finagling, since I was unfamiliar with the process). It was strange because Windows, PalmOS, and Maemo devices could acquire an IP address just fine.