Menu
What's new
By:
Filters Better Search

Beta Asuswrt-Merlin 386.1 Beta (stage 2) 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.
brummygit said:
Tried that, tried almost every normal setting for stabilising 2.4Ghz.

802.11ax = disable
Wifi Agile Multiband = disable
Target Wake Time = disable
Protected Management Frames = disable
Universal Beamforming = disable

It was working fine this morning using stock firmware on the RT-AX88U and beta4 on the RT-AX56Us (versions still in my signature). I've just put my emergency RT-AC68U in place as an AP running stock 386_41634 and everything connected up and worked perfectly using the AX88U as the router
Click to expand...
There's definitely something strange going on with 2.4Ghz in my setup using Beta 5. My RT-AX56Us as mesh nodes for the RT-AX88U have the issues with devices struggling to connect and getting poor performance. I tested with my RT-AC68U as an AP and it worked fine. So I upgraded it to beta5 then when I added it as a mesh node it suddenly started with the problems. Downgrading it to stock 386_41634 and it still had the same issues until I removed it from the mesh and configured it as an AP again. WiFi configuration was the same on both RT-AX88U and RT-AC68U for these tests.

I didn't see this on the 386_41535 code base (but I did have other issues) so I wonder if the WIFI SDK has been updated between the releases for the AX routers and its pushing different settings out to the RT-AC68U when it's in mesh mode.

It looks like I need to regress for now.
 
Can we expect the Daylight Saving Issue to be fixed in this final release? Looking through the changelog it seems the beta5 release does not address any fixes in this space.
 
gspannu said:
A question on VPN server:
- Are you running IKEv1 or IKEv2? Are both supported in beta5?
Click to expand...
Oops ... I don't really know the answer. However if you see my configuration I selected both V1 + V2 for supported IKE version.
 

Attachments

  • Screenshot 2021-01-27 at 07.40.48.png
    Screenshot 2021-01-27 at 07.40.48.png
    92.8 KB · Views: 106
rx2 said:
Can we expect the Daylight Saving Issue to be fixed in this final release? Looking through the changelog it seems the beta5 release does not address any fixes in this space.
Click to expand...
What Daylight Saving issue? You mean the fact that you may have to manually adjust the weeks? That's because not all countries and territories apply the same rules and dates, it is not a flaw in the router programming.
 
