Securifi Community Forum
Securifi Products => Almond+ => Topic started by: SteveD on September 02, 2014, 09:15:00 pm
-
As I posted on the Almond+ bug hunt board (http://forum.securifi.com/index.php/topic,1719.0.html (http://forum.securifi.com/index.php/topic,1719.0.html)), I am unable to configure the LAN settings on my A+ to use the 192.168.xx.xx IP range to replace my existing router. With the A+ LAN interface set to 192.168.xx.1, or even 192.168.xx.254, no wired or wireless devices will pick up an address via DHCP even after a restart. Using the front panel to re-configure the A+ to the default 10.10.10.254 router LAN address restores DHCP. Before I spend any more time researching the problem while waiting for a response from Securifi I thought I'd ask other A+ owners if they'd successfully changed the LAN settings on theirs. Thanks.
-
I have successfully changed the IP address of the router to 192.168.1.1 and DHCP starts at 192.168.1.100. Everything from wired to wireless has been working fine for 2 weeks now
I can't remember if I made the change with the touch screen or the webUI but I think I used the touch screen.
-
Yes, I've done so via the lcd and web interface. I'm currently using 192.168.5.x
-
Are you restarting the almond or your computer?
Remember that your computer won't try to grab a new IP if the lease for the one it has hasn't expired yet.
Have you tried a release/renew on the client?
-
Thanks for the feedback everybody. Thanks to a comment from Joe in the Bughunt forum I now know this may actually be the DHCP bug where the DHCP Server field "Number of Leases" should actually be "End Address" - see thread http://forum.securifi.com/index.php/topic,1549.msg4943.html#msg4943 (http://forum.securifi.com/index.php/topic,1549.msg4943.html#msg4943). I'll report back tomorrow after I've had a chance to test.
-
As I posted on the Almond+ bug hunt board (http://forum.securifi.com/index.php/topic,1719.0.html (http://forum.securifi.com/index.php/topic,1719.0.html)), I am unable to configure the LAN settings on my A+ to use the 192.168.xx.xx IP range to replace my existing router. With the A+ LAN interface set to 192.168.xx.1, or even 192.168.xx.254, no wired or wireless devices will pick up an address via DHCP even after a restart. Using the front panel to re-configure the A+ to the default 10.10.10.254 router LAN address restores DHCP. Before I spend any more time researching the problem while waiting for a response from Securifi I thought I'd ask other A+ owners if they'd successfully changed the LAN settings on theirs. Thanks.
My LAN access on my A+ is a 192.168.1.x range, but i don't use the A+ for DHCP though.
-
Probably the easiest way to change this is ssh into the a+ and edit /etc/config/network and /etc/config/dhcp
Full explanation of the format of these files is found here:
http://wiki.openwrt.org/doc/uci/network
-
I had no problem switching from the default 10.10.10.xxx to 192.168.1.xxx. THe A+ replaced my current router so it does everything. Its the only router in my network
-
It was the DHCP lease count vs. DHCP range end bug I was running into. Once I accounted for that, the A+ came up just fine as my primary router.