DHCP issue - Lease

[Comp0za]

Hi! I'm having this DHCP issue twice now. It seems that reserving the IP adress, and change to .50 doesn't work in long term. Before this issue started to occure, which previous firmwares didn't have this issue? I don't want to refund this router, I really do love the router, but the DHCP issues is a real router breaking bug. 

[Netduma Fraser]

Testing my memory here but you could try .40 or .32, I don't seem to recall the issue on those specifically

[Comp0za]

19 minutes ago, Netduma Fraser said:

Testing my memory here but you could try .40 or .32, I don't seem to recall the issue on those specifically

There is info about .50 in all over the places, here and Netgear.com.

So you are telling me that .50 was the wrong one all the time????

[Comp0za]

Fraser, you are serious, right?

[Netduma Fraser]

I was referring to the firmware versions that you asked about

[Comp0za]

Oh, okey, sorry about that. But is it safe to revert, considering the latest security fixes isn't in the previous firmwares?? 

[Netduma Fraser]

19 minutes ago, Comp0za_ said:

Oh, okey, sorry about that. But is it safe to revert, considering the latest security fixes isn't in the previous firmwares?? 

In terms of downgrading its fine but regarding the security fixes I can't indicate either way really, that's up to you if you're willing to risk it. 

[Comp0za]

7 minutes ago, Netduma Fraser said:

In terms of downgrading its fine but regarding the security fixes I can't indicate either way really, that's up to you if you're willing to risk it. 

Oki. Mean while, I have disabled DHCP instead and manually put internet connection to all my devices. Hopefully, this will resolve the issue.

[Comp0za]

soo far, I haven't experienced disconnection. But I have one question. The Logs seems to reset withing 12 hours, or maybe 24 hours, (you could correct me), so I wonder why it does like that?

[Netduma Fraser]

30 minutes ago, Comp0za_ said:

soo far, I haven't experienced disconnection. But I have one question. The Logs seems to reset withing 12 hours, or maybe 24 hours, (you could correct me), so I wonder why it does like that?

Great news! Usually it only occurs after a reboot, does the uptime reset after the log resets as well?

[Comp0za]

2 hours ago, Netduma Fraser said:

Great news! Usually it only occurs after a reboot, does the uptime reset after the log resets as well?

No actually not. 

[Netduma Fraser]

I can't see anything internally about this, it may be something on the NG side - does it also clear in the logs in Settings? It may be clearing out automatically to preserve memory

[Comp0za]

2 hours ago, Netduma Fraser said:

I can't see anything internally about this, it may be something on the NG side - does it also clear in the logs in Settings? It may be clearing out automatically to preserve memory

Yes, in the settings as well. Oh well, okie.

[Bert]

The better strategy for this is actually keeping DHCP active next to your fixed pool.

 

Ie I have fixed IP's for everything that is fixed like PC's and so on. But you want a small range for devices that cannot set fixed IP's or guests etc.

[Comp0za]

1 hour ago, Bert said:

The better strategy for this is actually keeping DHCP active next to your fixed pool.

What is a fixed pool?

[Bert]

Just means the fixed adresses you assign.

 

Say for instance you have the following:

 

DHCP:

192.168.1.20-49

 

Fixed:

PC's: 192.168.1.100-109

Servers: 192.168.1.110-119

Media devices: 192.168.1.120-129

IoT: 192.168.1.130-159

 

If you are using fixed adresses you have to keep track of what you put where to avoid internal conflicts. That's why a small DHCP pool for temporary devices is handy. Also nowadays some devices especially IoT will come without the option to set a fixed IP so you will have to do that through your router's DHCP reservation function.

[Comp0za]

Yes, disabling the DHCP and assigning IP adress, submask, dns and gateway to each devices, has resolved the issue, it's tottaly gone now! No internet disconnetion since then.