What's new

Beta Asuswrt-Merlin 3006.102.2 Beta is now available for Wifi 7 devices

  • 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.
I have updated BE88U to beta and cannot acces router, got internet etc, just GUI is not working, no matter if I use IP or http://www.asusrouter.com/ any clues? I have tried restart and no luck, it is quite problematic now. Any help would be appreciated!

Openvpn not working either, is there anything I can do apart reset?
Do you use the app for access?
Use https and should attach the port in the end?
 
Do you use the app for access?
Use https and should attach the port in the end?
I've been using 99% web gui, app got no access aswell, I have tried http but no luck, however what port should I use?

I've got AX86 running as mesh node, it is working and when I was trying to log into it by going through node IP it said that I cannot be connected asI can't connect to the main router or something like that.

Tried https://192.168.50.1:8443 with same result, I do not have ssh enabled... any other thing that I can check?

I will do factory reset if it wont help then well, warranty time
 
Last edited:
Works well on BE88U.
The only issue I experience is the spike in the "Traffic Monitor":
2024-10-29_18.11.44.142_Traffic Monitor_24H.png


And I found some suspicious traffic coming from nowhere:
2024-10-29_18.33.55.266_eth5.png

eth9 is connected to a NAS, but there's no way to have this traffic.
2024-10-29_14.32.35.282_eth9.png


Haven't tried the stock firmware, so don't know if it's an issue from ASUS or what.

---------------Edit------------
I found that each spike seems to contribute 256TiB to the corresponding traffic, so these abnormal numbers are all pretty much the multiple of 256TiB. E.g.:Another spike and now the TX of eth9 is 768TiB:
2024-10-31_01.56.30.768_putty_ftp-user@ssh192.168.33.123_-_KiTTY.png
 
Last edited:
Works well on BE88U.
The only issue I experience is the spike in the "Traffic Monitor":
View attachment 62209

And I found some suspicious traffic coming from nowhere:
View attachment 62210
eth9 is connected to a NAS, but there's no way to have this traffic.
View attachment 62211

Haven't tried the stock firmware, so don't know if it's an issue from ASUS or what.
Did you have VPN settings or anything on it prior flashing this firmware? As I cannot connect with GUI now and I am afraid device is broken...
 
Did you have VPN settings or anything on it prior flashing this firmware? As I cannot connect with GUI now and I am afraid device is broken...
No. I didn't even use the stock firmware and flashed the beta 1 the moment I got into the GUI.
You mean your device is dead, suddenly?
 
Hi Merlin, do you know why there is such issue in restarting service-event for RT-BE86U (FW 3006.102.2_beta1):


?

Is it FW related, as suggested from some other users in that thread?
 
No. I didn't even use the stock firmware and flashed the beta 1 the moment I got into the GUI.
You mean your device is dead, suddenly?
Mhm in my case even reset button is not working

Ok after 15 min of reset attempts I finally wwas able to reset via reset button, it is working now, I would sugghest everyone to reset to defaults before flashing merlin.
 
Last edited:
Hi Merlin, do you know why there is such issue in restarting service-event for RT-BE86U (FW 3006.102.2_beta1):


?

Is it FW related, as suggested from some other users in that thread?
Sorry, not gonna read through a 12 pages long thread... What issue specifically? Your post only indicates Scribe logging something. I have no idea how Scribe works or what it does...
 
Sorry, not gonna read through a 12 pages long thread... What issue specifically? Your post only indicates Scribe logging something. I have no idea how Scribe works or what it does...
The issue is related to the service-event invoked by scribe restart; it floods the syslog in the attempt of restarting autowan, as I've indicated in that post. It seems related to only RT-BE86U, since GT-BE98 does not suffer of the same problem
 
The issue is related to the service-event invoked by scribe restart; it floods the syslog in the attempt of restarting autowan, as I've indicated in that post. It seems related to only RT-BE86U, since GT-BE98 does not suffer of the same problem
Constant "restart autowan" events are normal in 102_36xxx. They are hidden by Asus in the rest of the firmware, but will appear if you have custom scripts that reports on every single events. I can try to reapply their same workaround for service-event logging, but if scribe logs every single event, then it will be scribe's responsibility to also hide them if they are judged problematic.
 
3006.102.2 is now available, locking this. Thank you to those who participated in this beta cycle.
 
Status
Not open for further replies.

Latest threads

Support SNBForums w/ Amazon

If you'd like to support SNBForums, just use this link and buy anything on Amazon. Thanks!

Sign Up For SNBForums Daily Digest

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

Members online

Top