Sagemcom suddenly not wanting to allocate IP addresses.

[Sidious]

I think this issue has been mentioned before a year or two ago (maybe more even!)

My Sagemcom has suddenly decided it doesn't want to allocate IP addresses (wired or wifi). I'm currently using it by having to set a static IP on my computer. The internet speed and reliability is as always: very good indeed. So not a throughput problem - just an apparent DHCP issue.

Has anybody any idea/recollection as to what the issue was/is and how it was corrected/circumvented?

When trying to deset-and-reset the LANIP4 settings (to try to humour DHCP into working), the router logs out and doesn't seem to remember/apply the changes.

I wonder if this is a consequence of having the firmware reverted some weeks back (to get my EE phone to have wifi-calling)?

Any ideas people?

Ant (AKA Sid)

[KeithFrench]

Yes I did read what you had said previously about the HG633.

I have not heard of a Ring doorbell causing this, but it would be easier to just turn it off or remove the battery? Is the battery permanently connected? In the ring app can't you just tell it to forget the network?

[Sidious]

@Gliwmaeden2 Yes, I have tried the 30-minute shut down - no different.

@KeithFrench The DHCP is switched-off on the Sagemcom for now, the HG633 acts like DHCP server. Seems to work up to now!

I've been told by someone that a similar issue happened about a year or so ago with some routers from another UK ISP (they can't remember which one). They eventually discovered those having problems had a common denominator; they all had Ring doorbells - like I have! 

It's been suggested that I remove the Ring doorbell unit and take it away from the house (to somewhere outside of my wifi range) and then see if the router behaves as it should

I do hope it's NOT the doorbell though; it's nice to be able to see who's at the door before answering - especially with Halloween coming up!

Thank you again, people

Ant/Sid. 

[KeithFrench]

I did not find any bugs relating to the DHCP server when I tested V206. However, the DHCP server in the router is misbehaving. Is DHCP enabled (OK you may have temporally disabled it whilst using the one in the HG633)? Assuming that it has not been disabled, please can you try a factory default of the router?

[Sidious]

Thanks Keith. It actually happens on any computer/laptop/tablet, Android, iPad, NOW TV sticks, Windows, Linux, wired or wireless, just refuses point blank to allocate an IP to them.

BUT - I have found a workaround which seems to work (up to now...); I've used the old HG633 (just running with no connection to the phone line) to acts as DHCP server.

I've also noticed something else while I was writing this; the Sagemcom received a firmware update yesterday at about 9:22am to version SG4K100206. After ploughing through many router log entries (I was at page 280 something - it was filling one page in about 7 minutes!), I found this:

23.10.2024 09:23:14	Info	SYS	The Modem successfully installed a firmware update
23.10.2024 09:22:47	Info	SYS	The Modem is installing a firmware update

I wonder if SG4K100206 firmware has introduced some bugs/incompatibilities?

Ant (AKA Sid)

[KeithFrench]

I have certainly seen this before, it happened to me! It was down to my WiFi adapter, not the router. I had to uninstall the adapter in my laptop & reinstall it. I can help you prove what the problem is, if you are getting this on a Windows PC.

[Debbie-TalkTalk]

Hi Sidious

I'm sorry to hear this.

This shouldn't be related to the firmware.

Please can you try the 30 minute power down of the router?

[Gliwmaeden2]

Have you tried the simple 30 minute switch off, @Sidious?