Daily network reset required, reason unknown.

[Shadow_Storm56]

I had some network issues previously which ended up being a conflict of a couple of devices that I fixed. One thing though that seems to happen now is after as little as 1 day or as long as a week is a few devices will start disconnecting and slowly go until most of them are disconnected. So in order to simplify things on daily resets I just added an outlet timer and now everything works great! Problem is this is not a normal thing to do, maybe my lease time is too long and as devices move around I run out of addresses over time? Or maybe it has to do with the main wifi transmitter which I can't connect to the admin page because the network did not like the static address I used for it.... 

 

Thinking out loud as I type makes me think it could be lease time...

[seanondemand]

This is an equipment issue and whatever is causing it should get replaced. Are all your devices connected to your ISP-provided gateway? Or is it your own networking gear?

[Shadow_Storm56]

My stuff, I'm unsure of the cause

6 hours ago, seanondemand said:

This is an equipment issue and whatever is causing it should get replaced. Are all your devices connected to your ISP-provided gateway? Or is it your own networking gear?

 

[wseaton]

I would try only rebooting specific devices and rule out what the actual culprit is. At some point by not rebooting certain things the problem wont go away, and bingo, you've found the problem child.

 

DHCP conflicts are usually visible because most operating systems will warn you.

 

Typically this behavior indicates a memory leak in a device, and at some point the stack collides with something it shouldn't and you have to power cycle to get things working again. Had this happen on anything.

 

*Usually* this happens on cheaper consumer devices that do a lot of complicated network translation. Typically Router / WiFi combos, but I've had the same issue with Enterprise level Firewalls and even VMware (5.5 vs iLO memory leak). Your router is my first suspect though.

 

I use the lamp timer trick on small businesses with non managed modems. Turning that modem off and on each night cleans up a lot of potential issues down the road and keeps ISP network changes always in sync. 

[Shadow_Storm56]

7 hours ago, wseaton said:

I would try only rebooting specific devices and rule out what the actual culprit is. At some point by not rebooting certain things the problem wont go away, and bingo, you've found the problem child.

 

DHCP conflicts are usually visible because most operating systems will warn you.

 

Typically this behavior indicates a memory leak in a device, and at some point the stack collides with something it shouldn't and you have to power cycle to get things working again. Had this happen on anything.

 

*Usually* this happens on cheaper consumer devices that do a lot of complicated network translation. Typically Router / WiFi combos, but I've had the same issue with Enterprise level Firewalls and even VMware (5.5 vs iLO memory leak). Your router is my first suspect though.

 

I use the lamp timer trick on small businesses with non managed modems. Turning that modem off and on each night cleans up a lot of potential issues down the road and keeps ISP network changes always in sync. 

Outlet/lamp timer was what I just added as a daily to weekly reboot seems to keep things running well, so automatically rebooting everything daily should do well. I can narrow it down to either the main router or the main wifi source.... unlikely to be just the switch I figure but thoes also get rebooted from this as well. On occasion but very rarely it happens faster than a day so next time I see that ill reboot just the switches and then if that dosen't work it's probably the main router that has problems after extended runs