What's new

Release Asuswrt-Merlin 386.5 is now available

  • SNBForums Code of Conduct

    SNBForums is a community for everyone, no matter what their level of experience.

    Please be tolerant and patient of others, especially newcomers. We are all here to share and learn!

    The rules are simple: Be patient, be nice, be helpful or be gone!

Status
Not open for further replies.
Dirty upgrade from previous. AX88U. Running without issues for a week, but router rebooted by itself today.
 
A little feedback : RT-AX88U + ONT ISP (WAN PORT)
I upgraded from 386.4 to 386.5 + WPS Reset + JFFS partition formatting and full configuration.
No problem to report for almost 8 days. I have not had any untimely reboots, everything is solid whether it is ethernet or wifi.
9.png
 
Can anyone confirm TimeMachine is fixed with 386.5. Thank you.
 
What version broke it?
 
Can anyone confirm TimeMachine is fixed with 386.5. Thank you.
See Post #221
 
There were posts that Time Machine was not working properly in 386.4. There were also posts of a fix, but I could find anything on when or where the fix was applied. I do not own a MAC, but my daughter does. She does not like to flash often, so I do not wish to ask her to flash then have to flash back.
 
After doing upgrades I noticed that Yaz-fi was no longer showing in GUI. I had to uninstall and re-install to get it working again. This isn't the first time this happened after an upgrade.

Should I be re-installing the other apps as well?
 
Dirty upgrade from 386.3_2 to 386.5

I reverted back to 386.3_2 from 386.4 after running into issues reaching certain websites with that update. 386.5 seems to be running well so far.
 
Hi,

The following are the System Log entries at the time I get dropouts on my Echo Studio I mentioned above. Is there anything anyone sees that might reveal a problem with my configuration? The Echo Studio is a 5Ghz device (the BRWD89C672EF0DA device is my Brother printer 2.4Ghz).

Mar 11 18:58:20 dnsmasq-dhcp[27064]: DHCPREQUEST(br0) 192.168.50.212 d8:9c:67:2e:f0:da
Mar 11 18:58:20 dnsmasq-dhcp[27064]: DHCPACK(br0) 192.168.50.212 d8:9c:67:2e:f0:da BRWD89C672EF0DA
Mar 11 19:03:03 hostapd: eth7: STA 64:6d:2f:61:b8:cd WPA: group key handshake completed (RSN)
Mar 11 19:03:03 hostapd: eth7: STA 4c:17:44:08:2b:ab WPA: group key handshake completed (RSN)
Mar 11 19:03:03 hostapd: eth7: STA 2c:db:07:57:8e:15 WPA: group key handshake completed (RSN)
Mar 11 19:03:03 hostapd: eth6: STA d8:9c:67:2e:f0:da WPA: group key handshake completed (RSN)
Mar 11 19:03:03 hostapd: wl0.2: STA 50:02:91:b2:81:26 WPA: group key handshake completed (RSN)
Mar 11 19:03:04 hostapd: wl0.2: STA 68:57:2d:d5:2d:49 WPA: group key handshake completed (RSN)
Mar 11 19:03:04 hostapd: wl0.2: STA 68:57:2d:d4:79:d9 WPA: group key handshake completed (RSN)
Mar 11 19:03:04 hostapd: wl0.2: STA 68:57:2d:d4:7b:d5 WPA: group key handshake completed (RSN)
Mar 11 19:03:04 hostapd: wl0.2: STA 9a:1c:76:52:0b:84 WPA: group key handshake completed (RSN)
Mar 11 20:01:50 kernel: httpd (1545): drop_caches: 1

Thanks,
Anton
 
Hi,

The following are the System Log entries at the time I get dropouts on my Echo Studio I mentioned above. Is there anything anyone sees that might reveal a problem with my configuration? The Echo Studio is a 5Ghz device (the BRWD89C672EF0DA device is my Brother printer 2.4Ghz).



