ChrisG82

Netduma soon they say, Yet what does that truly mean? Time slips away fast. 😁

I will hope a „Netduma soon“ is not a „Blizzard soon“ 😉

Here: Post with Downloadlink v.41

If we assume that the hardware is not defective, it could theoretically only be the software somewhere. Perhaps @Netduma Frasercan ask the development department about this.

That should definitely be the normal case. I can't really grasp what's going wrong with your Modem/R3 at the moment either

Look what i found: WAN Loss on ARRIS TM3402

No, this is not normally necessary. But you could have used it to see whether there is a technical hardware incompatibility between your modem and the R3. Or whether the R3 is also losing the connection via the switch.

Do you have a simple small network switch that you can connect between the modem and the R3?

Then try Modem —> R3 with no changes in the config…. Use the Cable that came with R3: Modem —> WAN Port R3 —> Reboot both

Okay, so that means that everything is running smoothly with the setup (modem -> ASUS -> R3). I would suggest observing the whole thing for a few hours and if it remains stable, we can assume that the R3 is not faulty. Then you can simply disconnect the Asus and connect the R3 to the modem. Simply use the cable that came with the R3. The important thing here is again modem -> WAN port R3 Leave the settings in the R3 as they are now. Do not change the settings on the PC either! Maybe you can check which MAC address the ASUS has... Maybe reboot both (Modem & R3) after the change…

No Problem 😉 Try the Steps out of my last Answer.

So please don’t USE the 192.168.100.1 for the R3. I told you this before i know that 192.168.100.x is the subnet what your modem use. Simply und the default IP of R3 (192.168.77.1)! One last attempt: Reset the R3 to factory settings while it is connected to the Asus (R3 WAN port to LAN port Asus). Then simply set up the R3. The R3 should automatically recognise that it is receiving Internet via DHCP. Leave the LAN settings of the R3 as they are. Connect the PC to the R3 and set the LAN interface of the PC to DHCP!

OK same Subnet of ASUS and R3 is ok but ONLY for the WAN Port (the R3 gets an WAN IP from the AUS DHCP). BUT the R3 have to be in a different Subnet for LAN/WiFi. The PC have to be in the LAN / WiFi Subnet from the R3 and use the LAN IP from the R3 as Gateway…. Please try this… ARRIS modem (192.168.100.1) > ASUS router (via WAN) (192.168.50.1, DHCP enabled) > R3 router (via ASUS port 1 to R3 WAN) (DHCP on WAN Interface, LAN IP 192.168.77.1) > PC (R3 port 1 to PC ethernet port; IP 192.168.77.10; Gateway/DNS 192.168.77.1). Don’t forget to put the R3 in DMZ of the ASUS Router

But you connected the R3 to the WAN port on the Asus, didn't you? EDIT: All three devices in the same subnet is actually not correct, especially if the R3 is connected to the Asus with its WAN port. Please try to set it up as follows:. ASUS: IP: 192.168.50.1 Subnetmask: 255.255.255.0 DHCP: 192.168.50.100 - 192.168.50.254 NETDUMA: IP: 192.168.100.1 Subnetmask: 255.255.255.0 DHCP: 192.168.100.100 - 192.168.100.254 WAN configuration: DHCP This should give the R3 the 192.168.50.100 on the WAN interface if nothing else is connected to the ASUS. You could now also configure the WAN port as a static IP and enter 192.168.50.10 there, for example. Gateway for the R3 would be the ASUS (192.168.50.1) The devices which connected to the R3 should get an IP out of the 192.168.100.X Subnet (Manually or DHCP). The gateway for this devices is the R3 (192.168.100.1).

What else you could try is the following: connect the Asus router to your modem. Deactivate WiFi and everything that is not necessary. Then connect the R3 to the Asus and put the R3 in the Asus in the DMZ.

Perhaps reset the R3 to the factory settings again and then disconnect it from the power supply for 10 minutes before setting it up again.

Are you able to connect another device to your Modem and check if there are the same Problems?

Have you tried setting the WAN connection from DHCP to static IP and entering a corresponding IP in the settings?

According to your log entries, the WAN interface was briefly offline before it apparently went back online permanently. In any case, no further disconnects are visible in the entries. Wed Feb 21 23:58:37 2024 daemon.notice netifd: Interface 'wan' has link connectivity loss Wed Feb 21 23:59:56 2024 daemon.notice netifd: Interface 'wan' has link connectivity Thu Feb 22 00:00:45 2024 daemon.notice netifd: wan (21369): udhcpc: lease of 24.54.129.14 obtained, lease time 21600 Thu Feb 22 00:00:45 2024 daemon.notice netifd: Interface 'wan' is now up No further disconnects or connectivity loss until you log ends (Thu Feb 22 00:40:33 2024)

Did you perform a factory reset after upgrading the R3 to the .41 firmware? If not, please try this. Currently, it is strongly recommended to perform a factory reset after the upgrade, as otherwise strange problems may occur.

Can you post your WAN settings from the R3?

Have you connected another device to your modem and checked whether it can connect to the Internet? Maybe your modem is faulty or your Internet line itself? Have you contacted your ISP and asked if there are any general problems?

Try to Connect the R3 directly to the ONT… Cascading routers is always a bad idea

So I think the CPU utilisation is perfectly OK when the dashboard is displayed. My R3 doesn't show any other values either. As soon as another menu item is selected beforehand, the CPU is almost between 4-35 with some peaks at 40, even if a massive amount of data is running through the R3... What I have also noticed is that it depends on the device or browser. On some devices, the dashboard continues to run in the background unless you select something else beforehand and on others it does not.

Select another feature like „Device Manager“ before you look on the CPU Usage! The Dashboard needs some CPU Power even it’s only visible in background!