emclean Posted March 4, 2021 Share Posted March 4, 2021 I've got a combo modem/router (wifi) from my ISP and the netduma r2 is connected to that via ethernet. sorry for the double post disconnect happened in between. i'm switching to my other wifi for now Link to comment Share on other sites More sharing options...
emclean Posted March 4, 2021 Share Posted March 4, 2021 19 minutes ago, Netduma Fraser said: Hey, welcome to the forum! Sorry to hear you're having this issue. What is your exact physical setup, i.e. are you using a pure modem (no wifi) or a modem/router (wifi)? I've got a combo cable modem/router (wifi) from my ISP and the netduma r2 is connected to that via ethernet. Link to comment Share on other sites More sharing options...
King Posted March 4, 2021 Share Posted March 4, 2021 Seems like everyone is having the same problem (persistent internet disconnections) what’s the ETA on the firmware fix for this? my brand new netduma also randomly resets/disconnects itself once a day, even tho I’ve set the DHCP to 168. And yes I’m on the latest firmware of course, and done multiple hard resets to no avail. I sure hope this is a main focus for the netduma company because it raises a huge red flag because there is. Product liability to a manufacturer or seller being held liable for placing a new defective product into the hands of a consumer. Link to comment Share on other sites More sharing options...
Administrators Netduma Fraser Posted March 4, 2021 Administrators Share Posted March 4, 2021 1 hour ago, emclean said: I've got a combo cable modem/router (wifi) from my ISP and the netduma r2 is connected to that via ethernet. Is that in router mode or have you put it in modem mode? Regardless of the way you have put it can you try the other method please and see if that works? 33 minutes ago, King said: Seems like everyone is having the same problem (persistent internet disconnections) what’s the ETA on the firmware fix for this? my brand new netduma also randomly resets/disconnects itself once a day, even tho I’ve set the DHCP to 168. And yes I’m on the latest firmware of course, and done multiple hard resets to no avail. I sure hope this is a main focus for the netduma company because it raises a huge red flag because there is. Product liability to a manufacturer or seller being held liable for placing a new defective product into the hands of a consumer. It is a support forum so you will mainly see people with issues here, it does not represent the entirety of our customer base and is within normal levels for a consumer based product. We are working on it, it's a tough issue to pin down but it's a high focus for us. Is that all devices or wired/wireless specifically? Link to comment Share on other sites More sharing options...
emclean Posted March 4, 2021 Share Posted March 4, 2021 42 minutes ago, Netduma Fraser said: Is that in router mode or have you put it in modem mode? Regardless of the way you have put it can you try the other method please and see if that works? Its a verizon fios router, it doesn't really operate as a modem but it interfaces with the optical network terminal in a separate room (that does act like a modem) via coax. So its essentially just acting as a router, I don't think I can put it in modem mode, if it helps its an actiontec MI424WR-GEN3I With my linksys router I just connected it to the fios router and had a double nat and connected all my devices to the linksys. I had hoped the netduma could just be a drop in replacement for the linksys router. Seems to work for a bit but then loses connectivity. Link to comment Share on other sites More sharing options...
Administrators Netduma Fraser Posted March 4, 2021 Administrators Share Posted March 4, 2021 Thanks for the information, on the actiontec would you be able to set a static IP for the R2 to see if it can sustain a connection? Might be to do with the actiontec DHCP release renewing. Link to comment Share on other sites More sharing options...
emclean Posted March 4, 2021 Share Posted March 4, 2021 5 minutes ago, Netduma Fraser said: Thanks for the information, on the actiontec would you be able to set a static IP for the R2 to see if it can sustain a connection? Might be to do with the actiontec DHCP release renewing. Done. Will let you know how it goes. Link to comment Share on other sites More sharing options...
emclean Posted March 4, 2021 Share Posted March 4, 2021 Just now, emclean said: Done. Will let you know how it goes. The R2 almost immediately lost its connection after that. Rebooting it now to see if it can keep its connection for longer. Link to comment Share on other sites More sharing options...
emclean Posted March 4, 2021 Share Posted March 4, 2021 31 minutes ago, Netduma Fraser said: Thanks for the information, on the actiontec would you be able to set a static IP for the R2 to see if it can sustain a connection? Might be to do with the actiontec DHCP release renewing. After the reboot it lost its connection after about 15 minutes. Below is some of what was in the system information logs Thu Mar 4 16:31:17 2021 daemon.err cli.lua[2877]: uci: Entry not found Thu Mar 4 16:31:17 2021 daemon.err cli.lua[2877]: uci: Entry not found Thu Mar 4 16:31:15 2021 kern.info kernel: [ 1031.312384] mtk_soc_eth 1e100000.ethernet eth0: rx_ring=0, base=07340000, max=0, calc=1864, drx=1865 Thu Mar 4 16:31:15 2021 kern.info kernel: [ 1031.290727] mtk_soc_eth 1e100000.ethernet eth0: tx_ring=0, base=07fb0000, max=0, ctx=2751, dtx=2225, fdx=2225, next=2751 Thu Mar 4 16:31:15 2021 kern.info kernel: [ 1031.278742] mtk_soc_eth 1e100000.ethernet eth0: dma_cfg:80000067 Thu Mar 4 16:31:15 2021 kern.err kernel: [ 1031.266407] mtk_soc_eth 1e100000.ethernet eth0: transmit timed out Thu Mar 4 16:31:11 2021 user.info com.netdumasoftware.qos: taking down IFB Thu Mar 4 16:31:11 2021 daemon.err cli.lua[2877]: RTNETLINK answers: No such file or directory Thu Mar 4 16:31:11 2021 user.info com.netdumasoftware.qos: applying qos for zone lan Thu Mar 4 16:31:11 2021 user.info com.netdumasoftware.qos: applying qos for zone wan Thu Mar 4 16:31:11 2021 daemon.err cli.lua[2877]: Connect error: Operation timed out Thu Mar 4 16:31:11 2021 daemon.err cli.lua[2877]: Connect error: Operation timed out Thu Mar 4 16:31:11 2021 daemon.err cli.lua[2877]: Connect error: Operation timed out Thu Mar 4 16:31:11 2021 daemon.err cli.lua[2877]: Connect error: Operation timed out Thu Mar 4 16:31:10 2021 kern.info kernel: [ 1026.272436] mtk_soc_eth 1e100000.ethernet eth0: rx_ring=0, base=07340000, max=0, calc=1824, drx=1825 Thu Mar 4 16:31:10 2021 kern.info kernel: [ 1026.250773] mtk_soc_eth 1e100000.ethernet eth0: tx_ring=0, base=07fb0000, max=0, ctx=2751, dtx=2225, fdx=2225, next=2751 Thu Mar 4 16:31:10 2021 kern.info kernel: [ 1026.238797] mtk_soc_eth 1e100000.ethernet eth0: dma_cfg:80000067 Thu Mar 4 16:31:10 2021 kern.err kernel: [ 1026.226461] mtk_soc_eth 1e100000.ethernet eth0: transmit timed out Thu Mar 4 16:31:05 2021 kern.info kernel: [ 1021.312470] mtk_soc_eth 1e100000.ethernet eth0: rx_ring=0, base=07340000, max=0, calc=1793, drx=1794 Thu Mar 4 16:31:05 2021 kern.info kernel: [ 1021.290825] mtk_soc_eth 1e100000.ethernet eth0: tx_ring=0, base=07fb0000, max=0, ctx=2751, dtx=2225, fdx=2225, next=2751 Thu Mar 4 16:31:05 2021 kern.info kernel: [ 1021.278849] mtk_soc_eth 1e100000.ethernet eth0: dma_cfg:80000067 Thu Mar 4 16:31:05 2021 kern.err kernel: [ 1021.266518] mtk_soc_eth 1e100000.ethernet eth0: transmit timed out Thu Mar 4 16:31:00 2021 kern.info kernel: [ 1016.272777] mtk_soc_eth 1e100000.ethernet eth0: rx_ring=0, base=07340000, max=0, calc=1728, drx=1729 Thu Mar 4 16:31:00 2021 kern.info kernel: [ 1016.251090] mtk_soc_eth 1e100000.ethernet eth0: tx_ring=0, base=07fb0000, max=0, ctx=2751, dtx=2225, fdx=2225, next=2751 Thu Mar 4 16:31:00 2021 kern.info kernel: [ 1016.239058] mtk_soc_eth 1e100000.ethernet eth0: dma_cfg:80000067 Thu Mar 4 16:31:00 2021 kern.err kernel: [ 1016.226647] mtk_soc_eth 1e100000.ethernet eth0: transmit timed out Thu Mar 4 16:30:55 2021 kern.info kernel: [ 1011.312716] mtk_soc_eth 1e100000.ethernet eth0: rx_ring=0, base=07340000, max=0, calc=1641, drx=1642 Thu Mar 4 16:30:55 2021 kern.info kernel: [ 1011.290943] mtk_soc_eth 1e100000.ethernet eth0: tx_ring=0, base=07fb0000, max=0, ctx=2751, dtx=2225, fdx=2225, next=2751 Thu Mar 4 16:30:55 2021 kern.info kernel: [ 1011.278961] mtk_soc_eth 1e100000.ethernet eth0: dma_cfg:80000067 Thu Mar 4 16:30:55 2021 kern.err kernel: [ 1011.266624] mtk_soc_eth 1e100000.ethernet eth0: transmit timed out Thu Mar 4 16:30:50 2021 kern.info kernel: [ 1006.272615] mtk_soc_eth 1e100000.ethernet eth0: rx_ring=0, base=07340000, max=0, calc=1595, drx=1596 Thu Mar 4 16:30:50 2021 kern.info kernel: [ 1006.250968] mtk_soc_eth 1e100000.ethernet eth0: tx_ring=0, base=07fb0000, max=0, ctx=2751, dtx=2225, fdx=2225, next=2751 Thu Mar 4 16:30:50 2021 kern.info kernel: [ 1006.238990] mtk_soc_eth 1e100000.ethernet eth0: dma_cfg:80000067 Thu Mar 4 16:30:50 2021 kern.err kernel: [ 1006.226661] mtk_soc_eth 1e100000.ethernet eth0: transmit timed out Thu Mar 4 16:30:45 2021 kern.info kernel: [ 1001.312798] mtk_soc_eth 1e100000.ethernet eth0: rx_ring=0, base=07340000, max=0, calc=1545, drx=1546 Thu Mar 4 16:30:45 2021 kern.info kernel: [ 1001.291116] mtk_soc_eth 1e100000.ethernet eth0: tx_ring=0, base=07fb0000, max=0, ctx=2751, dtx=2225, fdx=2225, next=2751 Thu Mar 4 16:30:45 2021 kern.info kernel: [ 1001.279083] mtk_soc_eth 1e100000.ethernet eth0: dma_cfg:80000067 Thu Mar 4 16:30:45 2021 kern.err kernel: [ 1001.266743] mtk_soc_eth 1e100000.ethernet eth0: transmit timed out Thu Mar 4 16:30:40 2021 kern.info kernel: [ 996.273008] mtk_soc_eth 1e100000.ethernet eth0: rx_ring=0, base=07340000, max=0, calc=1479, drx=1480 Thu Mar 4 16:30:40 2021 kern.info kernel: [ 996.251269] mtk_soc_eth 1e100000.ethernet eth0: tx_ring=0, base=07fb0000, max=0, ctx=2751, dtx=2225, fdx=2225, next=2751 Thu Mar 4 16:30:40 2021 kern.info kernel: [ 996.239206] mtk_soc_eth 1e100000.ethernet eth0: dma_cfg:80000067 Thu Mar 4 16:30:40 2021 kern.err kernel: [ 996.226827] mtk_soc_eth 1e100000.ethernet eth0: transmit timed out Thu Mar 4 16:30:35 2021 kern.info kernel: [ 991.312865] mtk_soc_eth 1e100000.ethernet eth0: rx_ring=0, base=07340000, max=0, calc=1397, drx=1398 Thu Mar 4 16:30:35 2021 kern.info kernel: [ 991.291193] mtk_soc_eth 1e100000.ethernet eth0: tx_ring=0, base=07fb0000, max=0, ctx=2751, dtx=2225, fdx=2225, next=2751 Thu Mar 4 16:30:35 2021 kern.info kernel: [ 991.279193] mtk_soc_eth 1e100000.ethernet eth0: dma_cfg:80000067 Thu Mar 4 16:30:35 2021 kern.err kernel: [ 991.266858] mtk_soc_eth 1e100000.ethernet eth0: transmit timed out Thu Mar 4 16:30:30 2021 kern.info kernel: [ 986.272899] mtk_soc_eth 1e100000.ethernet eth0: rx_ring=0, base=07340000, max=0, calc=1321, drx=1322 Thu Mar 4 16:30:30 2021 kern.info kernel: [ 986.251239] mtk_soc_eth 1e100000.ethernet eth0: tx_ring=0, base=07fb0000, max=0, ctx=2751, dtx=2225, fdx=2225, next=2751 Thu Mar 4 16:30:30 2021 kern.info kernel: [ 986.239248] mtk_soc_eth 1e100000.ethernet eth0: dma_cfg:80000067 Thu Mar 4 16:30:30 2021 kern.err kernel: [ 986.226907] mtk_soc_eth 1e100000.ethernet eth0: transmit timed out Thu Mar 4 16:30:25 2021 kern.info kernel: [ 981.313091] mtk_soc_eth 1e100000.ethernet eth0: rx_ring=0, base=07340000, max=0, calc=1232, drx=1233 Thu Mar 4 16:30:25 2021 kern.info kernel: [ 981.291399] mtk_soc_eth 1e100000.ethernet eth0: tx_ring=0, base=07fb0000, max=0, ctx=2751, dtx=2225, fdx=2225, next=2751 Thu Mar 4 16:30:25 2021 kern.info kernel: [ 981.279396] mtk_soc_eth 1e100000.ethernet eth0: dma_cfg:80000067 Thu Mar 4 16:30:25 2021 kern.err kernel: [ 981.267051] mtk_soc_eth 1e100000.ethernet eth0: transmit timed out Thu Mar 4 16:30:20 2021 kern.info kernel: [ 976.273289] mtk_soc_eth 1e100000.ethernet eth0: rx_ring=0, base=07340000, max=0, calc=1116, drx=1117 Thu Mar 4 16:30:20 2021 kern.info kernel: [ 976.251566] mtk_soc_eth 1e100000.ethernet eth0: tx_ring=0, base=07fb0000, max=0, ctx=2751, dtx=2225, fdx=2225, next=2751 Thu Mar 4 16:30:20 2021 kern.info kernel: [ 976.239498] mtk_soc_eth 1e100000.ethernet eth0: dma_cfg:80000067 Thu Mar 4 16:30:20 2021 kern.err kernel: [ 976.227146] mtk_soc_eth 1e100000.ethernet eth0: transmit timed out Thu Mar 4 16:30:15 2021 kern.info kernel: [ 971.313115] mtk_soc_eth 1e100000.ethernet eth0: rx_ring=0, base=07340000, max=0, calc=1027, drx=1028 Thu Mar 4 16:30:15 2021 kern.info kernel: [ 971.291444] mtk_soc_eth 1e100000.ethernet eth0: tx_ring=0, base=07fb0000, max=0, ctx=2751, dtx=2225, fdx=2225, next=2751 Thu Mar 4 16:30:15 2021 kern.info kernel: [ 971.279443] mtk_soc_eth 1e100000.ethernet eth0: dma_cfg:80000067 Thu Mar 4 16:30:15 2021 kern.err kernel: [ 971.267101] mtk_soc_eth 1e100000.ethernet eth0: transmit timed out Thu Mar 4 16:30:10 2021 kern.info kernel: [ 966.273213] mtk_soc_eth 1e100000.ethernet eth0: rx_ring=0, base=07340000, max=0, calc=913, drx=914 Thu Mar 4 16:30:10 2021 kern.info kernel: [ 966.251538] mtk_soc_eth 1e100000.ethernet eth0: tx_ring=0, base=07fb0000, max=0, ctx=2751, dtx=2225, fdx=2225, next=2751 Thu Mar 4 16:30:10 2021 kern.info kernel: [ 966.239543] mtk_soc_eth 1e100000.ethernet eth0: dma_cfg:80000067 Thu Mar 4 16:30:10 2021 kern.err kernel: [ 966.227208] mtk_soc_eth 1e100000.ethernet eth0: transmit timed out Thu Mar 4 16:30:05 2021 kern.info kernel: [ 961.313507] mtk_soc_eth 1e100000.ethernet eth0: rx_ring=0, base=07340000, max=0, calc=832, drx=833 Thu Mar 4 16:30:05 2021 kern.info kernel: [ 961.291737] mtk_soc_eth 1e100000.ethernet eth0: tx_ring=0, base=07fb0000, max=0, ctx=2751, dtx=2225, fdx=2225, next=2751 Thu Mar 4 16:30:05 2021 kern.info kernel: [ 961.279663] mtk_soc_eth 1e100000.ethernet eth0: dma_cfg:80000067 Thu Mar 4 16:30:05 2021 kern.err kernel: [ 961.267287] mtk_soc_eth 1e100000.ethernet eth0: transmit timed out Thu Mar 4 16:30:00 2021 kern.info kernel: [ 956.273314] mtk_soc_eth 1e100000.ethernet eth0: rx_ring=0, base=07340000, max=0, calc=731, drx=732 Thu Mar 4 16:30:00 2021 kern.info kernel: [ 956.251646] mtk_soc_eth 1e100000.ethernet eth0: tx_ring=0, base=07fb0000, max=0, ctx=2751, dtx=2225, fdx=2225, next=2751 Thu Mar 4 16:30:00 2021 kern.info kernel: [ 956.239655] mtk_soc_eth 1e100000.ethernet eth0: dma_cfg:80000067 Thu Mar 4 16:30:00 2021 kern.err kernel: [ 956.227311] mtk_soc_eth 1e100000.ethernet eth0: transmit timed out Thu Mar 4 16:30:00 2021 kern.info kernel: [ 956.143471] ash (28410): drop_caches: 3 Thu Mar 4 16:30:00 2021 cron.err crond[1404]: USER root pid 28410 cmd echo 3 > /proc/sys/vm/drop_caches Thu Mar 4 16:29:55 2021 kern.info kernel: [ 951.313435] mtk_soc_eth 1e100000.ethernet eth0: rx_ring=0, base=07340000, max=0, calc=638, drx=639 Thu Mar 4 16:29:55 2021 kern.info kernel: [ 951.291741] mtk_soc_eth 1e100000.ethernet eth0: tx_ring=0, base=07fb0000, max=0, ctx=2751, dtx=2225, fdx=2225, next=2751 Thu Mar 4 16:29:55 2021 kern.info kernel: [ 951.279740] mtk_soc_eth 1e100000.ethernet eth0: dma_cfg:80000067 Thu Mar 4 16:29:55 2021 kern.err kernel: [ 951.267407] mtk_soc_eth 1e100000.ethernet eth0: transmit timed out Thu Mar 4 16:29:50 2021 daemon.info hostapd: wlan1: STA dc:8b:28:39:a5:cb IEEE 802.11: deauthenticated due to inactivity (timer DEAUTH/REMOVE) Thu Mar 4 16:29:50 2021 kern.info kernel: [ 946.273446] mtk_soc_eth 1e100000.ethernet eth0: rx_ring=0, base=07340000, max=0, calc=534, drx=535 Thu Mar 4 16:29:50 2021 kern.info kernel: [ 946.251792] mtk_soc_eth 1e100000.ethernet eth0: tx_ring=0, base=07fb0000, max=0, ctx=2751, dtx=2225, fdx=2225, next=2751 Thu Mar 4 16:29:50 2021 kern.info kernel: [ 946.239812] mtk_soc_eth 1e100000.ethernet eth0: dma_cfg:80000067 Thu Mar 4 16:29:50 2021 kern.err kernel: [ 946.227476] mtk_soc_eth 1e100000.ethernet eth0: transmit timed out Thu Mar 4 16:29:45 2021 kern.info kernel: [ 941.313872] mtk_soc_eth 1e100000.ethernet eth0: rx_ring=0, base=07340000, max=0, calc=462, drx=463 Thu Mar 4 16:29:45 2021 kern.info kernel: [ 941.292129] mtk_soc_eth 1e100000.ethernet eth0: tx_ring=0, base=07fb0000, max=0, ctx=2751, dtx=2225, fdx=2225, next=2751 Thu Mar 4 16:29:45 2021 kern.info kernel: [ 941.280059] mtk_soc_eth 1e100000.ethernet eth0: dma_cfg:80000067 Thu Mar 4 16:29:45 2021 kern.err kernel: [ 941.267634] mtk_soc_eth 1e100000.ethernet eth0: transmit timed out Thu Mar 4 16:29:40 2021 kern.info kernel: [ 936.274001] mtk_soc_eth 1e100000.ethernet eth0: rx_ring=0, base=07340000, max=0, calc=335, drx=336 Thu Mar 4 16:29:40 2021 kern.info kernel: [ 936.252210] mtk_soc_eth 1e100000.ethernet eth0: tx_ring=0, base=07fb0000, max=0, ctx=2751, dtx=2225, fdx=2225, next=2751 Thu Mar 4 16:29:40 2021 kern.info kernel: [ 936.240121] mtk_soc_eth 1e100000.ethernet eth0: dma_cfg:80000067 Thu Mar 4 16:29:40 2021 kern.err kernel: [ 936.227695] mtk_soc_eth 1e100000.ethernet eth0: transmit timed out Thu Mar 4 16:29:35 2021 kern.info kernel: [ 931.313867] mtk_soc_eth 1e100000.ethernet eth0: rx_ring=0, base=07340000, max=0, calc=220, drx=221 Thu Mar 4 16:29:35 2021 kern.info kernel: [ 931.292136] mtk_soc_eth 1e100000.ethernet eth0: tx_ring=0, base=07fb0000, max=0, ctx=2751, dtx=2225, fdx=2225, next=2751 Thu Mar 4 16:29:35 2021 kern.info kernel: [ 931.280119] mtk_soc_eth 1e100000.ethernet eth0: dma_cfg:80000067 Thu Mar 4 16:29:35 2021 kern.err kernel: [ 931.267760] mtk_soc_eth 1e100000.ethernet eth0: transmit timed out Thu Mar 4 16:29:30 2021 kern.info kernel: [ 926.273786] mtk_soc_eth 1e100000.ethernet eth0: rx_ring=0, base=07340000, max=0, calc=118, drx=119 Thu Mar 4 16:29:30 2021 kern.info kernel: [ 926.252109] mtk_soc_eth 1e100000.ethernet eth0: tx_ring=0, base=07fb0000, max=0, ctx=2751, dtx=2225, fdx=2225, next=2751 Thu Mar 4 16:29:30 2021 kern.info kernel: [ 926.240126] mtk_soc_eth 1e100000.ethernet eth0: dma_cfg:80000067 Thu Mar 4 16:29:30 2021 kern.err kernel: [ 926.227768] mtk_soc_eth 1e100000.ethernet eth0: transmit timed out Thu Mar 4 16:29:25 2021 kern.info kernel: [ 921.313931] mtk_soc_eth 1e100000.ethernet eth0: rx_ring=0, base=07340000, max=0, calc=4049, drx=4050 Thu Mar 4 16:29:25 2021 kern.info kernel: [ 921.292205] mtk_soc_eth 1e100000.ethernet eth0: tx_ring=0, base=07fb0000, max=0, ctx=2751, dtx=2225, fdx=2225, next=2751 Thu Mar 4 16:29:25 2021 kern.info kernel: [ 921.280207] mtk_soc_eth 1e100000.ethernet eth0: dma_cfg:80000067 Thu Mar 4 16:29:25 2021 kern.err kernel: [ 921.267876] mtk_soc_eth 1e100000.ethernet eth0: transmit timed out Thu Mar 4 16:29:22 2021 user.info com.netdumasoftware.neighwatch: DHCP lease change. Thu Mar 4 16:29:22 2021 user.info com.netdumasoftware.neighwatch: DHCP old event. Thu Mar 4 16:29:22 2021 user.info com.netdumasoftware.neighwatch: DHCP lease change. Thu Mar 4 16:29:22 2021 user.info com.netdumasoftware.neighwatch: DHCP old event. Thu Mar 4 16:29:22 2021 daemon.info dnsmasq-dhcp[2840]: read /etc/ethers - 0 addresses Thu Mar 4 16:29:21 2021 daemon.info dnsmasq[2840]: read /tmp/hosts/dhcp.cfg01411c - 2 addresses Thu Mar 4 16:29:21 2021 daemon.info dnsmasq[2840]: read /tmp/hosts/odhcpd - 2 addresses Thu Mar 4 16:29:21 2021 daemon.info dnsmasq[2840]: read /etc/hosts - 4 addresses Thu Mar 4 16:29:21 2021 user.info com.netdumasoftware.neighwatch: DHCP lease change. Thu Mar 4 16:29:21 2021 user.info com.netdumasoftware.neighwatch: DHCP old event. Thu Mar 4 16:29:20 2021 daemon.info dnsmasq-dhcp[2840]: DHCPACK(br-lan) 192.168.77.226 dc:8b:28:39:a5:cb DESKTOP-OC0N1UT Thu Mar 4 16:29:20 2021 daemon.info dnsmasq-dhcp[2840]: DHCPREQUEST(br-lan) 192.168.77.226 dc:8b:28:39:a5:cb Thu Mar 4 16:29:20 2021 daemon.info hostapd: wlan0: STA dc:8b:28:39:a5:cb WPA: pairwise key handshake completed (RSN) Thu Mar 4 16:29:20 2021 daemon.info hostapd: wlan0: STA dc:8b:28:39:a5:cb RADIUS: starting accounting session 72BB47AF2B6C8298 Thu Mar 4 16:29:20 2021 daemon.notice hostapd: wlan0: AP-STA-CONNECTED dc:8b:28:39:a5:cb Thu Mar 4 16:29:20 2021 daemon.notice hostapd: wlan1: AP-STA-DISCONNECTED dc:8b:28:39:a5:cb Thu Mar 4 16:29:20 2021 daemon.notice hostapd: wlan1: Prune association for dc:8b:28:39:a5:cb Thu Mar 4 16:29:20 2021 daemon.info hostapd: wlan0: STA dc:8b:28:39:a5:cb IEEE 802.11: associated (aid 1) Thu Mar 4 16:29:20 2021 daemon.info hostapd: wlan0: STA dc:8b:28:39:a5:cb IEEE 802.11: authenticated Thu Mar 4 16:29:20 2021 kern.info kernel: [ 916.273931] mtk_soc_eth 1e100000.ethernet eth0: rx_ring=0, base=07340000, max=0, calc=3657, drx=3658 Thu Mar 4 16:29:20 2021 kern.info kernel: [ 916.252268] mtk_soc_eth 1e100000.ethernet eth0: tx_ring=0, base=07fb0000, max=0, ctx=2751, dtx=2225, fdx=2225, next=2751 Thu Mar 4 16:29:20 2021 kern.info kernel: [ 916.240290] mtk_soc_eth 1e100000.ethernet eth0: dma_cfg:80000067 Thu Mar 4 16:29:20 2021 kern.err kernel: [ 916.227956] mtk_soc_eth 1e100000.ethernet eth0: transmit timed out Thu Mar 4 16:29:15 2021 kern.info kernel: [ 911.314405] mtk_soc_eth 1e100000.ethernet eth0: rx_ring=0, base=07340000, max=0, calc=3500, drx=3501 Thu Mar 4 16:29:15 2021 kern.info kernel: [ 911.292514] mtk_soc_eth 1e100000.ethernet eth0: tx_ring=0, base=07fb0000, max=0, ctx=2751, dtx=2225, fdx=2225, next=2751 Thu Mar 4 16:29:15 2021 kern.info kernel: [ 911.280393] mtk_soc_eth 1e100000.ethernet eth0: dma_cfg:80000067 Thu Mar 4 16:29:15 2021 kern.err kernel: [ 911.268023] mtk_soc_eth 1e100000.ethernet eth0: transmit timed out Thu Mar 4 16:29:14 2021 kern.warn dpiclass-daemon: NFQUEUE unable to handle packet -1 Thu Mar 4 16:29:14 2021 kern.warn dpiclass-daemon: NFQUEUE unable to handle packet -1 Thu Mar 4 16:29:14 2021 kern.warn dpiclass-daemon: NFQUEUE unable to handle packet -1 Thu Mar 4 16:29:14 2021 kern.warn dpiclass-daemon: NFQUEUE unable to handle packet -1 Thu Mar 4 16:29:14 2021 kern.warn dpiclass-daemon: NFQUEUE unable to handle packet -1 Thu Mar 4 16:29:14 2021 kern.info kernel: [ 910.258230] ieee80211 phy1: Hardware restart was requested Thu Mar 4 16:29:14 2021 kern.info kernel: [ 910.238075] mt76x2e 0000:01:00.0: Firmware running! Thu Mar 4 16:29:14 2021 kern.info kernel: [ 910.210044] mt76x2e 0000:01:00.0: Build Time: 201507311614____ Thu Mar 4 16:29:14 2021 kern.info kernel: [ 910.201673] mt76x2e 0000:01:00.0: Build: 1 Thu Mar 4 16:29:14 2021 kern.info kernel: [ 910.190643] mt76x2e 0000:01:00.0: Firmware Version: 0.0.00 Thu Mar 4 16:29:13 2021 daemon.err cli.lua[2877]: RTNETLINK answers: No such file or directory Thu Mar 4 16:29:13 2021 user.info com.netdumasoftware.qos: applying qos for zone wan-ingress Thu Mar 4 16:29:13 2021 daemon.err cli.lua[2877]: RTNETLINK answers: No such file or directory Thu Mar 4 16:29:13 2021 user.info com.netdumasoftware.qos: applying qos for zone lan Thu Mar 4 16:29:12 2021 user.info com.netdumasoftware.qos: applying qos for zone wan Thu Mar 4 16:29:11 2021 user.info com.netdumasoftware.neighwatch: DHCP new lease allocated. Thu Mar 4 16:29:11 2021 user.info com.netdumasoftware.neighwatch: DHCP new event. Link to comment Share on other sites More sharing options...
emclean Posted March 4, 2021 Share Posted March 4, 2021 Didn't realize we could save the whole log file. Attaching it here in case it helps. log-1614890566864.txt Link to comment Share on other sites More sharing options...
Administrators Netduma Fraser Posted March 4, 2021 Administrators Share Posted March 4, 2021 Thanks for that, what was the IP you gave the R2? On the System Information page does it show the same IP that you set? Link to comment Share on other sites More sharing options...
emclean Posted March 4, 2021 Share Posted March 4, 2021 6 minutes ago, Netduma Fraser said: Thanks for that, what was the IP you gave the R2? On the System Information page does it show the same IP that you set? 192.168.1.14 and I believe that's what I saw in dumaos but I switched back to my old router for now. I'll check later and add an update if it was not the same. Netduma Fraser 1 Link to comment Share on other sites More sharing options...
emclean Posted March 5, 2021 Share Posted March 5, 2021 18 hours ago, Netduma Fraser said: Thanks for that, what was the IP you gave the R2? On the System Information page does it show the same IP that you set? Confirming the netduma was/is showing the same ip Link to comment Share on other sites More sharing options...
emclean Posted March 5, 2021 Share Posted March 5, 2021 Here's a log from today. Didn't stay connected for very long after the reboot. I like the software but the router is not usable for me like this. If anything else comes to mind let me know otherwise I'll be trying to send this back. Thank you for your help log-1614962238038.txt Link to comment Share on other sites More sharing options...
Administrators Netduma Fraser Posted March 5, 2021 Administrators Share Posted March 5, 2021 Thanks for that, can you go ahead and re-upgrade to the same firmware please and then factory reset for a fresh install and see if it still happens after that? It may not have flashed correctly prior to shipping. https://forum.netduma.com/topic/34950-new-r2-firmware-30205/ Link to comment Share on other sites More sharing options...
emclean Posted March 5, 2021 Share Posted March 5, 2021 5 hours ago, Netduma Fraser said: Thanks for that, can you go ahead and re-upgrade to the same firmware please and then factory reset for a fresh install and see if it still happens after that? It may not have flashed correctly prior to shipping. https://forum.netduma.com/topic/34950-new-r2-firmware-30205/ Did this all from my Mac and the R2 kept dropping its internet connection after the factory reset. I'm going to try again from a browser on my Windows PC to see if it makes a difference. Link to comment Share on other sites More sharing options...
emclean Posted March 5, 2021 Share Posted March 5, 2021 20 minutes ago, emclean said: Did this all from my Mac and the R2 kept dropping its internet connection after the factory reset. I'm going to try again from a browser on my Windows PC to see if it makes a difference. Fraser, No luck. Re upgraded to 30205, performed a factory reset, put all my settings in and it lost its connection maybe 10 minutes later. I then tried again from my pc with the static ip set as the dmz host on my verizon router and it died again shortly after the factory reset. Thank you for your all your help but looks like its just not going to work out. Could you let me know how I can go about returning it for a refund? Link to comment Share on other sites More sharing options...
Administrators Netduma Fraser Posted March 6, 2021 Administrators Share Posted March 6, 2021 36 minutes ago, emclean said: Fraser, No luck. Re upgraded to 30205, performed a factory reset, put all my settings in and it lost its connection maybe 10 minutes later. I then tried again from my pc with the static ip set as the dmz host on my verizon router and it died again shortly after the factory reset. Thank you for your all your help but looks like its just not going to work out. Could you let me know how I can go about returning it for a refund? I think we've gone through everything unfortunately yeah. We can do a replacement though and then that should work if you'd like to try that. Either way you'll need to email [email protected] with your order number, if you want the replacement then link this topic and they'll sort that out for you. Link to comment Share on other sites More sharing options...
emclean Posted March 7, 2021 Share Posted March 7, 2021 On 3/5/2021 at 7:11 PM, Netduma Fraser said: I think we've gone through everything unfortunately yeah. We can do a replacement though and then that should work if you'd like to try that. Either way you'll need to email [email protected] with your order number, if you want the replacement then link this topic and they'll sort that out for you. A buddy of mine who owns a netduma router suggested I downgrade to 3.0.179 before sending it back. I did it, same approach updated to that firmware version then performed a factory reset and the R2's internet connection has been stable since. I'll keep an eye on it but that seems to have done the trick for me. I grabbed the R2 3.0.179 firmware from the link below http://support.netduma.com/support/solutions/articles/16000091217-latest-firmwares Link to comment Share on other sites More sharing options...
Administrators Netduma Fraser Posted March 7, 2021 Administrators Share Posted March 7, 2021 10 hours ago, emclean said: A buddy of mine who owns a netduma router suggested I downgrade to 3.0.179 before sending it back. I did it, same approach updated to that firmware version then performed a factory reset and the R2's internet connection has been stable since. I'll keep an eye on it but that seems to have done the trick for me. I grabbed the R2 3.0.179 firmware from the link below http://support.netduma.com/support/solutions/articles/16000091217-latest-firmwares That's great to hear, thanks for sharing the solution for you. We're investigating the issue at hand so I'm confident we'll get it resolved. emclean 1 Link to comment Share on other sites More sharing options...
emclean Posted March 7, 2021 Share Posted March 7, 2021 2 hours ago, Netduma Fraser said: That's great to hear, thanks for sharing the solution for you. We're investigating the issue at hand so I'm confident we'll get it resolved. sounds good, if you'd like any more logs from my end just let me know. Netduma Fraser 1 Link to comment Share on other sites More sharing options...
syrupD Posted April 11, 2021 Share Posted April 11, 2021 I got my r2 a few weeks ago and just a few days ago this issue started happening. The r2 is plugged in all lights flashing but nothing can connect to the Internet for both wired and wifi devices. The only fix is to get it working is to power cycle it. I just now factory reset it hoping it will fix it but if not would you recommend updating to an older version of the firmware like emclean did? Link to comment Share on other sites More sharing options...
Administrators Netduma Fraser Posted April 11, 2021 Administrators Share Posted April 11, 2021 8 hours ago, syrupD said: I got my r2 a few weeks ago and just a few days ago this issue started happening. The r2 is plugged in all lights flashing but nothing can connect to the Internet for both wired and wifi devices. The only fix is to get it working is to power cycle it. I just now factory reset it hoping it will fix it but if not would you recommend updating to an older version of the firmware like emclean did? That's certainly an option but you could have the same issue on a previous version. What is the model of the modem/router the R2 is connected to? Are you able to set a static/reserved address for the R2 on the modem? In theory this should help to resolve the issue. Link to comment Share on other sites More sharing options...
syrupD Posted April 11, 2021 Share Posted April 11, 2021 7 hours ago, Netduma Fraser said: That's certainly an option but you could have the same issue on a previous version. What is the model of the modem/router the R2 is connected to? Are you able to set a static/reserved address for the R2 on the modem? In theory this should help to resolve the issue. I have Xfinity and the model is a xb7 ARRIS TG4482A. I set up a static address when I got the R2 but this issue recently started occurring. Link to comment Share on other sites More sharing options...
Administrators Netduma Fraser Posted April 11, 2021 Administrators Share Posted April 11, 2021 1 hour ago, syrupD said: I have Xfinity and the model is a xb7 ARRIS TG4482A. I set up a static address when I got the R2 but this issue recently started occurring. I can see you're using IPv6 now, if you disable this do you see the same issue? Link to comment Share on other sites More sharing options...
Recommended Posts