New to this forum. Major problem

[Ronnie Bailey]

Similar to what @degrub was alluding to make sure your devices don't have more than one network interface connected at the same time, i.e. Ethernet and WiFi. This can create network loops and broadcast storms.

That is a good point, I will take a look at that. Thanks

 

[Ronnie Bailey]

Took my 3 devices that were running a version of Linux offline yesterday, and all my other devices did NOT drop off the network.

My IP security cam and my networked TV tuner both stayed online.

It appears that one of the Linux boxes is causing my router to go nuts. I will have to find out which one and then try to find WHY it would cause these issues.

I will leave them off the network for the next 3 days and see what happens. Tomorrow, I will put my Asus router back into service and my Trendnet router back into storage.

Any thoughts on how my Linux boxes can **corrupt** my router??

thanks.

 

[ColinTaylor]

Any thoughts on how my Linux boxes can **corrupt** my router??

There's nothing so far so suggest it's effecting your router, let alone "corrupting" it. My (tentative) guess at the moment would be that one of those devices is flooding your LAN with traffic causing issues for some of the clients. At the risk of repeating myself for the 5th time , check the logs on the effected client devices.

As previously mentioned network loops can cause broadcast storms, and there was a similar issue recently with Chromecast devices.

 

[Ronnie Bailey]

There's nothing so far so suggest it's effecting your router, let alone "corrupting" it. My (tentative) guess at the moment would be that one of those devices is flooding your LAN with traffic causing issues for some of the clients. At the risk of repeating myself for the 5th time , check the logs on the effected client devices.

As previously mentioned network loops can cause broadcast storms, and there was a similar issue recently with Chromecast devices.

"At the risk of repeating myself for the 5th time , check the logs on the effected client devices". So, you are saying when I start adding back my devices that I have remove, and the problem recurs, I should check the logs on the device/s that loose network connection?? I am not sure how to do that, I will have to research the particular device, like my IP camera or ATSC networked tuner.

 

[Ronnie Bailey]

"My (tentative) guess at the moment would be that one of those devices is flooding your LAN with traffic causing issues"

That statement makes sense, but I can't grasp mechanics of it. I haven't found the culprit yet, but perhaps the device that is also my DVR is causing it?? It has to go on the web each night to grab the EPG..... I am using tvheadend DVR server on my Linux box. I don't know how a network, works internally, so flooding is abstract to me.

 

[ColinTaylor]

"At the risk of repeating myself for the 5th time , check the logs on the effected client devices". So, you are saying when I start adding back my devices that I have remove, and the problem recurs, I should check the logs on the device/s that loose network connection?? I am not sure how to do that, I will have to research the particular device, like my IP camera or ATSC networked tuner.

Sort of. What I meant was, in post #62 you said at least 3 of the effected devices were "PURE LINUX". As such they should have the standard Linux log file that you could go and look at now. No need to wait until the problem reoccurs.

Re-reading that post again I notice that you also said they were Android devices, so they're not "PURE LINUX". Even so they're similar enough that I'd expect them to also have the same sort of log file. Whether or not it would persist after the device was rebooted I couldn't say though.

That statement makes sense, but I can't grasp mechanics of it. I haven't found the culprit yet, but perhaps the device that is also my DVR is causing it?? It has to go on the web each night to grab the EPG..... I am using tvheadend DVR server on my Linux box. I don't know how a network, works internally, so flooding is abstract to me.

The easiest thing is to do what you're already doing. Just add devices back one at a time until you find the culprit. Then you can start to work out the cause.

 

[Ronnie Bailey]

I am running LibreELEC or derivative of on 3 boxes and Ubuntu 16.04 on 3 other devices.

LibreELEC is a Linux distribution or “Linux distro,” an operating system based on the Linux kernel. Specifically, it’s an operating system designed to load just enough software to allow a computer to run Kodi.

 

[ColinTaylor]

I am running LibreELEC or derivative of on 3 boxes and Ubuntu 16.04 on 3 otherdevices.

OK, so not Android. So there should be some log files in /var/log, probably called syslog and/or messages.

 

[Ronnie Bailey]

