New to this forum. Major problem

[ColinTaylor]

Here is the pastebin log. Wow, lots of entries............ Dang, I hope my router did not crap out. Guess the next thing to do is reset the router, what do you think?? I also have a spare router to try.

There are no messages in the log file since last night up until the point when you rebooted it. So no obvious clues there. Although we now know that the router isn't crashing, etc. So it looks unlikely that it's a router issue. But we're running out of alternatives so if you want to swap the router that could confirm/deny whether that is the issue.

Did the devices come back online after you rebooted the router?

Next time some of your devices at the entertainment go offline can you try pinging their IP addresses from the router's interface (Network Tools > Network Analysis) instead of using the scanner app.

 

[Ronnie Bailey]

There are no messages in the log file since last night up until the point when you rebooted it. So no obvious clues there. Although we now know that the router isn't crashing, etc. So it looks unlikely that it's a router issue. But we're running out of alternatives so if you want to swap the router that could confirm/deny whether that is the issue.

Did the devices come back online after you rebooted the router?

Next time some of your devices at the entertainment go offline can you try pinging their IP addresses from the router's interface (Network Tools > Network Analysis) instead of using the scanner app.

I went ahead and swapped the Asus router for my Trendnet TEW-818DRU (AC1900). Most of the items did not come back online, I had to power off/on the devices that did not connect to the network. I will be monitoring them to see if any drops off line tonight. Biggest pain right now, is getting my wireless smart devices working again. My google controlled devices....... what a pain........

I try to ping the devices if it happens again..

 

[Ronnie Bailey]

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.

 

[Ronnie Bailey]

Also, should I NOT post a pick of my MAC addresses???

 

[degrub]

Also, should I NOT post a pick of my MAC addresses???

Yeah, not a good idea in general for mac and ip addresses.

When you reserve a range of addresses for dhcp, those are for new devices connecting that have no ip address eg a friend visiting or devices you don’t care what the address is. The dhcp server in the router will assign from that range starting from the lowest number.

If you assign a static address to a device in the device config. that is within the range the dhcp server is using, a conflict can occur if the address is assigned to another device by the dhcp server.

Same thing if you are assigning a static address by mac address reservation.

You want those reserved addresses outside of the range dhcp server is using

 

[ColinTaylor]

I did wonder what you were doing about your IP addresses. I don't see any DHCP messages in your log so I assume they are being suppressed (either by choice or default).

The rules regarding whether DHCP reservations should be inside or outside the "pool" of addresses can vary between manufacturers . But on the Asus there is an assumption that the reserved addresses will be inside the pool. However this is not enforced so in reality they can be inside or outside.

Most manufactures have the reserved addresses inside a pool, leaving the addresses outside free to be used on devices that have to have their address manually (static) configured on their network interfaces (infrastructure servers for example).

So that's a long-winded way of saying that what you're doing is perfectly normal. You just have to make sure that the DHCP address pool is large enough for all your reservations plus any other DHCP clients that may want to connect.

Regarding your MAC addresses, personally I see absolutely no security reason to obfuscate them as unlike your WAN IP address they are not accessible from outside your LAN. Another forum poster strongly disagreed with me (not about the accessibility) because he felt that if he posted the same MAC addresses in other forums people (?) might be able to associate his user account on one forum with his user account on another by matching the MAC addresses he posted. So his concern was not about whether his devices would be hacked but how to increase his anonymity on the web.

 

[degrub]

You may not have seen an issue yet since your lowest reserved address is 25 above the start of the dhcp server range.
You can check for a screen that lists the addresses the dhcp server has assigned and see if there are any conflicts.

 

[ColinTaylor]

You may not have seen an issue yet since your lowest reserved address is 25 above the start of the dhcp server range.
You can check for a screen that lists the addresses the dhcp server has assigned and see if there are any conflicts.

What sort of conflict were you thinking of?

 

[degrub]

Tcp/ip address same for two devices on same subnet.

 

[ColinTaylor]

Tcp/ip address same for two devices on same subnet.

But that won't happen (at least on an Asus) because dnsmasq won't give out any address that has already been issued or is reserved.

BTW non-reserved addresses are not issued sequentially but pseudo-randomly unless you set the dhcp-sequential-ip option.

 

[Ronnie Bailey]

Yeah, not a good idea in general for mac and ip addresses.

When you reserve a range of addresses for dhcp, those are for new devices connecting that have no ip address eg a friend visiting or devices you don’t care what the address is. The dhcp server in the router will assign from that range starting from the lowest number.

If you assign a static address to a device in the device config. that is within the range the dhcp server is using, a conflict can occur if the address is assigned to another device by the dhcp server.

Same thing if you are assigning a static address by mac address reservation.

You want those reserved addresses outside of the range dhcp server is using

To make easier for me to understand, in the second pic of reserved address, are they wrong??

 

[Ronnie Bailey]

