What's new

Beta Asuswrt-Merlin 388.1 Beta is available for select models

  • 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.
Nothing strange there. As I mentioned, that feature does not work with the kernel 4.19 used by these newer models. That setting was simply not doing anything, hence its removal from these models that don't support it.

Is this only related to AsusWRT-Merlin? Or does that mean the official firmware is misleading? As the option is there on the GT-AX6000 when running 3.0.0.4.388.21617 to change from Symmetrical to Full-Cone NAT. Haven't been able to test or verify if the change is actually doing anything, but I would find it strange for Asus to keep the toggle on the GT-AX6000 if the toggle doesn't affect anything.
 
but I would find it strange for Asus to keep the toggle on the GT-AX6000 if the toggle doesn't affect anything.
You must be new to Asus hardware then, this has happened many times with all kinds of devices they develop. The key word is develop, as this is a continued effort. Some things fall through the cracks man, but at least they get corrected in due time.
 
ax88u
tragic thing it works on 388.1 b3.
Each page turn on the router takes at least a minute or even two.
(before throwing 388b3 total factory reset and cleaning nvram). pages in browsers also crashed
I'm going back to the factory 388.20558 - it's definitely several dozen times faster. too bad too bad...
 
ax88u
tragic thing it works on 388.1 b3.
Each page turn on the router takes at least a minute or even two.
(before throwing 388b3 total factory reset and cleaning nvram). pages in browsers also crashed
I'm going back to the factory 388.20558 - it's definitely several dozen times faster. too bad too bad...
I have an AX88U and don't have the issue you have. I would flash the beta again, and because you are coming from stock, a reset to factory defaults AFTER the flash of the beta 3 firmware. Coming from stock it's highly advised to reset to defaults by @RMerlin himself.
 
ax88u
tragic thing it works on 388.1 b3.
Each page turn on the router takes at least a minute or even two.
(before throwing 388b3 total factory reset and cleaning nvram). pages in browsers also crashed
I'm going back to the factory 388.20558 - it's definitely several dozen times faster. too bad too bad...


Hard reseting the router BEFORE flashing a new version of the FW does not and cannot help at all...


Reset the router AFTER flashing a new version. Try it and then report back.

Good luck!
 
I did write it. After uploading beta 3, there were already 4 factory resets. It didn't change anything. I just uploaded the last factory one - it runs elegantly
 
I did write it. After uploading beta 3, there were already 4 factory resets. It didn't change anything. I just uploaded the last factory one - it runs elegantly
Are you importing settings that you have saved? Like from a settings file? If so DON'T import the file. Reset to defaults and manually reconfigure to avoid importing the broken settings.
 
Are you importing settings that you have saved? Like from a settings file? If so DON'T import the file. Reset to defaults and manually reconfigure to avoid importing the broken settings.
no, I configured router manually.
 
The other thing to try is reset to defaults and setup your WAN connection and WiFi in the quick connect wizard. Once done that, try the navigation at that point.
 
If it works okay add your preferred settings one at a time to find the breaking point.
 
AX88U- 4 days uptime with Beta3, no issues so far.
 

Attachments

  • Screenshot_20221127_020305.jpg
    Screenshot_20221127_020305.jpg
    16.9 KB · Views: 42
Ax56U- after an unusuall crash was 2 days ago, I manually reboot the router from the GUI for healthier proccess of tests and debug.

For now, 2 days and no issues.
Will keep monitor untill Beta4 or Stable release will be out.
 

Attachments

  • Screenshot_20221127_020447.jpg
    Screenshot_20221127_020447.jpg
    15.1 KB · Views: 44
Hard reseting the router BEFORE flashing a new version of the FW does not and cannot help at all...


Reset the router AFTER flashing a new version. Try it and then report back.
If this problem is encountered resetting to factory defaults and reconfigure doesn't help.
I have no idea what's causing it but I see it on multiple routers (GT-AX11000 and XT12) and, IIRC, I have seen it on stock firmware as well.
Once it starts it doesn't stop, GUI starts seeing the long hangs after 12-24 hours following the factory reset, making it unusable.
The GT-AX11000 doesn't have a stock 388 yet which is what I have gone back too since the XT12 has wifi disconnect problems (both Merlin and stock) which a factory reset doesn't resolve.
The AX11000 feels like it's about the best behaved router I have ...
 
