ProjectNero Posted December 23, 2018 Share Posted December 23, 2018 Hey Peeps, My WiFi has dropped out twice (2nd time about half hour ago), like completely dropped out. Devices came up saying internet not available, but is fine on wired connection. I had to change the WiFi channel from 7 to 8 back to 7 again, it was back on. But then I checked the log. A lot of: Sun Dec 23 19:32:45 2018 kern.info dpiclass-daemon: Kill flow due to timeout Sun Dec 23 19:33:18 2018 kern.info kernel: [256715.884000] recv: nf_ct_get failed Sun Dec 23 19:31:34 2018 user.warn com.netdumasoftware.settings: Error opening wireless-mirror with error wireless-mirror: No such file or directory. Sun Dec 23 19:32:02 2018 daemon.notice miniupnpd[1406]: http://192.168.88.1:5000/rootDesc.xml not found, responding ERROR 404 and generally a lot of errors and failed this that and the other. Anything to be worried about? Link to comment Share on other sites More sharing options...
Azlios Posted December 24, 2018 Share Posted December 24, 2018 On 12/23/2018 at 7:40 PM, ProjectNero said: Hey Peeps, My WiFi has dropped out twice (2nd time about half hour ago), like completely dropped out. Devices came up saying internet not available, but is fine on wired connection. I had to change the WiFi channel from 7 to 8 back to 7 again, it was back on. But then I checked the log. A lot of: Sun Dec 23 19:32:45 2018 kern.info dpiclass-daemon: Kill flow due to timeout Sun Dec 23 19:33:18 2018 kern.info kernel: [256715.884000] recv: nf_ct_get failed Sun Dec 23 19:31:34 2018 user.warn com.netdumasoftware.settings: Error opening wireless-mirror with error wireless-mirror: No such file or directory. Sun Dec 23 19:32:02 2018 daemon.notice miniupnpd[1406]: http://192.168.88.1:5000/rootDesc.xml not found, responding ERROR 404 and generally a lot of errors and failed this that and the other. Anything to be worried about? I get this roughly once a week. My log looks exactly the same. I've managed to narrow it down to being something wrong with when the DHCP lease renews. Link to comment Share on other sites More sharing options...
Administrators Netduma Admin Posted December 24, 2018 Administrators Share Posted December 24, 2018 Has this continued for you both? Have you set anything specific for DHCP in your Network Settings? I'm not sure if the cause is there (could just be a random drop out), but would be good to know if you share similar settings. Link to comment Share on other sites More sharing options...
Azlios Posted December 25, 2018 Share Posted December 25, 2018 mine used to drop near enough everyday, got advised to increase my DHCP lease time in the duma so I put it at the max 168 hours, 7 days. Nearly always on that 7th day my wifi drops and I have to do a manual change of the wifi channel to get it back. Link to comment Share on other sites More sharing options...
Administrators Netduma Admin Posted December 25, 2018 Administrators Share Posted December 25, 2018 Ok that is super helpful to know. Thank you. I will pass this onto the developers. Link to comment Share on other sites More sharing options...
ProjectNero Posted December 26, 2018 Author Share Posted December 26, 2018 WiFi connection seems to be touch and go sometimes. It will be fine, then seems to struggle every now and then, and then just return to normal until next time it struggles. No pattern to it, and no trigger. Log is still full of 'failed' and 'timeout' text. Link to comment Share on other sites More sharing options...
Administrators Netduma Admin Posted December 27, 2018 Administrators Share Posted December 27, 2018 I wouldn’t worry about the failed and timeout messages. It’s just for devs and it’s almost always about something completely innocuous that won’t affect your experience. Are you now just seeing slower speeds or are the full dropouts still happening? Link to comment Share on other sites More sharing options...
Azlios Posted December 28, 2018 Share Posted December 28, 2018 On 12/27/2018 at 11:01 AM, Netduma Admin said: I wouldn’t worry about the failed and timeout messages. It’s just for devs and it’s almost always about something completely innocuous that won’t affect your experience. Are you now just seeing slower speeds or are the full dropouts still happening? Had a full drop out today, wired included. I was at work though so couldn't grab the log for when it happened, all the log said when I got home was the good old kill flow to timeout. I think its just my duma is getting old and has taken a couple too many knocks and is beginning to struggle. Link to comment Share on other sites More sharing options...
Administrators Netduma Fraser Posted December 28, 2018 Administrators Share Posted December 28, 2018 I'd set some static IPs for your most important devices and see if they drop as well at the end of the DHCP lease or not Link to comment Share on other sites More sharing options...
Azlios Posted January 3, 2019 Share Posted January 3, 2019 On 12/28/2018 at 2:04 PM, Netduma Fraser said: I'd set some static IPs for your most important devices and see if they drop as well at the end of the DHCP lease or not So WiFi just dropped on the seventh day like usual, even devices with static IPs dropped too. Simple fix like always, a quick change of the wifi channel and all back up running again. I starred out what I'm guessing are mac addresses to some of my devices. Log for when the WiFi dropped - Thu Jan 3 22:48:12 2019 kern.err kernel: [184230.688000] ath: phy0: Failed to stop TX DMA, queues=0x00c! Thu Jan 3 22:48:08 2019 kern.err kernel: [184226.104000] ath: phy0: Failed to stop TX DMA, queues=0x00e! Thu Jan 3 22:48:03 2019 daemon.info hostapd: wlan0: STA **:**:**:**:**:** WPA: group key handshake completed (RSN) Thu Jan 3 22:48:03 2019 daemon.info hostapd: wlan0: STA **:**:**:**:**:** WPA: group key handshake completed (RSN) Thu Jan 3 22:48:01 2019 daemon.info hostapd: wlan0: STA **:**:**:**:**:** WPA: group key handshake completed (RSN) Thu Jan 3 22:48:01 2019 daemon.info hostapd: wlan0: STA **:**:**:**:**:** WPA: group key handshake completed (RSN) Thu Jan 3 22:48:01 2019 daemon.info hostapd: wlan0: STA **:**:**:**:**:** WPA: group key handshake completed (RSN) Thu Jan 3 22:48:01 2019 daemon.info hostapd: wlan0: STA **:**:**:**:**:** WPA: group key handshake completed (RSN) Thu Jan 3 22:48:01 2019 daemon.info hostapd: wlan0: STA **:**:**:**:**:** WPA: group key handshake completed (RSN) Thu Jan 3 22:48:01 2019 daemon.info hostapd: wlan0: STA **:**:**:**:**:** WPA: group key handshake completed (RSN) Thu Jan 3 22:48:01 2019 daemon.info hostapd: wlan0: STA **:**:**:**:**:** WPA: group key handshake completed (RSN) Thu Jan 3 22:47:52 2019 daemon.info hostapd: wlan0: STA **:**:**:**:**:** IEEE 802.11: deauthenticated due to inactivity (timer DEAUTH/REMOVE) Thu Jan 3 22:47:51 2019 daemon.info hostapd: wlan0: STA **:**:**:**:**:** IEEE 802.11: disassociated Thu Jan 3 22:47:40 2019 user.info com.netdumasoftware.neighwatch: DHCP lease change. Thu Jan 3 22:47:40 2019 user.info com.netdumasoftware.neighwatch: DHCP old event. Log just after it came back after channel change - Thu Jan 3 22:58:37 2019 daemon.info dnsmasq-dhcp[19874]: read /etc/ethers - 0 addresses Thu Jan 3 22:58:37 2019 daemon.info dnsmasq[19874]: read /tmp/hosts/dhcp - 0 addresses Thu Jan 3 22:58:37 2019 daemon.info dnsmasq[19874]: read /etc/hosts - 2 addresses Thu Jan 3 22:58:37 2019 daemon.info dnsmasq[19874]: using nameserver 192.168.1.254#53 Thu Jan 3 22:58:37 2019 daemon.info dnsmasq[19874]: using local addresses only for domain lan Thu Jan 3 22:58:37 2019 daemon.info dnsmasq[19874]: reading /tmp/resolv.conf.auto Thu Jan 3 22:58:37 2019 daemon.info dnsmasq[19874]: using local addresses only for domain lan Thu Jan 3 22:58:37 2019 daemon.info dnsmasq-dhcp[19874]: DHCP, IP range 192.168.88.100 -- 192.168.88.249, lease time 7d Thu Jan 3 22:58:37 2019 daemon.info dnsmasq[19874]: compile time options: IPv6 GNU-getopt no-DBus no-i18n no-IDN DHCP no-DHCPv6 no-Lua TFTP conntrack no-ipset no-auth no-DNSSEC Thu Jan 3 22:58:37 2019 daemon.info dnsmasq[19874]: started, version 2.71 cachesize 150 Thu Jan 3 22:58:36 2019 daemon.info dnsmasq[1155]: exiting on receipt of SIGTERM Link to comment Share on other sites More sharing options...
Administrators Netduma Fraser Posted January 3, 2019 Administrators Share Posted January 3, 2019 How many devices do you have? Would it be much more of a hassle to give remaining devices wired & wireless static IPs/reservations and then disable the DHCP server? Link to comment Share on other sites More sharing options...
Azlios Posted January 4, 2019 Share Posted January 4, 2019 19 hours ago, Netduma Fraser said: How many devices do you have? Would it be much more of a hassle to give remaining devices wired & wireless static IPs/reservations and then disable the DHCP server? I have anywhere between 10-20 devices connected at a time, I can try and give them all static IPs and turn off the DHCP server when I get some time. Link to comment Share on other sites More sharing options...
Administrators Netduma Fraser Posted January 4, 2019 Administrators Share Posted January 4, 2019 Okay let us know if that resolves it, if so then looks like DHCP server causes issues even when devices are set to static. Link to comment Share on other sites More sharing options...
Azlios Posted January 5, 2019 Share Posted January 5, 2019 18 hours ago, Netduma Fraser said: Okay let us know if that resolves it, if so then looks like DHCP server causes issues even when devices are set to static. Just out of curiosity would I be able to still use the Duma if I turn off DHCP on the Smart Hub Link to comment Share on other sites More sharing options...
Administrators Netduma Admin Posted January 7, 2019 Administrators Share Posted January 7, 2019 You would - you;ll just need to assign a static WAN IP on the R1 because it won't be assigned an IP address from the Hub anymore Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.