Thanks,
Anton

Mar 11 18:58:20 dnsmasq-dhcp[27064]: DHCPREQUEST(br0) 192.168.50.212 d8:9c:67:2e:f0:da
Mar 11 18:58:20 dnsmasq-dhcp[27064]: DHCPACK(br0) 192.168.50.212 d8:9c:67:2e:f0:da BRWD89C672EF0DA

DHCP Lease Renewal - Normal

Mar 11 19:03:03 hostapd: eth7: STA 64:6d:2f:61:b8:cd WPA: group key handshake completed (RSN)
Mar 11 19:03:03 hostapd: eth7: STA 4c:17:44:08:2b:ab WPA: group key handshake completed (RSN)
Mar 11 19:03:03 hostapd: eth7: STA 2c:db:07:57:8e:15 WPA: group key handshake completed (RSN)
Mar 11 19:03:03 hostapd: eth6: STA d8:9c:67:2e:f0:da WPA: group key handshake completed (RSN)
Mar 11 19:03:03 hostapd: wl0.2: STA 50:02:91:b2:81:26 WPA: group key handshake completed (RSN)
Mar 11 19:03:04 hostapd: wl0.2: STA 68:57:2d:d5:2d:49 WPA: group key handshake completed (RSN)
Mar 11 19:03:04 hostapd: wl0.2: STA 68:57:2d:d4:79:d9 WPA: group key handshake completed (RSN)
Mar 11 19:03:04 hostapd: wl0.2: STA 68:57:2d:d4:7b:d5 WPA: group key handshake completed (RSN)
Mar 11 19:03:04 hostapd: wl0.2: STA 9a:1c:76:52:0b:84 WPA: group key handshake completed (RSN)

WEP Key update - normal

Mar 11 20:01:50 kernel: httpd (1545): drop_caches: 1

Don't know why there is an issue with the web server, yet it's not related to communications

Morris
 
I'm using this DNS setttings, and second time within last week I got no DNS response to clients, had to restart the router to make it work. Only after router reboot got DNS resolution again.
 

Attachments

  • dns.png
    dns.png
    61.3 KB · Views: 211
I'm using this DNS setttings, and second time within last week I got no DNS response to clients, had to restart the router to make it work. Only after router reboot got DNS resolution again.

I've had similar experiences using encrypted DNS. Eventually I abended using encrypted DNS and have not had a problem since. Also, you are splitting your DNS redundancy between two DNS providers. While this seems a reliable choice at first chance, it probably reduces reliability as the each provider provide geographic and network redundancy. Since you have no idea if the choices of DNS services will survive a geographic or network reliability issue, you are better to chose one as there engineers have made a considerable investment in time and equipment to provide reliable service.

Morris
 
I'm using this DNS setttings, and second time within last week I got no DNS response to clients, had to restart the router to make it work. Only after router reboot got DNS resolution again.

When I select those DoT preset servers on Asuswrt, there are no TLS Port entries. I wonder why the difference.

OE
 
I entered those manually

Without knowing, I'd reduce to one provider and no TLS Port entries and see what happens.

OE
 
Try reconfiguring that Guest in case for some reason the passphrase might be corrupted, or some of the low-level Guest settings were corrupted.
I've tried completely resetting the device (it's an IP camera by the way), but that didn't work.

I've tried numerous things, including changing the guest SSID and such. The only way I'm able to connect it is when protected management frames are disabled, and no guest network is configured on that band. Enabling any guest network, or setting the protected management frames to anything but disabled, causes the device to disconnect.

The log indicates the device is not authenticated with the current station or something in that direction, which makes me believe the protected management frames are enabled in the broadcom driver as soon as a guest SSID is enabled, regardless of the wireless setting in the firmware.
 
Status
Not open for further replies.

Latest threads

Sign Up For SNBForums Daily Digest

Get an update of what's new every day delivered to your mailbox. Sign up here!
Top