Ip renew in DHCP

[askpc 15]

Fibaro HCL Lite got problem with get ip adress in dhcp mode.
SImple when i turn on my router home center lite renew adress only when i switch off the power of home center

[T.Konopka 8]

The topic has been moved from "

Please login or register to see this link.

" to "

Please login or register to see this link.

".

 

Temat został przeniesiony z "

Please login or register to see this link.

" do "

Please login or register to see this link.

".

[T.Konopka 8]

13 godzin temu, askpc napisał:

Fibaro HCL Lite got problem with get ip adress in dhcp mode.
SImple when i turn on my router home center lite renew adress only when i switch off the power of home center

Hello,

 

Did you have static IP before and you wanted to change it back to DHCP mode?

[askpc 15]

Specially for FIbaro team screenshot.
Where is FIBARO HOme CEnter ?
All DHCP devices could renew new ip adress after router restart but not F.
Only power off fibaro helps....

Please login or register to see this attachment.

Please login or register to see this attachment.

Edited November 27, 2016 by askpc

[BloWer 4]

I confirm the behaviour: after router restarts the HCL doesn't request new ip -or ip confirmation- to dhcp server

[jakub.jezek 371]

@BloWer,

 

Sollution could be IP reservation within your router. We use that in our Showroom and we have no problem if router goes down.

[BloWer 4]

51 minutes ago, jakub.jezek said:

@BloWer,

 

Sollution could be IP reservation within your router. We use that in our Showroom and we have no problem if router goes down.

 

Yes, I did it but doesn't work. My workaround is to keep IP reservation in DHCP pool and set static IP on HCL.

Maybe it's a router flaw...

[petergebruers 1,268]

A DHCP client gets a lease for a certain amount of time (some servers allow this to be configured). If my memory serves me well, a DHCP client can use the lease for at least half that time, without asking for a new lease. It should stop using the address when the full period passed without getting confirmation from the server. Clients also request a lease when their interface changes from down to up. That might explain your observations... If you restart a DHCP server, it has no impact on the clients. The server does not notify the clients. It is the client that asks if the lease is still valid. If the DHCP server reboots, and also happens to be the ethernet switch connected to your device, the interface might go down then up, triggering the client. If you use an extra switch, that switch will not change status en clients connected to that switch will not request a lease when you reboot the server.

[BloWer 4]

49 minutes ago, petergebruers said:

If you use an extra switch, that switch will not change status en clients connected to that switch will not request a lease when you reboot the server.

 

I agree with you, but HCL is directly connected to the router integrated switch. I need to investigate if during router software reboot the integrated ports remain powered or not.

The router is a custom model built by Huawei (963168_HUAWEIVOX25) for Vodafone costumers.

[plutonium 5]

Any solution for this problem?

[MaTi 29]

What exactly is the problem then? WHat @petergebruers wrote is correct.

Why would you want your HCL to get a new lease from your dhcpd? This makes no sense, unless you made any changes to the lease settings.. Which you normally (almost) never do I would say?

 

Not trying to be stubborn here, just trying to understandint the underlying problem/wish so we can help you..

[plutonium 5]

The problem is if there is power failure and HCL and router go off. Then after power comes back, HCL boots faster than router and does not get any IP and router does not sees it. Then you cant access on HCL through mobile phone. HCL gets new IP only when it is restarted again (router is booted and online).

[AutoFrank 372]

16 minutes ago, plutonium said:

The problem is if there is power failure and HCL and router go off. Then after power comes back, HCL boots faster than router and does not get any IP and router does not sees it. Then you cant access on HCL through mobile phone. HCL gets new IP only when it is restarted again (router is booted and online).

 @plutonium

 

If you assign a static IP on your router /modem for the HCL shouldn't the HCL  connect to the network even if it boots faster

 

I don't have a HCL but I have  HC2 with static ip setup on my dhcp server / gateway and have rebooted  both in many different orders and it never fails to acquire the IP address 

 

Have you tried a different router/modem ? 

[askpc 15]

Solution on DHCP is to Bundle Ip adress on router. (for FIbaro,Ip Camera and other devices steering by plugins with Ip).
I set my devices on dhcp server to static ip.(devices also must set for static ip)
Instruction for settings router.
 

The IP address must be different from the IP address set on the LAN Host Settings area, but they must be on the same network segment.
You can set the IP from webpage manager of Huawei B593,
1. Choose LAN > DHCP Settings.
2. Set the DHCP server to Enable.
3. Set Start IP address.
4. Set End IP address.
5. Set Lease time.
6. Click Submit.

Bundled Address List
1. Choose LAN > DHCP Settings.
2. Click Edit List.
3. Click Add.
4. Set the MAC address and IP Address.
5. Click Submit.

Topic is for close.
*source code-

Please login or register to see this link.

[petergebruers 1,268]

16 hours ago, plutonium said:

The problem is if there is power failure and HCL and router go off. Then after power comes back, HCL boots faster than router and does not get any IP and router does not sees it. Then you cant access on HCL through mobile phone. HCL gets new IP only when it is restarted again (router is booted and online).

 

I understand what you are saying.

 