Was gone for about 3 or 4 hours, when I got home, my IP cam and my networked TV tuner were off the network again....... Grrrrrrrrrrrrr.. None of the Linux devices were connected.

Guess I have to start removing ONE device at a time until I find out what is going on. The IP camera is fed from a cat 6 cable that goes from the router to the 4 port POE switch. The other 3 IP cams that are on that same POE switch, and they NEVER go offline. But the one that goes off line is a Dahau brand and the only one of that brand that I have.

The tuner that lost network connection is connected to my new 16 port Ethernet switch, that is fed by a cat 6 cable running from my router to the 16 port switch. None of the other devices go off the network.

I THINK I can eliminate the router (swapped 2 days ago, and same problem). I THINK I can eliminate the 16 port switch because it is new that purchased a few days ago, thinking it was the problem.

I don't see any logs from either the IP cam or the networked tuner.

Using the Advanced IP Scanner Windows app, I don't see any overlapping IP or MAC addresses.

Again, this issue just started in the last week or two..

 

[Ronnie Bailey]

Got up this morning and my TV tuner and IP camera were dropped off the network again..I am beginning to think that I am going to have to call in the Ghostbusters.........

I am running out of things to disconnect.

I have taken 10 Android devices, running different OS's out of the system. I also took one of my Synology NAS's out of the system.

I have 3 Windows 10 (2 are microPC's) still connected to the system.

I have one Synology and one WD NAS's still connected to the system

I have 2 HDHomeRun OTA networked turners, still connected to the system.

I have ONE Ooma VOIP phone connected to my system

I have 5 (one of which keeps dropping off the network) IP security cams connected to my system.

I don't know what to remove next.

It seems that both the tuner and IP camera drop off at the same time, (only guessing about the time). But whenever I check, and one is offline the other one is offline.........

I guess, the next time they drop off the network, I will take the IP cam out of the system and see if the networked tuner still drops connection.

I tried to move those devices from the reservation group, but the router won't allow it. In other words my group is from 40 to 199, I tried to move the IP from the cam of 65 to 38, but the router won't let me.

 

[degrub]

did you delete the reservation first ?
You probably want the device not connected when you make the change.
Addresses usually "stick" in devices until it requests a new one.
Does the device have a static address in it's config or does it use DHCP to get an address ?
If it uses DHCP, disconnect and power cycle it. Change the reservation and then reconnect to network.

 

[Ronnie Bailey]

In the configuration of my IP cam, the IP address is set to static. I will give your instructions a try.

did you delete the reservation first ?
You probably want the device not connected when you make the change.
Addresses usually "stick" in devices until it requests a new one.
Does the device have a static address in it's config or does it use DHCP to get an address ?
If it uses DHCP, disconnect and power cycle it. Change the reservation and then reconnect to network.

In the configuration of my IP cam, the IP address is set to static. I will give your instructions a try.

Do you think it will make a difference IF I can set the IP address outside of the reservation list?? If I do set it outside of the reservations, will it acquire a different IP address on a reboot??? That IP camera MUST maintain the same IP address, so I can access it from out of my local network.

 

[ColinTaylor]

Do you think it will make a difference IF I can set the IP address outside of the reservation list?? If I do set it outside of the reservations, will it acquire a different IP address on a reboot??? That IP camera MUST maintain the same IP address, so I can access it from out of my local network.

TBH it doesn't make much difference which way you do it. Choose a system that make sense to you so that you remember it. If you set the IP address on the camera itself it will always use that address. The only thing you need to do is ensure that no other device uses the same address. There are two ways to achieve this:

a) Because the camera is manually configured the router's DHCP server knows nothing about it. To stop the DHCP server giving the same address to one of its clients just set the camera to an address outside of the DHCP pool. If you have any other devices you want to manually configure you need to remember what addresses you have already used and give them different ones.

b) Alternatively you could create a "normal" DHCP reservation on the router for the camera even though the camera isn't a DHCP client. What this does is create a "dummy" entry in DHCP for the camera's IP which prevents that address being given to another device. This can be used as a way of remembering what IP addresses you have used (an aide-mémoire). But if you change the static IP address on the camera you must remember to make the same change on the router, it won't do it for you automatically.

 