If you assign a static address to a device in the device config. that is within the range the dhcp server is using, a conflict can occur if the address is assigned to another device by the dhcp server.

You want those reserved addresses outside of the range dhcp server is using

Does your question mean, *** have I set a static IP on any of the devices itself** ?? Example, did I set a static IP on my computer or one of my Android boxes?? No, I have not, at least not intentionally.

 

[Ronnie Bailey]

I want to have a static address on my 3 NAS's because my media is stored on them, and Kodi, Emby and Plex need a fixed IP address to **see** where my media is located on my network.

I also **think** I need my security IP cameras on a static IP so I can access them externally.

I have ONE CoreELEC box that is my DVR server, so it has to have a static address so I can access it from any device on my network.

Oh, and I have to have a static IP address for my two **networked** HDHomeRun OTA tuners.

 

[ColinTaylor]

It's less ambiguous (but more long-winded) to refer to IP addresses as "reserved" (in DHCP) or "static" (manually configured on the client's network interface). Unfortunately the term "static" is frequently misused which can sometimes lead to confusion.

 

[Ronnie Bailey]

It's less ambiguous (but more long-winded) to refer to IP addresses as "reserved" (in DHCP) or "static" (manually configured on the client's network interface). Unfortunately the term "static" is frequently misused which can sometimes lead to confusion.

Thanks for the clarification.

 

[Ronnie Bailey]

Just checked, and all my devices that should be running 24/7, are still connected to my network. I will see in the morning, if replacing the router solves the issue of my devices dropping off the network. Or maybe the ghost in my house takes the weekends off.

 

[Ronnie Bailey]

Today, Sunday Sept. 23, same thing with different router, devices lost network connection. Security cam went offline at 1:30 am last night. Only way to bring them back online is power off/on.

Right now, I am clueless on what the issue is. It is NOT the router, NOR is it any of the switches, I replaced/swapped each one that is in the chain.

Guess now, I will have to remove every device and add them one at a time. There must be something with one of these devices that is causing the issue, but no idea what.

Using the command prompt in Windows, I pinged the devices that were off line, and 192.168.10.65 is my IP cam.

Pinging 192.168.10.65 with 32 bytes of data:
Reply from 192.168.10.80: Destination host unreachable.
Reply from 192.168.10.80: Destination host unreachable.
Reply from 192.168.10.80: Destination host unreachable.
Reply from 192.168.10.80: Destination host unreachable.

Any more ideas??

Edit: The IP cam is connected to the same 4 port POE switch as my other 3 IP cams, but they NEVER loose network connection. This IP cam just started loosing network connection about a couple of weeks ago.

 

[ColinTaylor]

Guess now, I will have to remove every device and add them one at a time.

I think so. I would also be suspicious of your power sources. How reliable is your mains supply? Could you be getting power spikes, either from outside or from something like a fridge/freezer compressor turning on. Maybe one of the power adaptors is failing.

Using the command prompt in Windows, I pinged the devices that were off line, and 192.168.10.65 is my IP cam.

Pinging 192.168.10.65 with 32 bytes of data:
Reply from 192.168.10.80: Destination host unreachable.
Reply from 192.168.10.80: Destination host unreachable.
Reply from 192.168.10.80: Destination host unreachable.
Reply from 192.168.10.80: Destination host unreachable.

The idea was to test the link from the router to the client, not from another client. But I guess that was not possible because you changed the router.

Edit: The IP cam is connected to the same 4 port POE switch as my other 3 IP cams, but they NEVER loose network connection. This IP cam just started loosing network connection about a couple of weeks ago.

Maybe one of the POE devices is faulty and sending power surges though the switches. See that straw, that's me clutching at it.

 

[Ronnie Bailey]

One more piece of information. I did NOT set a "reserved" IP address for my Vorke V2 (Windows 10 microPC that is my Emby and Plex server). Yesterday when I swapped routers, it kept the same IP of 192.168.88, and it stayed that way for numerous reboots of the router. Today, it obtained a new IP address of 192.168.10.48. Same thing with my WD NAS, it has always had an IP of ...111, today it has .... 45.

It seems to me that when I give a device a different IP address, I have to reboot the device for the IP change to take place. That would indicate a power loss every night, that MAY cause my issues.

So, if it is a power issue, what is in common?? The IP cam is in the basement, obviously with it's own power source.

The other devices that keep losing their network connection are at my entertainment center, but on different surge protectors.

Any thoughts???

Another thought, if my Vorke V2 loses power, it does NOT come back on, I have to turn it back on. So, how did the IP change on it?? I never power it off. It draws very little power.

 

[ColinTaylor]

It seems to me that when I give a device a different IP address, I have to reboot the device for the IP change to take place.

Yes, this is normal. I'd assumed that you were using the same reserved addresses for any devices that needed them. Any non-reserved clients will get a pseudo-random address based on a hash of their MAC address. Because you changed routers the algorithm that generates the number has probably changed which is why you get a different number when you power cycle the client.