I have a cable modem, and it is very slow to boot, compared with DSL or generic WiFi routers. It can take 1 to 2 minutes to be fully operational. I think it is typical for this technology, it is called DOCSIS. And indeed, even the basic services like the DHCP server take a long time to start.

 

Please login or register to see this link.

 

I'm not sure it is typical of this technology, it might also be that my provider uses a certain protocol to manage the router, so it checks and possibly updates firmware and configuration over the cable, making it slower than a stand alone WiFi router.

 

I have no reason to doubt what you are saying: if the DHCP client on the HCL gives up after a few attempts and does not try again, it might either have no IP address or it may go to auto IP (PCs do that) 169.254.X.Y or some "rescue" IP like 192.168.81.1. The DHCP client of the HCL is highly configurable, but we do not have access, so I cannot tell with certainty and you cannot change it either. All this would explain why you cannot use your HCL after a global power cut. Some posters suggest adding a reservation on your router, but I bet that does not work, because the DHCP server is simply too slow to start. You might want to report this issue and ask for assistance: mail to [email protected]

 

Because my HC2 is using static IP, I do not have this issue. I never even considered DHCP (or DHCP plus reservation), because I want to access my HC2 over VPN.

 

Is there any particular reason why you do not use a static configuration on your HCL? Or do you also have issues with static IP after a power cut?

[Sjekke 87]

I use fixed IP's for all my devices that may never change (NAS, Camera, HC2....). All other devices are given a IP adress by my own router. I also have a Cable Modem like

Please login or register to see this link.

but "modem only". I have my own ASUS router which is used as DHCP server within a prefdefined range. Untill today I don't have issues when the electricity is cut.

[MaTi 29]

Few comments:

 

1) You should seriously consider using fixed IP adresses, especially if you want to address it in scripting (or in the future)

2) I cannot test whether what you mention is correct, but it is absurd if the HCL does not try again, should it not receive a lease. If a discovery does not lead to an offer, or a request to an ack, it should initiate the whole thing again with a delay of x. This should be default behaviour imho.

3) Alternatively you could see if if you could see if you can make a VD (as LUA is not possible on your HCL) which checks if it can ping your gateway and do a reboot if it cannot. Then initiate this scene on your HCL to let it run every x minutes. Not sure if you can do a ping action from a VD though, but that's a question for someone else who can actually code and is aware of the capabilities

[petergebruers 1,268]

9 minutes ago, MaTi said:

Few comments:

 

1) You should seriously consider using fixed IP adresses, especially if you want to address it in scripting (or in the future)

2) I cannot test whether what you mention is correct, but it is absurd if the HCL does not try again, should it not receive a lease. If a discovery does not lead to an offer, or a request to an ack, it should initiate the whole thing again with a delay of x. This should be default behaviour imho.

3) Alternatively you could see if if you could see if you can make a VD (as LUA is not possible on your HCL) which checks if it can ping your gateway and do a reboot if it cannot. Then initiate this scene on your HCL to let it run every x minutes. Not sure if you can do a ping action from a VD though, but that's a question for someone else who can actually code and is aware of the capabilities

 

I am not sure if your statement "... if the HCL does not try again ..." is correct... Let me explain...

 

I do not have access to the config files, but if this is a standard debian dhcp client (this is speculation!)...

 

a) The DHCP client gives up after 60 seconds. As I said in my previous post, my modem takes 60 - 120 seconds to be fully operational, so that might be marginal and result in no IPV4 address after my internet is fully functional.

b) The DHCP client tries again after 5 minutes.

 

Has anyone tried to wait for at least 7 minutes after power on (1 minute to boot the HCL, 1 minute of failed attempts, 5 minutes pause then retry DHCP). Maybe it comes alive after say 10 minutes?

 

I quote from the dhcpd.conf man page:

 

timeout time;

 

The timeout statement determines the amount of time that must pass between the time that the client begins to try to determine its address and the time that it decides that it's not going to be able to contact a server. By default, this timeout is sixty seconds. After the timeout has passed, if there are any static leases defined in the configuration file, or any leases remaining in the lease database that have not yet expired, the client will loop through these leases attempting to validate them, and if it finds one that appears to be valid, it will use that lease's address. If there are no valid static leases or unexpired leases in the lease database, the client will restart the protocol after the defined retry interval.The retry statement

 

retry time;The retry statement determines the time that must pass after the client has determined that there is no DHCP server present before it tries again to contact a DHCP server. By default, this is five minutes."

[MaTi 29]

@petergebruers makes sense

I am not sure either whether that is true for a fact; I wrote an 'if' in that sentence, as I do not know myself whether it does or does not retry.

I have a rooted hc2 at home, so I could check the config to see whether Fibar did anything with it, or if it is the standard conf..

[petergebruers 1,268]

@MaTi that would be very kind of you. It might settle the issue.

[plutonium 5]

Hi, do we have any progress with DHCP and IP? Just for information....

 

One of my HCL's was in Fibaro for testing and service of mentioned problem. Yesterday I got it back and report said:"There is nothing wrong! All tests passed!" I tested it by myself...same issue. I will try to test it on different router and different location and different service provider