Release Asuswrt-Merlin 386.1 is now available

  • ATTENTION! As of November 1, 2020, you are not able to reply to threads 6 months after the thread is opened if there are more than 500 posts in the thread.
    Threads will not be locked, so posts may still be edited by their authors.
    Just start a new thread on the topic to post if you get an error message when trying to reply to a thread.
Status
Not open for further replies.

skeal

Part of the Furniture
Hey @RMerlin why would my LAN MAC address be all zeros, as reported by network map page and, the new AIMesh page. They both show my AX88U with no mac address just zeros. Could this be affecting my ability to connect to my AC68U through the AIMesh search for node feature? My AC68U access point has a lan mac address, and is visible in the above mentioned places, also with 386.1. How would one fix this issue? I have reset to defaults and setup again from screen shots three times now. Doesn't seem to make a difference to this issue. As far as AIMesh goes I never got connected no matter what I tried.
 
Last edited:

IcerJo

New Around Here
Yup, but diff from the changelog the Ui/ssh never came back after two days in the new build
Yikes! any luck after a hard reboot?
 

telUK

Regular Contributor
I did a clean install. With WPS reset and jffs reset too. Idk why , but my 2.4ghz keeps being flaky all the times... After a few hours. My IoT devices on guest network 2 (i don't use guest 1 since it's a known issue) is dropping in and out and the link rate is all ??/?? . The normal main network seems fine until you tried to use it. You can't connect to 2.4ghz and the connected clients can't even go to 192.168.1.1 ... Tho after 10 mins or so when it goes normal . Everything went fine again. And it'll happen again for sometimes later. Tried wps reset it again. And same deal. So I just reinstalled 384.19 now and Im trying to check if it happens here too. Since this didn't happen before 386.1 . If it doesn't do that on 384.19, then there's something wrong with the 386.1 atleast in AC86U ...

Is it easy to downgrade, is the process exactly the same as installing new firmware?

I need 2.4ghz to be stable for some of my devices so if I get same issue I will need to downgrade.
 

Andorul

Occasional Visitor
Anyone experience problems in VPN if I have 2 ou more OpenVPNClients ON all traffic goes to SAME vpn server!
ISP: Fiber 500Mbps
AX88U: Wireless router - 386.1 : Diversion + skynet behind ISP router - Local IP
Subscribed Vpn: Surf Shark (suport varius vpnserver to same client)

OPENVPNCLIENT1->TV
OPENVPNCLIENT2-> Smartphone
Force Internet traffic through tunnel Policy Rules (Strict)
Block routed clients if tunnel goes down YES

OpenVPNClient1 - Public IP 91.205.230.141 Local IP 10.8.8.6
OpenVPNClient2 - Public IP 66.115.166.148 Local IP 10.8.8.3

My solution:
changing the server protocol of VPNClient2 has it changed de port of server! it works
OpenVPNClient1 UDP port 11xx
OpenVPNClient1 TCP port 14xx

SpeedTest
RJ45
TV + VPN1 .PT - 70Mbps
Notebook i7 2gen NOVPN - 474Mbps

Wifi 5Ghz - far from router
Galaxy S5 + VPN2 .US - 9Mbps
Galaxy A70 NOVPN - 120Mbps

Not Bad 2 VPN Clients 4 devices testing at sometime, what do you think?

1 QUESTION HOW COME SOME USER HAVE MORE THAN 2?
change server port or port forward to another port i think
 
Last edited:

JIPG

Regular Contributor
I have upgraded from my old RT AC87U to a new RT AX88U and the first thing I have done is installing FW 386.1 (to be honest I waited to have it released before buying the router ;) ).

It is working without a glitch, so I would like to thank RMerlin (do not forget themiron with the last security patches in dsnmasq) for the great effort.
 

Matthew Patrick

Senior Member
Is it easy to downgrade, is the process exactly the same as installing new firmware?

I need 2.4ghz to be stable for some of my devices so if I get same issue I will need to downgrade.
Yeah it's just like when you do a clean install. Just install the 384.19, after it rebooted. Make sure it is now 384.19 if it is. I recommend to just go straight to wps reset. Since it apparently wipes the jffs too ... I do not reset since i already have a working 384.19 backup before going to 386 . So I just went to 384.19 and then restored both jffs and the backed up configuration..

