Jump to content

kevwhite

R2 Early Access
  • Posts

    23
  • Joined

  • Last visited

Everything posted by kevwhite

  1. Thanks for a response at such a late time! I'll re-test it this weekend I've downgraded to 219 just for stability as i'll get sacked if I continue with the same connection tomorrow lol
  2. Hello Guys, I upgraded to the latest firmware for the R3 2 days ago and since then I've had my connection drop multiple times. I haven't rebooted the router and the uptime is 2 days. I have logs if you wish to have a look. I work for the health service and access to my VPN with them has dropped (VPN isn't configured via the router). I have logs aswell but I wouldn't want to post the logs on here just given there is some data in them relating to the health service. Also got times of drops and it does look like it has parts like the below in the logs: Tue Aug 27 16:13:40 2024 kern.warn kernel: br-lan: received packet on wl0 with own address as source address (addr:44:10:91:6a:7c:21, vlan:0) Tue Aug 27 16:13:40 2024 kern.warn kernel: wl1: random key value: 35F1D02AEDE0847F3E0F013127E3758A1200619123BB0118F3F33A64391C9DD9 Tue Aug 27 16:13:40 2024 daemon.info hostapd: wl0: STA 78:af:08:53:00:f7 IEEE 802.11: associated Tue Aug 27 16:13:40 2024 daemon.info hostapd: wl1: STA 78:af:08:53:00:f7 IEEE 802.11: disassociated Tue Aug 27 16:13:40 2024 daemon.notice hostapd: wl1: AP-STA-DISCONNECTED 78:af:08:53:00:f7 Tue Aug 27 16:13:40 2024 daemon.info hostapd: wl1: STA 78:af:08:53:00:f7 IEEE 802.11: disassociated Tue Aug 27 16:13:40 2024 daemon.notice hostapd: wl0: AP-STA-CONNECTED 78:af:08:53:00:f7 Tue Aug 27 16:13:40 2024 daemon.info hostapd: wl0: STA 78:af:08:53:00:f7 RADIUS: starting accounting session 70362CFA1168507C Tue Aug 27 16:13:40 2024 daemon.info hostapd: wl0: STA 78:af:08:53:00:f7 WPA: pairwise key handshake completed (RSN) Tue Aug 27 16:13:40 2024 daemon.info dnsmasq-dhcp[6345]: DHCPREQUEST(br-lan) 192.168.77.181 78:af:08:53:00:f7 Tue Aug 27 16:13:40 2024 daemon.warn dnsmasq-dhcp[6345]: Ignoring domain REDACTED for DHCP host name LP316688 Tue Aug 27 16:13:40 2024 daemon.info dnsmasq-dhcp[6345]: DHCPACK(br-lan) 192.168.77.181 78:af:08:53:00:f7 LP316688 Tue Aug 27 16:13:40 2024 user.info com.netdumasoftware.neighwatch: DHCP old event. Tue Aug 27 16:13:40 2024 user.info com.netdumasoftware.neighwatch: DHCP lease change. Tue Aug 27 16:13:40 2024 user.info com.netdumasoftware.neighwatch: DHCP old event. Tue Aug 27 16:13:40 2024 user.info com.netdumasoftware.neighwatch: DHCP lease change. Tue Aug 27 16:13:40 2024 daemon.warn odhcpd[2641]: No default route present, overriding ra_lifetime! Tue Aug 27 16:13:41 2024 daemon.warn odhcpd[2641]: No default route present, overriding ra_lifetime! Tue Aug 27 16:13:42 2024 daemon.info dnsmasq-dhcp[6345]: DHCPREQUEST(br-lan) 192.168.77.181 78:af:08:53:00:f7 Tue Aug 27 16:13:42 2024 daemon.warn dnsmasq-dhcp[6345]: Ignoring domain REDACTED for DHCP host name LP316688 Tue Aug 27 16:13:42 2024 daemon.info dnsmasq-dhcp[6345]: DHCPACK(br-lan) 192.168.77.181 78:af:08:53:00:f7 LP316688 Hope you can help.
  3. After downgrade / wipe / upgrade I've been fine. I had those same issues you mention where my blink doorbell stopped connecting too but since my changes it's working.
  4. Just an update - downgraded to .23.. then upgraded to .41 and factory reset and it's now working. Will monitor and see how it goes.
  5. I'm getting similar - since the upgrade to .41 some wifi devices like my blink doorbell wont connect to it - tried splitting to 2.4 and 5ghz but still wont. Blink have sent me a replacement device as I thought it was that but even the replacement isn't connecting. Will downgrade to .23 at the moment. Fraser if you need any logs let me know and I can grab some for you
×
×
  • Create New...