Jump to content

Wifi drops when I turn on PC which is connected via Ethernet


Recommended Posts

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

@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

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

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

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

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

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

  • Administrators
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

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

  • Administrators
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

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 account

Sign in

Already have an account? Sign in here.

Sign In Now
 Share

×
×
  • Create New...