doddsbrah Posted May 27 Share Posted May 27 Hi, I recently upgraded the firmware which I was hoping would help my poor wifi signal, which in the most part it has. however, most of the times when I fire up my pc which is connected via Ethernet in the R3 it boots all of the offer devices off of the wifi which is very frustrating especially when trying to work on other devices. Please let me know a fix for this? At the moment I am having to re start the router every time. thanks Link to comment Share on other sites More sharing options...
Administrators Netduma Fraser Posted May 27 Administrators Share Posted May 27 That makes no sense at all, please grab the logs from the router when it happens and we can take a look Link to comment Share on other sites More sharing options...
doddsbrah Posted May 27 Author Share Posted May 27 @Netduma Fraser yeah it’s odd it’s almost like it prioritises the PC too much which cuts off other devices but does it a lot. Sorry, how do I get the logs? Link to comment Share on other sites More sharing options...
Administrators Netduma Fraser Posted May 27 Administrators Share Posted May 27 You can find them in Settings > Troubleshooting > Advanced Link to comment Share on other sites More sharing options...
doddsbrah Posted May 28 Author Share Posted May 28 @Netduma Fraser it has kicked the wifi off again when I turned on my PC, see attached log and also a copy and paste of around the time it did it below - when I re start the router and get it all working again, all of my other devices connected to the wifi (even when placed right next to the router) are VERY slow.... when I pay £200 for a router I'd expect better performance than this, please advise Wed May 28 13:11:00 2025 daemon.notice hostapd: wl0: AP-STA-POSSIBLE-PSK-MISMATCH dc:97:ba:1c:15:dd Wed May 28 13:11:01 2025 daemon.notice hostapd: wl0: AP-STA-POSSIBLE-PSK-MISMATCH dc:97:ba:1c:15:dd Wed May 28 13:11:01 2025 daemon.err cli.lua[4119]: [0;33m[WARNING]: [0mct b004f812: time went backwards! Wed May 28 13:11:03 2025 daemon.err cli.lua[4119]: [0;33m[WARNING]: [0mct 684a53f4: time went backwards! Wed May 28 13:11:03 2025 daemon.err cli.lua[4119]: [0;33m[WARNING]: [0mct 684a53f4: time went backwards! Wed May 28 13:11:03 2025 daemon.err cli.lua[4119]: [0;33m[WARNING]: [0mct 684a53f4: time went backwards! Wed May 28 13:11:03 2025 daemon.err cli.lua[4119]: [0;33m[WARNING]: [0mct 9e8a842f: time went backwards! Wed May 28 13:11:07 2025 daemon.info hostapd: wl0: STA dc:97:ba:1c:15:dd IEEE 802.11: deauthenticated due to local deauth request Wed May 28 13:11:09 2025 daemon.err odhcp6c[5744]: Failed to send SOLICIT message to ff02::1:2 (Cannot assign requested address) Wed May 28 13:11:10 2025 daemon.err cli.lua[4119]: [0;33m[WARNING]: [0mct 7636ee18: time went backwards! Wed May 28 13:11:10 2025 daemon.err cli.lua[4119]: [0;33m[WARNING]: [0mct 7636ee18: time went backwards! Wed May 28 13:11:10 2025 daemon.err cli.lua[4119]: [0;33m[WARNING]: [0mct 7636ee18: time went backwards! Wed May 28 13:11:10 2025 daemon.err cli.lua[4119]: [0;33m[WARNING]: [0mct 7636ee18: time went backwards! Wed May 28 13:11:10 2025 daemon.err cli.lua[4119]: [0;33m[WARNING]: [0mct 7636ee18: time went backwards! Wed May 28 13:11:23 2025 daemon.err cli.lua[4119]: [0;33m[WARNING]: [0mct 7b87d916: time went backwards! Wed May 28 13:11:31 2025 daemon.err cli.lua[4119]: goto outTLS hook failed Wed May 28 13:11:47 2025 daemon.info hostapd: wl0: STA 1e:e5:6c:a3:1f:09 IEEE 802.11: associated Wed May 28 13:11:47 2025 daemon.info hostapd: wl1: STA 1e:e5:6c:a3:1f:09 IEEE 802.11: disassociated Wed May 28 13:11:47 2025 daemon.notice hostapd: wl1: AP-STA-DISCONNECTED 1e:e5:6c:a3:1f:09 Wed May 28 13:11:47 2025 daemon.info hostapd: wl1: STA 1e:e5:6c:a3:1f:09 IEEE 802.11: disassociated Wed May 28 13:11:47 2025 daemon.notice hostapd: wl0: AP-STA-CONNECTED 1e:e5:6c:a3:1f:09 Wed May 28 13:11:47 2025 daemon.info hostapd: wl0: STA 1e:e5:6c:a3:1f:09 RADIUS: starting accounting session B3DDB7DBD781CAC9 Wed May 28 13:11:47 2025 daemon.info hostapd: wl0: STA 1e:e5:6c:a3:1f:09 WPA: pairwise key handshake completed (RSN) Wed May 28 13:11:48 2025 daemon.err cli.lua[4119]: [0;33m[WARNING]: [0mct efa4e713: time went backwards! Wed May 28 13:11:49 2025 daemon.err cli.lua[4119]: [0;33m[WARNING]: [0mct 3fc0a91c: time went backwards! Wed May 28 13:11:49 2025 daemon.err cli.lua[4119]: [0;33m[WARNING]: [0mct 3fc0a91c: time went backwards! Wed May 28 13:11:52 2025 daemon.err cli.lua[4119]: goto outTLS hook failed Wed May 28 13:12:02 2025 daemon.err cli.lua[4119]: [0;33m[WARNING]: [0mct 7fe7f1a6: time went backwards! Wed May 28 13:12:02 2025 daemon.err cli.lua[4119]: [0;33m[WARNING]: [0mct 7fe7f1a6: time went backwards! Wed May 28 13:12:03 2025 daemon.err cli.lua[4119]: [0;33m[WARNING]: [0mct 25386a17: time went backwards! Wed May 28 13:12:03 2025 daemon.err cli.lua[4119]: [0;33m[WARNING]: [0mct 25386a17: time went backwards! Wed May 28 13:12:04 2025 daemon.err cli.lua[4119]: [0;33m[WARNING]: [0mct 4f34d642: time went backwards! Wed May 28 13:12:10 2025 daemon.err cli.lua[4119]: [0;33m[WARNING]: [0mct 6b162f21: time went backwards! Wed May 28 13:12:10 2025 daemon.err cli.lua[4119]: [0;33m[WARNING]: [0mct 6b162f21: time went backwards! Wed May 28 13:12:10 2025 daemon.err cli.lua[4119]: [0;33m[WARNING]: [0mct 6b162f21: time went backwards! Wed May 28 13:12:14 2025 daemon.info hostapd: wl1: STA 84:7b:57:3f:4d:32 IEEE 802.11: disassociated Wed May 28 13:12:14 2025 daemon.notice hostapd: wl1: AP-STA-DISCONNECTED 84:7b:57:3f:4d:32 Wed May 28 13:12:14 2025 daemon.info hostapd: wl1: STA 84:7b:57:3f:4d:32 IEEE 802.11: associated Wed May 28 13:12:14 2025 daemon.notice hostapd: wl1: AP-STA-CONNECTED 84:7b:57:3f:4d:32 Wed May 28 13:12:14 2025 daemon.info hostapd: wl1: STA 84:7b:57:3f:4d:32 RADIUS: starting accounting session 2040738D473B731F Wed May 28 13:12:14 2025 daemon.info hostapd: wl1: STA 84:7b:57:3f:4d:32 WPA: pairwise key handshake completed (RSN) Wed May 28 13:12:14 2025 daemon.info dnsmasq-dhcp[6532]: DHCPREQUEST(br-lan) 192.168.77.230 84:7b:57:3f:4d:32 Wed May 28 13:12:14 2025 daemon.info dnsmasq-dhcp[6532]: DHCPACK(br-lan) 192.168.77.230 84:7b:57:3f:4d:32 GBRV3NBO3NXCDK3 Wed May 28 13:12:14 2025 user.info com.netdumasoftware.neighwatch: DHCP old event. Wed May 28 13:12:14 2025 user.info com.netdumasoftware.neighwatch: DHCP lease change. Wed May 28 13:12:14 2025 user.info com.netdumasoftware.neighwatch: DHCP old event. Wed May 28 13:12:14 2025 user.info com.netdumasoftware.neighwatch: DHCP lease change. Wed May 28 13:12:17 2025 daemon.info dnsmasq-dhcp[6532]: DHCPREQUEST(br-lan) 192.168.77.230 84:7b:57:3f:4d:32 Wed May 28 13:12:17 2025 daemon.info dnsmasq-dhcp[6532]: DHCPACK(br-lan) 192.168.77.230 84:7b:57:3f:4d:32 GBRV3NBO3NXCDK3 Wed May 28 13:12:17 2025 user.info com.netdumasoftware.neighwatch: DHCP old event. Wed May 28 13:12:17 2025 user.info com.netdumasoftware.neighwatch: DHCP lease change. Wed May 28 13:12:17 2025 user.info com.netdumasoftware.neighwatch: DHCP old event. Wed May 28 13:12:17 2025 user.info com.netdumasoftware.neighwatch: DHCP lease change. Wed May 28 13:12:19 2025 daemon.warn dnsmasq[6532]: possible DNS-rebind attack detected: vodafone.powerhub Wed May 28 13:12:23 2025 daemon.warn dnsmasq[6532]: possible DNS-rebind attack detected: vodafone.powerhub Wed May 28 13:12:25 2025 daemon.warn dnsmasq[6532]: possible DNS-rebind attack detected: vodafone.powerhub Wed May 28 13:12:25 2025 daemon.warn dnsmasq[6532]: possible DNS-rebind attack detected: vodafone.powerhub Wed May 28 13:12:29 2025 daemon.err cli.lua[4119]: goto outTLS hook failed Wed May 28 13:12:31 2025 daemon.info hostapd: wl1: STA 84:7b:57:3f:4d:32 IEEE 802.11: disassociated Wed May 28 13:12:31 2025 daemon.notice hostapd: wl1: AP-STA-DISCONNECTED 84:7b:57:3f:4d:32 Wed May 28 13:12:35 2025 daemon.info hostapd: wl1: STA 84:7b:57:3f:4d:32 IEEE 802.11: associated Wed May 28 13:12:35 2025 daemon.notice hostapd: wl1: AP-STA-CONNECTED 84:7b:57:3f:4d:32 Wed May 28 13:12:35 2025 daemon.info hostapd: wl1: STA 84:7b:57:3f:4d:32 RADIUS: starting accounting session B78F18EF42E13834 Wed May 28 13:12:35 2025 daemon.info hostapd: wl1: STA 84:7b:57:3f:4d:32 WPA: pairwise key handshake completed (RSN) Wed May 28 13:12:35 2025 daemon.info dnsmasq-dhcp[6532]: DHCPREQUEST(br-lan) 192.168.77.230 84:7b:57:3f:4d:32 Wed May 28 13:12:35 2025 daemon.info dnsmasq-dhcp[6532]: DHCPACK(br-lan) 192.168.77.230 84:7b:57:3f:4d:32 GBRV3NBO3NXCDK3 Wed May 28 13:12:35 2025 user.info com.netdumasoftware.neighwatch: DHCP old event. Wed May 28 13:12:35 2025 user.info com.netdumasoftware.neighwatch: DHCP lease change. Wed May 28 13:12:35 2025 user.info com.netdumasoftware.neighwatch: DHCP old event. Wed May 28 13:12:35 2025 user.info com.netdumasoftware.neighwatch: DHCP lease change. Wed May 28 13:12:42 2025 daemon.info dnsmasq-dhcp[6532]: DHCPREQUEST(br-lan) 192.168.77.230 84:7b:57:3f:4d:32 Wed May 28 13:12:42 2025 daemon.info dnsmasq-dhcp[6532]: DHCPACK(br-lan) 192.168.77.230 84:7b:57:3f:4d:32 GBRV3NBO3NXCDK3 Wed May 28 13:12:42 2025 user.info com.netdumasoftware.neighwatch: DHCP old event. Wed May 28 13:12:42 2025 user.info com.netdumasoftware.neighwatch: DHCP lease change. Wed May 28 13:12:42 2025 user.info com.netdumasoftware.neighwatch: DHCP old event. Wed May 28 13:12:42 2025 user.info com.netdumasoftware.neighwatch: DHCP lease change. Wed May 28 13:12:43 2025 daemon.err cli.lua[4119]: [0;33m[WARNING]: [0mct 47a2bfca: time went backwards! Wed May 28 13:12:43 2025 daemon.err cli.lua[4119]: [0;33m[WARNING]: [0mct 47a2bfca: time went backwards! Wed May 28 13:12:43 2025 daemon.err cli.lua[4119]: [0;33m[WARNING]: [0mct d8a77bf0: time went backwards! Wed May 28 13:12:46 2025 daemon.err cli.lua[4119]: [0;33m[WARNING]: [0mct 20239ed4: time went backwards! Wed May 28 13:12:46 2025 daemon.err cli.lua[4119]: [0;33m[WARNING]: [0mct 20239ed4: time went backwards! Wed May 28 13:12:46 2025 daemon.err cli.lua[4119]: [0;33m[WARNING]: [0mct 20239ed4: time went backwards! Wed May 28 13:12:46 2025 daemon.err cli.lua[4119]: [0;33m[WARNING]: [0mct 20239ed4: time went backwards! Wed May 28 13:12:46 2025 daemon.err cli.lua[4119]: [0;33m[WARNING]: [0mct 5afef90c: time went backwards! Wed May 28 13:12:48 2025 daemon.err cli.lua[4119]: goto outTLS hook failed Wed May 28 13:12:51 2025 daemon.warn dnsmasq[6532]: possible DNS-rebind attack detected: vodafone.powerhub Wed May 28 13:12:53 2025 daemon.err cli.lua[4119]: [0;33m[WARNING]: [0mct 65f96a1d: time went backwards! Wed May 28 13:12:53 2025 daemon.err cli.lua[4119]: [0;33m[WARNING]: [0mct 65f96a1d: time went backwards! Wed May 28 13:12:53 2025 daemon.err cli.lua[4119]: [0;33m[WARNING]: [0mct 65f96a1d: time went backwards! Wed May 28 13:12:53 2025 daemon.err cli.lua[4119]: [0;33m[WARNING]: [0mct 65f96a1d: time went backwards! Wed May 28 13:12:53 2025 daemon.err cli.lua[4119]: [0;33m[WARNING]: [0mct 65f96a1d: time went backwards! Wed May 28 13:12:54 2025 daemon.warn dnsmasq[6532]: possible DNS-rebind attack detected: vodafone.powerhub Wed May 28 13:12:54 2025 daemon.warn dnsmasq[6532]: possible DNS-rebind attack detected: vodafone.powerhub Wed May 28 13:12:56 2025 daemon.warn dnsmasq[6532]: possible DNS-rebind attack detected: vodafone.powerhub Wed May 28 13:12:58 2025 daemon.warn dnsmasq[6532]: possible DNS-rebind attack detected: vodafone.powerhub Wed May 28 13:12:59 2025 daemon.err cli.lua[4119]: [0;33m[WARNING]: [0mct 3ed1a0e2: time went backwards! Wed May 28 13:12:59 2025 daemon.err cli.lua[4119]: [0;33m[WARNING]: [0mct 3507320a: time went backwards! Wed May 28 13:12:59 2025 daemon.err cli.lua[4119]: [0;33m[WARNING]: [0mct 3ed1a0e2: time went backwards! Wed May 28 13:12:59 2025 daemon.err cli.lua[4119]: [0;33m[WARNING]: [0mct 3ed1a0e2: time went backwards! Wed May 28 13:12:59 2025 daemon.err cli.lua[4119]: [0;33m[WARNING]: [0mct 3507320a: time went backwards! Wed May 28 13:13:01 2025 daemon.warn dnsmasq[6532]: possible DNS-rebind attack detected: vodafone.powerhub Wed May 28 13:13:01 2025 daemon.warn dnsmasq[6532]: possible DNS-rebind attack detected: vodafone.powerhub Wed May 28 13:13:03 2025 daemon.warn dnsmasq[6532]: possible DNS-rebind attack detected: vodafone.powerhub Wed May 28 13:13:04 2025 daemon.err odhcp6c[5744]: Failed to send SOLICIT message to ff02::1:2 (Cannot assign requested address) Wed May 28 13:13:04 2025 daemon.err cli.lua[4119]: goto outTLS hook failed Wed May 28 13:13:06 2025 daemon.err cli.lua[4119]: goto outTLS hook failed R3_2025-05-28T12_13_15.474Z_logs.txt Link to comment Share on other sites More sharing options...
Kahari Posted May 28 Share Posted May 28 Frasor, this is exactly what was happening to me 2 weeks ago prior to you having me upgrade the firmware. (Beta firmware) Link to comment Share on other sites More sharing options...
doddsbrah Posted May 28 Author Share Posted May 28 7 minutes ago, Kahari said: Frasor, this is exactly what was happening to me 2 weeks ago prior to you having me upgrade the firmware. (Beta firmware) Im pretty sure I’ve done that new firmware update 😕 still no luck Link to comment Share on other sites More sharing options...
doddsbrah Posted May 29 Author Share Posted May 29 @Netduma Fraserplease help Link to comment Share on other sites More sharing options...
Administrators Netduma Fraser Posted May 29 Administrators Share Posted May 29 I'm checking in with a dev with the log to see if they can determine the problem and will come back to you Link to comment Share on other sites More sharing options...
doddsbrah Posted May 29 Author Share Posted May 29 2 minutes ago, Netduma Fraser said: I'm checking in with a dev with the log to see if they can determine the problem and will come back to you Thank you, it’s becoming unusable at this point Link to comment Share on other sites More sharing options...
doddsbrah Posted June 2 Author Share Posted June 2 @Netduma Fraser hi has somebody looked into this for me? Link to comment Share on other sites More sharing options...
doddsbrah Posted June 3 Author Share Posted June 3 @Netduma Fraser I am very disappointed that this hasn’t been looked into, spent £200 on a router just to not be able to use it practically. Link to comment Share on other sites More sharing options...
doddsbrah Posted June 5 Author Share Posted June 5 @Netduma Fraser Has this been looked into? If not am I able to get a re fund? Link to comment Share on other sites More sharing options...
doddsbrah Posted June 6 Author Share Posted June 6 On 5/29/2025 at 3:28 PM, Netduma Fraser said: I'm checking in with a dev with the log to see if they can determine the problem and will come back to you Can’t believe I’m now being ignored - great customer service Link to comment Share on other sites More sharing options...
Administrators Netduma Fraser Posted June 6 Administrators Share Posted June 6 You're not being ignored, I just haven't got any new information yet that can help determine the issue/cause, as I said, I will come back to you when I hear back from a dev Link to comment Share on other sites More sharing options...
doddsbrah Posted June 6 Author Share Posted June 6 4 minutes ago, Netduma Fraser said: You're not being ignored, I just haven't got any new information yet that can help determine the issue/cause, as I said, I will come back to you when I hear back from a dev Ok thank you - I have a nagging wife that moans everytime she tries to use her laptop or tv! Lol Link to comment Share on other sites More sharing options...
Administrators Netduma Fraser Posted June 6 Administrators Share Posted June 6 1 hour ago, doddsbrah said: Ok thank you - I have a nagging wife that moans everytime she tries to use her laptop or tv! Lol Haha understood, hopefully will have some insight by Monday for you! Link to comment Share on other sites More sharing options...
doddsbrah Posted Sunday at 09:48 PM Author Share Posted Sunday at 09:48 PM On 6/6/2025 at 6:35 PM, Netduma Fraser said: Haha understood, hopefully will have some insight by Monday for you! I am thinking, could I have all WiFi devices connected to my main router, then just my PC as the only device connected to R3 and that’s through Ethernet? So only one devices connected to R3 then? Link to comment Share on other sites More sharing options...
Administrators Netduma Fraser Posted Sunday at 11:02 PM Administrators Share Posted Sunday at 11:02 PM 1 hour ago, doddsbrah said: I am thinking, could I have all WiFi devices connected to my main router, then just my PC as the only device connected to R3 and that’s through Ethernet? So only one devices connected to R3 then? Yes you could do that, although QoS then wouldn't be effective, you'd essentially then just be using it for the Geo-Filter Link to comment Share on other sites More sharing options...
doddsbrah Posted Monday at 05:33 AM Author Share Posted Monday at 05:33 AM 6 hours ago, Netduma Fraser said: Yes you could do that, although QoS then wouldn't be effective, you'd essentially then just be using it for the Geo-Filter Yea I’ll give it a go as I can’t continue with how it is Link to comment Share on other sites More sharing options...
Administrators Netduma Fraser Posted Monday at 02:09 PM Administrators Share Posted Monday at 02:09 PM Let us know how you get on. In the meantime it's been forwarded to a higher up dev but they are generally quite busy so may not be a quick turn around but I will update the post when I have info Link to comment Share on other sites More sharing options...
doddsbrah Posted Monday at 02:21 PM Author Share Posted Monday at 02:21 PM 11 minutes ago, Netduma Fraser said: Let us know how you get on. In the meantime it's been forwarded to a higher up dev but they are generally quite busy so may not be a quick turn around but I will update the post when I have info So far so good - the wifi devices are now connected via my original router with only my gaming PC connected by Ethernet to my R3. Have tested and seems like this may have solved the issue. Not ideal as I lose some of the features of the R3 but I good solution while we wait for future improvements which may help Link to comment Share on other sites More sharing options...
Administrators Netduma Fraser Posted Monday at 02:40 PM Administrators Share Posted Monday at 02:40 PM 19 minutes ago, doddsbrah said: So far so good - the wifi devices are now connected via my original router with only my gaming PC connected by Ethernet to my R3. Have tested and seems like this may have solved the issue. Not ideal as I lose some of the features of the R3 but I good solution while we wait for future improvements which may help That's good to hear, thanks for the update! Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now