Class C private IP space not supported on LAN interface with RO65?

[SteveD]

I tried to configure my Almond+ to replace my existing router configured with a 192.168.xx.xx class C private IP range on the LAN side with a mask of 255.255.255.0. The front panel of the A+ shows the router's LAN address has been changed to 192.168.xx.1, but no device will get an IP address via DHCP on a wired or wireless connection with that IP range. Also tried using LAN address of 192.168.xx.254 with same result. Tried power cycling, still nothing. Tried changing LAN settings in the OpenWRT UI, still nothing. Re-configuring A+ via the front panel to the default 10.10.10.254 LAN setting restores DHCP, but it didn't seem like devices were seeing the outside world until unit was power cycled (sorry to be unclear on this point, but it's been several hours since I did these tests, and I had to re-connect the old router so the family could get their evening Netflix fix). I didn't see this in the known RO65 issues list, but it seems like a pretty major bug, and and unfortunately renders the A+ useless to me until fixed  (I have several servers configured in this IP range, so just changing the LAN IP range isn't an easy/acceptable fix).

[jjoepaulines]

Please follow this thread .... May be it's related to this ..

http://forum.securifi.com/index.php/topic,1549.msg4943.html#msg4943

[SteveD]

Joe, thanks for that reference, could definitely be related as I did change the DHCP range (but failed to note it in my report). Unfortunately I won't be able to test until tomorrow, but will report back what I find.

[SteveD]

Joe,

it was the DHCP bug I was running into. The Almond+ is now acting as my primary router.

Thanks again.

Steve