Is this only related to AsusWRT-Merlin?
No, it`s related to the kernel, therefore it will be the same on both Asuswrt and Asuswrt-Merlin.

I would find it strange for Asus to keep the toggle on the GT-AX6000 if the toggle doesn't affect anything.
Asus weren't aware until recently that the setting did not work on newer HND 5.04 models, Broadcom had only implemented it on the 5.02 models. The setting will also be removed from the next stock firmware release as it`s not doing anything at all.
 
I'm done with this worthless site and all the elitists. Merlin, I really do appreciate all you do though. Do not ever give up and keep on doing what you are doing..

"Did you reboot your router?" FFS I was doing TCP/IP and Linux before you were in diapers. Trumpet Winsock on Windows 3.1 with DoS?

My post went to the dumpster so ya'll can bitch about wifi I had an actual concern but from previous posts I see how this community beyond Merlin is. I have a bigger pen1s than you do.

It's not all of you - some of you ACTUALLY look over logs and give solutions. But way too many of you need to stop bashing people that are reasonable in their requests and concerns.

OH WELL SCRUB

Y'all Need Jesus

MODS please nuke my account
Well somebody spoke the truth. Good on you man, and goodbye I guess?
 
Running beta 3 since it was released on AX-88U and had no hiccups.
Only thing to mention maybe was that after a day or so my wireguard cliënt speed was cut in half.
Disabling and enabling it again solved it, could well be an VPN provider issue but mentioning it is maybe usefull.
 
No, it`s related to the kernel, therefore it will be the same on both Asuswrt and Asuswrt-Merlin.


Asus weren't aware until recently that the setting did not work on newer HND 5.04 models, Broadcom had only implemented it on the 5.02 models. The setting will also be removed from the next stock firmware release as it`s not doing anything at all.

Hmm, that is disappointing. So I have to choose between a 2.5Gbps downlink to my switch (10Gbps if I go with the GT-AX11000 Pro) or Full-Cone NAT on my RT-AX88U. When stuck with Symmetrical NAT solutions like building a small form factor X86-64 system and running OPNsense becomes a possibility as well.
 
Quite honestly, I ignore any Wifi-related complains. Because out of 10 complains, 9 of them turn out to be configuration issues, or caused by people using cheap, broken IoT wifi clients. There are wifi-related complains with every single release. I refuse to become an unpaid tech support devoting hours of my time trying to investigate every single issue, and I'm can't expect their engineers to start devoting time and resources helping people troubleshoot their network just for the odd case that there _might_ be a genuine issue. That's the job of the tech support department, not the engineering department.
Quite right. Been trying and testing Beta1-3 on AX86U. Finally solved this


Code:
Nov 26 06:18:45 acsd: eth6: COEX: downgraded chanspec 0x1906 (8) to 0x1008 (8): channel 1 used by exiting BSSs
Nov 26 06:33:50 acsd: eth6: COEX: downgraded chanspec 0x1906 (8) to 0x1008 (8): channel 1 used by exiting BSSs
Nov 26 06:48:55 acsd: eth6: COEX: downgraded chanspec 0x1906 (8) to 0x1008 (8): channel 1 used by exiting BSSs

Checked Wireless Log and saw Apple watch connected to 5Ghz (with WiFi 6 ) when it is capable of 802.11n only (Streams 1 (n) 20MHz and iPhone showing Streams 2 (ax) 80Mhz.) Thought it was “essential” to have it on the same SSID with my phone. Switch it to 2.4Ghz Guest, no more acsd log now.

But still can’t work out what this is, only appear in Beta 3 i think.
Code:
Nov 26 18:25:57 rc_service: conn_diag 1766:notify_rc restart_amas_portstatus
Nov 26 18:25:57 custom_script: Running /jffs/scripts/service-event (args: restart amas_portstatus)

WiFi signal has improved significantly imo with Beta 3. iPhone in bathroom reading RSSI -70 dBm.

Thank you for all the hard work @RMerlin
 
Hmm, that is disappointing. So I have to choose between a 2.5Gbps downlink to my switch (10Gbps if I go with the GT-AX11000 Pro) or Full-Cone NAT on my RT-AX88U. When stuck with Symmetrical NAT solutions like building a small form factor X86-64 system and running OPNsense becomes a possibility as well.
It's a bit puzzling really.
There is an implementation around which might be able to be merged into either ASUS or Merlin firmware and yet we are left with "gaming routers" that can't do full cone NAT so anyone with two or more Xbox consoles will have problems ...
 
Status
Not open for further replies.

Similar threads

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!
Top