Hi, reporting another successful dirty upgrade from beta4b to beta5 over my RT-AX88U router and RT-AX56U mesh client about 1 hour ago. I can observe a bit faster throughput and good 2.4Ghz coverage although only at 20Mhz channel width (won't try 40Mhz since living in a crowded area). Also Samba seems like working fine for me plus ovpn, trendmicro ON, diversion, and all the scripting. Thanks Merlin & team !
Will report if anything strange is observed in the next few days.
 
Last edited:
brummygit said:
There's definitely something strange going on with 2.4Ghz in my setup using Beta 5. My RT-AX56Us as mesh nodes for the RT-AX88U have the issues with devices struggling to connect and getting poor performance. I tested with my RT-AC68U as an AP and it worked fine. So I upgraded it to beta5 then when I added it as a mesh node it suddenly started with the problems. Downgrading it to stock 386_41634 and it still had the same issues until I removed it from the mesh and configured it as an AP again. WiFi configuration was the same on both RT-AX88U and RT-AC68U for these tests.

I didn't see this on the 386_41535 code base (but I did have other issues) so I wonder if the WIFI SDK has been updated between the releases for the AX routers and its pushing different settings out to the RT-AC68U when it's in mesh mode.

It looks like I need to regress for now.
Click to expand...

the wifi has been broken for donkey's years very buggy not as good as fritz box to many brodcom hacks etc in it
 
elorimer said:
It does on my ac86U. You might need to restart unbound or run the stats first.
Click to expand...
Updating stats did nothing, restarting unbound made the graphs appear again. But...a router reboot wiped it all out again until I forced another unbound restart. May not be a beta 5 issue, didn't notice before with 384.19.

Edit: Or does it require a different setting during install to appear permanently?
 
Last edited:
FTC said:
Hi, reporting another successful dirty upgrade from beta4b to beta5 over my RT-AX88U router and RT-AX56U mesh client about 1 hour ago. I can observe a bit faster throughput and good 2.4Ghz coverage although only at 20Mhz channel width (won't try 40Mhz since living in a crowded area). Also Samba seems like working fine for me plus ovpn, trendmicro ON, diversion, and all the scripting. Thanks Merlin & team !
Will report if anything strange is observed in the next few days.
Click to expand...
Interesting - it could be new defaults introduced in the GPL used for beta5. I did a full reset after upgrading. I'm just going back to beta4b / beta4 with a full reset to see if it helps me. If that is stable again for a day or two I might try a dirty upgrade if the lynch mob go out for any period of time.
 
RMerlin said:
Can you post the output of ifconfig on your router?
Click to expand...
Here it is:
Code: 
bond0     Link encap:Ethernet  HWaddr 04:D4:C4:50:81:C0 
          inet6 addr: fe80::6d4:c4ff:fe50:81c0/64 Scope:Link
          UP BROADCAST RUNNING ALLMULTI MASTER MULTICAST  MTU:1500  Metric:1
          RX packets:15892376 errors:0 dropped:44 overruns:0 frame:0
          TX packets:6155090 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:20218454157 (18.8 GiB)  TX bytes:1179581960 (1.0 GiB)

br0       Link encap:Ethernet  HWaddr 04:D4:C4:50:81:C0 
          inet addr:192.168.33.1  Bcast:192.168.33.255  Mask:255.255.255.0
          inet6 addr: 240e:38b:86bf:fd00::1/56 Scope:Global
          inet6 addr: fe80::6d4:c4ff:fe50:81c0/64 Scope:Link
          UP BROADCAST RUNNING ALLMULTI MULTICAST  MTU:1500  Metric:1
          RX packets:17325113 errors:0 dropped:48 overruns:0 frame:0
          TX packets:10768205 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:20125041467 (18.7 GiB)  TX bytes:7806230790 (7.2 GiB)

eth0      Link encap:Ethernet  HWaddr 04:D4:C4:50:81:C0 
          inet addr:169.254.84.159  Bcast:169.254.255.255  Mask:255.255.0.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:10598499 errors:0 dropped:56 overruns:0 frame:0
          TX packets:16904116 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:7505316483 (6.9 GiB)  TX bytes:20437451108 (19.0 GiB)

eth0.51   Link encap:Ethernet  HWaddr 04:D4:C4:50:81:C0 
          inet6 addr: fe80::6d4:c4ff:fe50:81c0/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:3 errors:0 dropped:0 overruns:0 frame:0
          TX packets:66 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:126 (126.0 B)  TX bytes:8632 (8.4 KiB)

eth0.85   Link encap:Ethernet  HWaddr 04:D4:C4:50:81:C0 
          inet6 addr: fe80::6d4:c4ff:fe50:81c0/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:3 errors:0 dropped:0 overruns:0 frame:0
          TX packets:68 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:126 (126.0 B)  TX bytes:8796 (8.5 KiB)

eth0:1    Link encap:Ethernet  HWaddr 04:D4:C4:50:81:C0 
          inet addr:192.168.1.33  Bcast:192.168.1.255  Mask:255.255.255.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1

eth1      Link encap:Ethernet  HWaddr 04:D4:C4:50:81:C0 
          inet6 addr: fe80::6d4:c4ff:fe50:81c0/64 Scope:Link
          UP BROADCAST ALLMULTI MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

eth2      Link encap:Ethernet  HWaddr 04:D4:C4:50:81:C0 
          inet6 addr: fe80::6d4:c4ff:fe50:81c0/64 Scope:Link
          UP BROADCAST RUNNING ALLMULTI MULTICAST  MTU:1500  Metric:1
          RX packets:254486 errors:0 dropped:76 overruns:0 frame:0
          TX packets:987873 errors:0 dropped:486 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:39542557 (37.7 MiB)  TX bytes:1258379803 (1.1 GiB)

eth3      Link encap:Ethernet  HWaddr 04:D4:C4:50:81:C0 
          inet6 addr: fe80::6d4:c4ff:fe50:81c0/64 Scope:Link
          UP BROADCAST RUNNING ALLMULTI SLAVE MULTICAST  MTU:1500  Metric:1
          RX packets:10205479 errors:0 dropped:10 overruns:0 frame:0
          TX packets:6149742 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:13371735392 (12.4 GiB)  TX bytes:1178122058 (1.0 GiB)

eth4      Link encap:Ethernet  HWaddr 04:D4:C4:50:81:C0 
          inet6 addr: fe80::6d4:c4ff:fe50:81c0/64 Scope:Link
          UP BROADCAST RUNNING ALLMULTI SLAVE MULTICAST  MTU:1500  Metric:1
          RX packets:5686897 errors:0 dropped:8 overruns:0 frame:0
          TX packets:5348 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:6846718765 (6.3 GiB)  TX bytes:1459902 (1.3 MiB)

eth5      Link encap:Ethernet  HWaddr 04:D4:C4:50:81:C0 
          inet6 addr: fe80::6d4:c4ff:fe50:81c0/64 Scope:Link
          UP BROADCAST RUNNING ALLMULTI MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:106588 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:0 (0.0 B)  TX bytes:19157395 (18.2 MiB)

eth5.85   Link encap:Ethernet  HWaddr 04:D4:C4:50:81:C0 
          inet6 addr: fe80::6d4:c4ff:fe50:81c0/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:57 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:0 (0.0 B)  TX bytes:7782 (7.5 KiB)

eth6      Link encap:Ethernet  HWaddr 04:D4:C4:50:81:C0 
          inet6 addr: fe80::6d4:c4ff:fe50:81c0/64 Scope:Link
          UP BROADCAST RUNNING ALLMULTI MULTICAST  MTU:1500  Metric:1
          RX packets:68549 errors:0 dropped:18 overruns:0 frame:0
          TX packets:79714 errors:0 dropped:96219 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:20255421 (19.3 MiB)  TX bytes:51913261 (49.5 MiB)

eth7      Link encap:Ethernet  HWaddr 04:D4:C4:50:81:C4 
          inet6 addr: fe80::6d4:c4ff:fe50:81c4/64 Scope:Link
          UP BROADCAST RUNNING ALLMULTI MULTICAST  MTU:1500  Metric:1
          RX packets:1779977 errors:0 dropped:17 overruns:0 frame:0
          TX packets:3838524 errors:0 dropped:7776 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:142196343 (135.6 MiB)  TX bytes:5345933123 (4.9 GiB)

lo        Link encap:Local Loopback 
          inet addr:127.0.0.1  Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING MULTICAST  MTU:65536  Metric:1
          RX packets:564595 errors:0 dropped:0 overruns:0 frame:0
          TX packets:564595 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:107471184 (102.4 MiB)  TX bytes:107471184 (102.4 MiB)

lo:0      Link encap:Local Loopback 
          inet addr:127.0.1.1  Mask:255.0.0.0
          UP LOOPBACK RUNNING MULTICAST  MTU:65536  Metric:1

ppp0      Link encap:Point-to-Point Protocol 
          inet addr:58.32.19.140  P-t-P:58.32.16.1  Mask:255.255.255.255
          inet6 addr: fe80::7df6:e7d5:60ad:5761/10 Scope:Link
          UP POINTOPOINT RUNNING MULTICAST  MTU:1442  Metric:1
          RX packets:10359968 errors:0 dropped:0 overruns:0 frame:0
          TX packets:16540947 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:3
          RX bytes:7146556580 (6.6 GiB)  TX bytes:19628987463 (18.2 GiB)

spu_ds_dummy Link encap:UNSPEC  HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00 
          inet6 addr: fe80::200:ff:fe00:0/64 Scope:Link
          UP RUNNING NOARP  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:100
          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

spu_us_dummy Link encap:UNSPEC  HWaddr 00-00-00-00-00-00-30-30-00-00-00-00-00-00-00-00 
          inet6 addr: fe80::200:ff:fe00:0/64 Scope:Link
          UP RUNNING NOARP  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:100
          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

vlan85    Link encap:Ethernet  HWaddr 04:D4:C4:50:81:C0 
          inet addr:192.168.98.1  Bcast:192.168.98.255  Mask:255.255.255.0
          inet6 addr: fe80::6d4:c4ff:fe50:81c0/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:6 errors:0 dropped:0 overruns:0 frame:0
          TX packets:53 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:252 (252.0 B)  TX bytes:7482 (7.3 KiB)

wl0.2     Link encap:Ethernet  HWaddr 04:D4:C4:50:81:C2 
          inet6 addr: fe80::6d4:c4ff:fe50:81c2/64 Scope:Link
          UP BROADCAST RUNNING ALLMULTI MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:534 errors:0 dropped:32403 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:0 (0.0 B)  TX bytes:67950 (66.3 KiB)

wl1.2     Link encap:Ethernet  HWaddr 04:D4:C4:50:81:C6 
          inet6 addr: fe80::6d4:c4ff:fe50:81c6/64 Scope:Link
          UP BROADCAST RUNNING ALLMULTI MULTICAST  MTU:1500  Metric:1
          RX packets:7668 errors:0 dropped:0 overruns:0 frame:0
          TX packets:39931 errors:0 dropped:247 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:921641 (900.0 KiB)  TX bytes:8711345 (8.3 MiB)
 
Gar said:
But...a router reboot wiped it all out again until I forced another unbound restart.
Click to expand...
My suggestion would be to uninstall unbound and reinstall it. I don't think it is a b5 problem but that should set the scripts right.
 
clvk07 said:
Flashed beta 5 on AX86U can't access via SSH anymore

:\Users\claud>ssh admin@192.168.1.1
ssh: connect to host 192.168.1.1 port 22: Connection timed out

C:\Users\claud>telnet 192.168.1.1 22
Connecting To 192.168.1.1...Could not open connection to the host, on port 22: Connect failed
Click to expand...

Check your system log, it will tell you if/why dropbear isn't running.
Max33Verstappen said:
Here it is:
Click to expand...

Ok, could be related to having multiple interfaces. Can you post the output from the following commands?

Code: 
killall wsdd2
wsdd2 -WWWWW -w -i br0 -b sku:RT-AX88U,serial:0123456789

Wait for about 5 seconds, then press Ctrl-C to stop it, and send me the resulting output.
 
RMerlin said:
Known issues:

  • RT-AX88U syslog spam when using Guest Network 1 (issue that will have to be resolved by Asus, only workaround is to switch to Guest Network 2)
  • I need further testing of the Speedtest on the RT-AX56U and RT-AX58U, results don't seem right. (Seems fine so far)
  • Downgrading the RT-AC68U to a previous version will require a factory default reset (Not a bug, just the same side effect as previous models when they switched to encrypted password storage)
  • High CPU temperature on the RT-AC86U (fixed in beta 5)
  • RT-AX88U performance issues for some users, also cannot flash other firmware images on top of beta 4 (Beta 4 pulled for this model, fixed in beta 5)
Click to expand...

Thanks for the hard work you put into the merlin firmware. I flashed the beta 4 on my ax88u before you pulled it. What can i do to upgrade to beta 5?
 
rx2 said:
No that is not what I mean. Daylight Savings appears to be broken in 386.x.

I reported it in the following thread - https://www.snbforums.com/threads/d...in-386-1-beta-4-asus-3-0-0-4-386-41535.69526/
Click to expand...
This may be related to the issue I reported backed on the 2nd of Jan that the Wifi Region setting in the GUI didn't seem to be setting the actual region country in use by the router and the US wifi bands and power levels are always used unless you SSH into the router and manually change the country. Haven't seen any word on when this would be fixed. Not sure if it is an ASUS GPL issue or one Merlin can fix.
www.snbforums.com

Beta - Asuswrt-Merlin 386.1 Beta is now available

I've been running beta 3 since we resolved the MCU being blanked problem when installing over asus stock. Everything has been going well with my AC88U, running non-mesh, with about 30 clients with two exceptions: 1. I lost the 5g band once. I turned off 160, and that problem has not...
www.snbforums.com www.snbforums.com
 
Gar said:
Unbound no longer displays charts, just the small box with printed stats. Did not use earlier betas though, so may not be a new change.
Click to expand...

it works for me. But I do have other @Jack Yaz extensions installed so maybe that is why the graphs work. Do you have other things installed?

edit: saw your later post. So that isn’t it. On first boot the stats may be generated when all values are zero and produce empty graphs. Wait an hour and it should populate. The speed of response graphs and the retuned codes graph are both from unbound internal stats and reset on restart or reboot.
 
Last edited:
  • Like
Reactions: Gar
juched said:
it works for me. But I do have other @Jack Yaz extensions installed so maybe that is why the graphs work. Do you have other things installed?
Click to expand...
Just Skynet. It displays unbound data/graphs fine until a reboot or power cycle. That small section with the basic stats always works though.

EDIT: Continuing this issue under the Unbound thread.
 
Last edited:
Status
Not open for further replies.

Similar threads

RMerlin
  • Locked
Beta Asuswrt-Merlin 3004.388.6 Beta is now available
12 13 14
Replies
279
Views
35K
RMerlin
RMerlin
RMerlin
Current plans regarding separate version branches
3 4 5
Replies
87
Views
10K
zay2u
Z
RMerlin
  • Locked
Beta Asuswrt-Merlin 3004.388.4 beta is now available
28 29 30
Replies
598
Views
73K
RMerlin
RMerlin
RMerlin
  • Locked
Beta Asuswrt-Merlin 386.13 beta is now available for AC models
2
Replies
32
Views
4K
RMerlin
RMerlin
RMerlin
  • Locked
Beta Asuswrt-Merlin 3004.388.5-beta is now available
2 3
Replies
58
Views
9K
RMerlin
RMerlin
Similar threads
Thread starter Title Forum Replies Date
RMerlin Release Asuswrt-Merlin 386.13 / 386.13_2 is now available for AC models Asuswrt-Merlin 39
RMerlin Beta Asuswrt-Merlin 386.13 beta is now available for AC models Asuswrt-Merlin 32
RMerlin Release Asuswrt-Merlin 386.12_6 is now available for AC models Asuswrt-Merlin 168
B is AsusWRT-MERLIN 388.2_2 (dd 7 May 2023) affected by the security issues fixed in 3.0.0.4.386.51665 (dd 18 May 2023)? - RT-AX56U Asuswrt-Merlin 23
RMerlin Release Asuswrt-Merlin 386.12 is now available for AC models Asuswrt-Merlin 582
RMerlin Beta Asuswrt-Merlin 386.12 Beta is now available for AC models Asuswrt-Merlin 21
H How to upgrade asuswrt merlin 386.2_6 on rt-ax88u Asuswrt-Merlin 3
RMerlin Release Asuswrt-Merlin 386.11 is now available for AC models Asuswrt-Merlin 148
RMerlin Release Asuswrt-Merlin 3004.388.7 is now available Asuswrt-Merlin 24
RMerlin Beta Asuswrt-Merlin 3004.388.7 beta is now available Asuswrt-Merlin 123

Similar threads

Latest threads

Sign Up For SNBForums Daily Digest

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

Members online

Total: 834 (members: 12, guests: 822)
Top