The only thing I hate about 384.19 atleast in my AC86U is that it seems like there's a memory leak. Seems like it's from trend micro stuff but idk. I can see it go up in ram usage per hour and yeah I can see it pushing to swap usage after a day or two. And I don't use much addons. It's fixed on 386 though since I've run it for 2 days and the ram usage is consistent there. But yeah let me know if you experienced 2.4ghz problems as well. So far 4 and a half hour on 384.19 and 2.4ghz is still going strong. Will check it regularly to see if it happens here or not. I'd assume not
 

L&LD

Part of the Furniture
@Matthew Patrick, your 'ram usage issue' may be you. :)

If you flashed from 384.19_0 to 386.1_0 and then back to 384.19 and (without fully resetting the router) you restore your backup config file and backup JFFS file too, your router is far from a clean slate.

And that is assuming that the back config and JFFS files you're restoring are made from a fully reset 384.19_0 firmware base and the router was minimally and manually configured.

FYI. :)
 

RMerlin

Asuswrt-Merlin dev
It looks like the /rom/etc/init.d/ssl.sh file is missing there (for longer period of time), in /rom/etc/rc3.d/ there is the linked file S50ssl which points to it. Nothing terrible, only to know to clean it up.
Neither of these are used by the firmware. They are just leftovers from the Broadcom SDK that Asuswrt doesn't use.
 

RMerlin

Asuswrt-Merlin dev
Hi Eric, wouldn't it be appropriate to add also the other known and reported here bugs of this release (even if being more of a GPL thing and also existing in the official firmwares) ?

- Regression : Spikes in traffic monitor stats
- Phantom devices in network map
- Unstable 2.4Ghz band on RT-AX88U when channel bandwidth is set to 40Mhz

My rational is that having those at least mentioned in the 'known bugs' section would allow many users not to spend time with those issues, and for the rest save time in repeating that those are already known.
No, because some of these are old long-standing minor issues, and others look to me like end-user environment issues (40 MHz on the 2.4 GHz will always be unstable due to the large amount of interference in that band, this has nothing to do with the firmware). I only list things that are new, critical, and which I can actually reproduce.
 

RMerlin

Asuswrt-Merlin dev
I saw the change log for alpha 386.2 and realized I can stop waiting. There will NEVER be Instant Guard for the RT-AC68U will there? Unless Asus decided to release it, right?
It's a kernel issue, IPSEC modules don't work properly on that model's patched kernel.
 

RMerlin

Asuswrt-Merlin dev
Hey @RMerlin why would my LAN MAC address be all zeros, as reported by network map page and, the new AIMesh page. They both show my AX88U with no mac address just zeros. Could this be affecting my ability to connect to my AC68U through the AIMesh search for node feature? My AC68U access point has a lan mac address, and is visible in the above mentioned places, also with 386.1. How would one fix this issue? I have reset to defaults and setup again from screen shots three times now. Doesn't seem to make a difference to this issue. As far as AIMesh goes I never got connected no matter what I tried.
Release after release, your router always seem to constantly get weird issues that no one else has. I have to wonder what you are running or configuring on your router to get all of these weird issues, assuming it's not a defective router...
 

bluzfanmr1

Senior Member
I decided to do a factory reset of my RT-AC88U to see if that helps with the lock ups. After setting my router back up though and putting them back on my usual manual 5 GHz channel (44), I found that my iPad and iPhone were dropping a ton of packets. The connection was horrible.

I checked the Wifi professional page and saw that Enable IGMP Snooping and Multi-User MIMO now default to being enabled, when I previously had them disabled, so I changed them, but that made no difference. Airtime Fairness was already disabled (the new default?).

The only thing that worked was to switch my Wifi channel to auto which picked 153 at first and then later 157. That stopped the dropped pings on my iPad. My iPhone still has dropped ping for about 30 seconds and then seems to stabilize.

i checked the site survey and there is a nearby Wifi network on channel 44, but the strength is 10% so it shouldn’t interfere.

Any idea why channel 44 simply wasn’t working after a factory reset when it’s worked fine for years?


On a side note, on the site survey screen do the number of rings on the Wifi signal mean anything at all? Some of the ones with full rings have 5% signal. These are “open system“ networks, but that seems wrong.

I would leave Enable IGMP Snooping enabled as it optimizes wireless multicast traffic. I would also try forgetting the network connection on each Apple device and recreate a new one since the router was reset.

Have you tried using a wireless survey program to see what channels are being used around you and so you can pick the least congested or the one that gives you the best experience on the network? WiFi Explorer Lite is a good one to use on Apple devices.
 

