Securifi Community Forum
Securifi Products => Almond+ => Topic started by: mrv777 on January 18, 2015, 06:38:58 pm
-
This has happened to me twice now. I have switched the ip range my Almond+ from 192.168.81.xxx to 192.168.13.xxx. 99% of the time the computers get the correct IP addresses, but twice now the computers start getting IP addresses that start with 192.168.81 and I have to wait until the DHCP leases expire before the Almond+ sends out new (correct ones)
-
Hi there....
Well we know the issue, we are going to fix it in future firmware. This issue is only coming from wired connection, you can release/renew the ip from wired client.
Use following commands on your client:-
For windows:- Open cmd then type --- >ipconfig/release>ipconfig/renew
For Linux:-
dhclient -r interface
Where interface is the device you want to get a new address for.
like dhclient -r eth0.
or
/etc/init.d/networking restart
or
ifdown eth0; ifup eth0
or
If you're using the dhcpcd tool then:
dhcpcd -k interface
dhcpcd interface
or you can do one thing after changing LAN segment, reboot your almond +, it will fix the issue.
-
Thank you for chiming in, but my issue seems a little different. My issue is on both wired and wireless connections. If I manually type in an IP address, everything works fine, but DHCP is sending out incorrect addresses to all clients, and it doesn't seem to even report it is on and/or giving out addresses. I've tried restarting the DHCP server, restarting the router, releasing and renewing the IP address on a windows and OSX client, updated the router to the beta firmware, left the router unplugged for a minute, restarted the modem, and left everything alone over night to see if it would start giving out correct addresses in the morning. Still not working though. I also tried changing the DHCP server to go up to 151 to force a change and hope it would reload the DHCP server again. I'm including some screenshots to show what I'm talking about.
Edit: Also, all my static leased ip address computers lost their correct addresses too. This is very annoying and inconvenient since I have to manually set each one now to get it online
(http://s3.postimg.org/b205jaf6n/Screen_Shot_2015_01_19_at_6_59_51_AM.png) (http://postimg.org/image/b205jaf6n/)
(http://s3.postimg.org/kb2bteo2n/Screen_Shot_2015_01_19_at_7_00_08_AM.png) (http://postimg.org/image/kb2bteo2n/)
(http://s3.postimg.org/3w3t33gpr/Screen_Shot_2015_01_19_at_7_00_50_AM.png) (http://postimg.org/image/3w3t33gpr/)
(http://s3.postimg.org/hr6ozb0in/Screen_Shot_2015_01_19_at_7_02_15_AM.png) (http://postimg.org/image/hr6ozb0in/)
-
This topic can be closed as I was able to resolve this. It was because of another DHCP server getting turned on