i should have said an "additional" reboot. 1st being the flash itself.Thanks. Let me try at next firmware upgrade with double reboot.
i should have said an "additional" reboot. 1st being the flash itself.Thanks. Let me try at next firmware upgrade with double reboot.
Yet no-one else is reporting it.
Try forgetting the network on the iPhone, then reconnect.
Have you tried a factory reset with minimal setup after updating?
Upon reading your and MDM's comments and doing a factory reset yesterday, setting up everything again from scratch, WG still dies after some hours.While you can do a factory reset before installing new firmware, you should be doing the factory reset AFTER flashing the new firmware, if you are going to be doing a factory reset. Doing the factory reset AFTER flashing the firmware insures (or should insure) the new firmware's default settings are used.
Edit to add: Asus is now strongly recommending a factory default reset after installing the latest Asus stock firmware releases for certain routers. (see here, here, here, here for recent examples)
I would think the virtual interfaces represent the wired and wireless interfaces that can, in part, be assigned to or already are VLAN's.
Then posting your VPN settings would be the next thing, in maybe a separate thread, since it seems not to be FW related but probably config...Upon reading your and MDM's comments and doing a factory reset yesterday, setting up everything again from scratch, WG still dies after some hours.
What should I try next?
Answer is likely simple. You likely have a main LAN WiFI and then several Guest Network WiFi profiles (br55, br56) enabled. Coupled with it being a WiFi 7 router (RT-BE88U) meaning more than two wireless channels/bands, and likely what I assume are multiple WiFi virtual interfaces to handle the WiFi 4 (802.11n), WiFi 5 (802.11ac), WiFi 6 (802.11ax), and WiFi 7 (802.11be). Along with a mix of 9 x LAN ports of various speeds and one 10Gbps SFP+ Port. Further Asus may set aside additional vlans for AiMesh as well (possibly even if you don't enable AiMesh).Thanks, but that's not it. 'wl' interfaces are wireless. Anything that starts with wl0 is the 2.4 ghz band and wl1 is the 5 ghz band. Still unclear why there would be 4 wireless virtual interfaces instead of 2 on those bridges (and 5 of them on the main br0).
As already suggested, perhaps start a separate discussion on your issue since it may not be firmware related.Upon reading your and MDM's comments and doing a factory reset yesterday, setting up everything again from scratch, WG still dies after some hours.
What should I try next?
i dont have any issue with wireguard. you might want to check your configuration. might be some misconfig when u extracting your nordvpn settingsUpon reading your and MDM's comments and doing a factory reset yesterday, setting up everything again from scratch, WG still dies after some hours.
What should I try next?
Ditto... using WG on main lan and a different one for guest. On initial setup I had an issue with a specific WG server, but created a new profile for a different server in the same endpoint city and it has stayed stable for many days. Note I'm using Proton VPN with WG.i dont have any issue with wireguard. you might want to check your configuration. might be some misconfig when u extracting your nordvpn settings
Ask ASUS or Trend Micro...Same here. Anybody trying to fix it?
I just ran the update.Not FW related, but noticed Trend Micro Signature update is down...
View attachment 67297View attachment 67298
True, it seems they fixed it.I just ran the update.
Want to confirm the same issue:RT-BE92 here, was on the previous stable .4 and upgraded to this stable version .5 via dirty flash.
Have an RT-AX56 as mesh node with ethernet backhaul.
Can get WAN access from the RT-AX56 but not LAN:
Have a Home Assistant server running on the main network (wired connection) and Android device or Win laptop when connected to the AX56 on the main network SSID can no longer find my Home Assistant server. Quite annoying as I need the mesh node to connect when I arrive home to operate the garage or front door. Without access, that's no longer possible so Mrs is giving me grief
With .4 this was working as expected.
I deleted the mesh node and re-established it with the same outcome. Any ideas?
Once I deleted the previous Captive Portal Guest Network, and re-created it, all is well...thanks!! That's what I get for a dirty upgrade....Dirty upgrade, no real issues, SSH session right after reboot seemed to lock up, but another reboot via GUI fixed...
Still no joy with Captive Portal on Guest Network, even with favicon added, any updates? (Couldn't find the thread in the beta discussions that talked about it....)
Thanks for all the hard work!!!
Welcome To SNBForums
SNBForums is a community for anyone who wants to learn about or discuss the latest in wireless routers, network storage and the ins and outs of building and maintaining a small network.
If you'd like to post a question, simply register and have at it!
While you're at it, please check out SmallNetBuilder for product reviews and our famous Router Charts, Ranker and plenty more!