Matthew Patrick

Senior Member
@Matthew Patrick, your 'ram usage issue' may be you. :)

If you flashed from 384.19_0 to 386.1_0 and then back to 384.19 and (without fully resetting the router) you restore your backup config file and backup JFFS file too, your router is far from a clean slate.

And that is assuming that the back config and JFFS files you're restoring are made from a fully reset 384.19_0 firmware base and the router was minimally and manually configured.

FYI. :)
Nonono. It's been like that before the going back to 384.19. And on 384.19 I've WPS reset + normal reset and jffs reset more than twice. And the end results were the same. It's a real thing. I didn't really look into it since it seems to climb slowly enough that it's not really a problem I guess. But yeah. 386 has fixed it for me. Atleast for that minor problem :)
 

GHog

Occasional Visitor
So here is my feedback,

2 routers setup in mesh mode. Using wireless for node connection not wired backhaul mode. Master is a RT-AX88U and node is an V1 RT-AC68U router. Both were running the 384.19 merlin firmware prior to update. No issues other than ASUS not passing live device access time back to master router. Have brought that to ASUS attention since it does not look like it has anything to do with RMerlin firmware.

Updated both routers Saturday evening when traffic in house stopped for the evening. Update master first and then node. Updated went without a hitch. Looked good. Next day did a full power cycle on both. First powered down master and the node. Let sit for 10 minutes and then powered up master first, waited for all led to come on and then the node.

Been running for a week without issues. My DSL is a 40d/5u subscription. No bonded line. My speed test came out same as before, 40/5. Did noticed QOS was on by default. Turned off and did test again. No difference. I also use AiProtection and that being on did not slow things down.

All in all mesh network working great. Let QOS stay in auto and that was the only thing I changed. I do not use smart connect and always select control channels based on traffic in area.

The only mesh issue again seems to be an ASUS bug. This time when I log into master and look at connected devices, the only live data is from master. Nothing from node. No Rx/Tx data or access time. Also when using the phone app, prior AiMesh 1.0 would only show what was currently connected and talking to router. Now app show everything that has connect to router whether it is currently connected or not. Connected devices do show current data rates up and down.
 

sentinelvdx

Very Senior Member
My LAN/WAN went down again today on my RT-AC88U. That’s less than 2 days after it went down last time and that was less than 2 days after I upgraded to 386.1.

Wifi didn’t go “down” per say, but if I disconnected from WiFi I couldn’t get back on.

Having this happen twice in 2 days is more or less unheard of. Something seems off with this update.
Do a hard reset and configure it all over again. I've been running 386.1 on my AC88U and didn't face any issue like that since this build has been released.
Also check the syslog if after hard reset issue continues to find what could be causing it.
 

Crazy

Regular Contributor
Did a dirty update from 384.19 to 386.1 on my RT-AC5300. Everything seems to be fine, cpu temp went down by 2 degree C, it is sitting at 68C now. But did noticed my traffic log not working correctly. I’ve have cleared the database and will see if that fix the problem.
 
Last edited:

Rob Q

Regular Contributor
I don't know if it's the firmware or even a setting or maybe even it could be that I did a full factory reset with the router but I find that Netflix and my other video streaming services are loading up more quickly, also 4K HDR playback is instant now. Before it would take a few seconds to load. As for streaming 2160p content on YouTube, that has constant buffering issues. Not sure if it's something on there end?
For video playback I am using my Roku TV on the 5 GHz network, no neighbouring networks are on this control channel or even near it and I've got it maxed out to 80 MHz wide. The distance from the router is about 10 feet and nothing is between them.
As for streaming on the 2.4 GHz, that player is only limited to HD content (Older Roku streaming stick). I never seen Netflix load a movie so fast before and that is on the other side of the house and has a brick wall in between.

Preamble Type: Short (2.4GHz)
Universal Beamforming: Disable (2.4/5GHz)

Regardless, I am very happy with this update! :)
 

scottegos2

Occasional Visitor
My RT-AC5300 crashes continually with 386.1. I don't think it's lasted longer than 12 hours. This is even after doing the factory reset and fresh install, then entering my config in manually (to rule out bad backups). Not seeing anything noteworthy in the syslog. No problems at all with 384.19. Pretty vanilla setup (Qos off, no VPN, no scripts, smartconnect on).
 
Status
Not open for further replies.

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