[michaeljc70]

I have 3 Pis running Kodi for several years. They are using LibreElec. In the last few weeks one of them keeps losing its network connection.  Generally to fix it, I have to reboot the router. Sometimes I also have to reboot the Pi.  Sometimes both.  It seems like the network connection is there when everything is reset but is quickly lost.  It is hardwired but when I turn that off and use the wifi connection, the same thing happens.  Any ideas on what could be causing this?  

Sometimes it shows a blank IP when not working and sometimes it shows an IP under System Info. 

My network seems fine otherwise with no issues with other devices. 

I tried an IP reservation for the Pi but that didn't help.

[Klojum]

Is the "Wait for network" option enabled? That should ensure getting the IP address at boot time.

[michaeljc70]

Is the "Wait for network" option enabled? That should ensure getting the IP address at boot time.

I didn't have that on. I turned it on and still have the problem.

The last time it said the ip was 10.0.0.11 (which is what I reserved for it), but it couldn't access my NAS or the internet.

[DarrenHill]

In this case, if you have a spare SD card I'd be tempted to burn a copy of Raspbian onto it and see if that has similar connection issues.

From what you've described I would use that to determine if it's a software or hardware issue, and then take the investigation from there.

[michaeljc70]

In this case, if you have a spare SD card I'd be tempted to burn a copy of Raspbian onto it and see if that has similar connection issues.

From what you've described I would use that to determine if it's a software or hardware issue, and then take the investigation from there.

Thanks.  I tried a new sd card with a fresh install and same problem.  I changed out the ethernet cable from the wall to the Pi. Same issue.  Now I am trying a different Pi to see if it is the wiring in the wall or possibly the switch port it is ultimately plugged into or if the Pi board is bad.  My guess is the Pi board, but we'll see.

[DaVu]

The last time it said the ip was 10.0.0.11 (which is what I reserved for it), but it couldn't access my NAS or the internet.

I guess you reserved it at the router? Have you tried it the other way round? Set a static IP on the Pi itself?

Also interesting that ppl are using private class A networks for their home. Aren't ~250 IPs/possible devices enough ? Or do you really need "16777216" IPs?

[michaeljc70]

The last time it said the ip was 10.0.0.11 (which is what I reserved for it), but it couldn't access my NAS or the internet.

I guess you reserved it at the router? Have you tried it the other way round? Set a static IP on the Pi itself?

Also interesting that ppl are using private class A networks for their home. Aren't ~250 IPs/possible devices enough ? Or do you really need "16777216" IPs?  

Yes, I was reserving it on the router.  I swapped out the Pi with another one and it worked fine.  The chip must be going bad on the Pi board.  I am replacing the Pi board.  

I thought class addressing ended in the 1990's.  It is just a number. I don't like to do what everybody else does. 

[DarrenHill]

Thanks for coming back and concluding that one. It was kinda what I suspected from what you described, but needed some testing to prove.

Thread marked solved.