[sfx2000]

One question. Perhaps I am creating my own problems. I like to "reserve" (like a static) IP addresses for some/most of my devices. My networking knowledge is limited, and maybe that is causing my problems.

I will try to explain what I am doing, and it may be all wrong. I set parameters for DHCP Server Setting and within those settings, I reserved my device IPs. Should I have set my "reserved" IPs outside of those parameters? I have them inside those parameters.
I attached photos to show what I mean.......

Thanks for your help.
View attachment 14538

View attachment 14539

Hint... drop the DHCP lease time down - I'd suggest 7200 (it's a value in seconds)

Hint 2 - really look at the need for reservations in the first place - you don't need so many... if I recall correctly, there's a limit there, perhaps 16 in total with AsusWRT?

Anyways, a DHCP client is going to ask/request the address it already has, which negates many of the reasons for reservations in the first place.

 

[Ronnie Bailey]

TBH it doesn't make much difference which way you do it. Choose a system that make sense to you so that you remember it. If you set the IP address on the camera itself it will always use that address. The only thing you need to do is ensure that no other device uses the same address. There are two ways to achieve this:

a) Because the camera is manually configured the router's DHCP server knows nothing about it. To stop the DHCP server giving the same address to one of its clients just set the camera to an address outside of the DHCP pool. If you have any other devices you want to manually configure you need to remember what addresses you have already used and give them different ones.

b) Alternatively you could create a "normal" DHCP reservation on the router for the camera even though the camera isn't a DHCP client. What this does is create a "dummy" entry in DHCP for the camera's IP which prevents that address being given to another device. This can be used as a way of remembering what IP addresses you have used (an aide-mémoire). But if you change the static IP address on the camera you must remember to make the same change on the router, it won't do it for you automatically.

Thanks for that valuable information. At this time, I am almost positive my issue is software and NOT hardware.

 

[Ronnie Bailey]

Hint... drop the DHCP lease time down - I'd suggest 7200 (it's a value in seconds)

Hint 2 - really look at the need for reservations in the first place - you don't need so many... if I recall correctly, there's a limit there, perhaps 16 in total with AsusWRT?

Anyways, a DHCP client is going to ask/request the address it already has, which negates many of the reasons for reservations in the first place.

It is set to 86400, so I dropped it down to 7200 per your recommendation. I don't understand what you are telling me that there is a limit if 16 that can be in the reserved IP group. I am NOT using Asus WRT.

 

[sfx2000]

It is set to 86400, so I dropped it down to 7200 per your recommendation. I don't understand what you are telling me that there is a limit if 16 that can be in the reserved IP group. I am NOT using Asus WRT.

I may have mispoke - digging around, the list size for dhcp reservations is 32 according to this entry - I don't think that has changed over time...

So from DHCP, 23 clients should be more than covered...

What the number of clients per connection...

1) Wired
2) 2.4 GHz
3) 5 GHz

 

[Ronnie Bailey]

I may have mispoke - digging around, the list size for dhcp reservations is 32 according to this entry - I don't think that has changed over time...

So from DHCP, 23 clients should be more than covered...

What the number of clients per connection...

1) Wired
2) 2.4 GHz
3) 5 GHz

Approx. 25 wired and 4 or 5 on 2.4Ghz. None on 5Gz. Right now, all have been taken off my network except. My Synology and WD NAS's , desktop, and 2 microPC's running windows 10, 2 HDHomeRun networked tuners, 5 IP security cams, and one Ooma VOIp, that are all connected via Ethernet cable. Oh, and one Android box connected by
Ethernet.

I have a Leviton WiFi smart switch running on 2.4 gh WiFi, and my cellular phone also on 2.4 Gh Wifi.

I think that is pretty much it, for devices that I have connected.

 

[Ronnie Bailey]

It is set to 86400, so I dropped it down to 7200 per your recommendation. I don't understand what you are telling me that there is a limit if 16 that can be in the reserved IP group. I am NOT using Asus WRT.

I just checked my router settings and I have 22 devices setup with ""static"" IP addresses.

 

[Ronnie Bailey]

Here is my router settings for reserved IP addresses.