What's new

Beta Asuswrt-Merlin 386.5 Beta 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.
I ran into some bad NAND blocks a release or two back on a AC86U. I never found any formatting around them and I believe they were the root of several of my issues. That's when I stopped using /JFFS as for AMTM temp areas. I cannot remember if that was the AC86U which eventually "fried" itself. :(

Release - Asuswrt-Merlin 384.19 is now available | Page 24 | SmallNetBuilder Forums (snbforums.com)
According to Merlins response on the next page, that is unlikely: http://www.snbforums.com/threads/asuswrt-merlin-384-19-is-now-available.65801/post-615575
 
Last edited:
I did dirty upgrades to my Asus RT-AC68U from AsusWRT-Merlin 386.4_0 to the two alphas and now to AsusWRT_Merlin 368.5_beta1. All appears to be working well, I didn't encounter any problem.
The Disable 11b option on the 2.4 GHz WiFi when Wireless Mode is set to Auto still makes the clients disconnect a few seconds after connecting, but, unlike 386.4_0, the option can be disabled by the WebUI, no need to use the terminal.
Thank you RMerlin!


I think that this line, Feb 22 08:32:35 acsd: eth6: COEX: downgraded chanspec 0x1909 to 0x100b: channel 6 used by exiting BSSs, refers to the fact that your 2.4 GHz Channel bandwidth is not set to 20 MHz and when the router detects another wireless network using a channel overlapping with its own, it correctly falls back the bandwidth to 20 MHz and informs you by that line. Check this soon to be 10 years old article from this very website for more information.
You should manually set the Channel bandwidth to 20 MHz, also set the Control channel to 1, 6 or 11, depending on which is the most unused.

For the other lines, searching for 88:d0:39 OUI reveals the owner to be Tonly Technology Co. Ltd, formerly TCL Technoly Electronics(Huizhou).,Ltd, which unfortunatelly means nothing to me.

Thx for the reply, after checking it looks like my settings actually had 20/40mhz channels selected, cant remember i changed that to those settings from the 20mhz only.
Changed it back and will keep a eye out.

As for the TCL, i know that company as a phone/TV maker, but i dont have those in my house.
Guess i have a further search as to what it might be and causing my log to be cluttered with those messages.

Edit: after some more searching i found the device.
Its my JBL Soundbar thats having problems with the WiFi
 
Last edited:
Another thing is that I get the impression that the NAT passthrough does not function properly.

Hi Sheikh, what problems are you seeing with NAT passthrough? I'm interested as I use it and I haven't updated yet and I can't try as due to a situation at home I need a 100% stable network for the time being.
 
Dirty upgrade from alpha 2 to beta 1 with USB plugged in, no issues so far.
 
Saw something pop up on GitHub a day or 3 ago, so I've been expecting this.

Did you have to clone the modem's MAC to your router?

Couldn't figure out how to get the AT&T part of the
 
This version works great, and from what I can say so far, is that I don’t have those ridiculous amount of queries running of to Microsoft checking an internet connection. Other than that, at all is stable and looking good.
 
All my AX58U's and AC68U's are working good.
 
ax88 up to b1, no issues to report
 
Hi Sheikh, what problems are you seeing with NAT passthrough? I'm interested as I use it and I haven't updated yet and I can't try as due to a situation at home I need a 100% stable network for the time being.
the moment device use their own vpn client
 
Installed 386.5_beta1 over 386.3_2 and notice one odd behavior of the QOS tab in the logging.
I have not configured or enabled anything in the "Adaptive QOS" tab, it is at its default's "off" settings.

QOS_tab.JPG
Just going to the "Adaptive QOS" tab and then back to the "System log" tab will show the following:​
Code:
Feb 23 16:06:57 kernel: Init chrdev /dev/idp with major 190
Feb 23 16:06:57 kernel: tdts: tcp_conn_max = 8000
Feb 23 16:06:57 kernel: tdts: tcp_conn_timeout = 300 sec
Feb 23 16:06:59 kernel: SHN Release Version: 2.0.2 36f59aa
Feb 23 16:06:59 kernel: UDB Core Version: 0.2.20
Feb 23 16:06:59 kernel: Init chrdev /dev/idpfw with major 191
Feb 23 16:06:59 kernel: IDPfw: flush fc
Feb 23 16:06:59 kernel: IDPfw: IDPfw is ready
Feb 23 16:06:59 kernel: sizeof forward pkt param = 280
Feb 23 16:06:59 BWDPI: fun bitmap = 3
Feb 23 16:07:25 BWDPI: force to flush flowcache entries
Feb 23 16:07:25 kernel: IDPfw: Exit IDPfw
Feb 23 16:07:25 kernel: mod epilog takes 0 jiffies
Feb 23 16:07:25 kernel: IDPfw: Exit IDPfw
Feb 23 16:07:25 kernel: Exit chrdev /dev/idpfw with major 191
Feb 23 16:07:25 kernel: Exit chrdev /dev/idp with major 190
Feb 23 16:07:25 BWDPI: rollback fc
Feb 23 16:07:25 custom_script: Running /jffs/scripts/nat-start
Feb 23 16:07:25 custom_script: Running /jffs/scripts/firewall-start (args: eth0)

So at the end the scripts will be executed , just by having entered and leaving the QOS page where nothing is changed or configured.
@RMerlin Is the (re)-start of the scripts as intended or a bug?
 
Installed 386.5_beta1 over 386.3_2 and notice one odd behavior of the QOS tab in the logging.
I have not configured or enabled anything in the "Adaptive QOS" tab, it is at its default's "off" settings.

Just going to the "Adaptive QOS" tab and then back to the "System log" tab will show the following:​
Code:
Feb 23 16:06:57 kernel: Init chrdev /dev/idp with major 190
Feb 23 16:06:57 kernel: tdts: tcp_conn_max = 8000
Feb 23 16:06:57 kernel: tdts: tcp_conn_timeout = 300 sec
Feb 23 16:06:59 kernel: SHN Release Version: 2.0.2 36f59aa
Feb 23 16:06:59 kernel: UDB Core Version: 0.2.20
Feb 23 16:06:59 kernel: Init chrdev /dev/idpfw with major 191
Feb 23 16:06:59 kernel: IDPfw: flush fc
Feb 23 16:06:59 kernel: IDPfw: IDPfw is ready
Feb 23 16:06:59 kernel: sizeof forward pkt param = 280
Feb 23 16:06:59 BWDPI: fun bitmap = 3
Feb 23 16:07:25 BWDPI: force to flush flowcache entries
Feb 23 16:07:25 kernel: IDPfw: Exit IDPfw
Feb 23 16:07:25 kernel: mod epilog takes 0 jiffies
Feb 23 16:07:25 kernel: IDPfw: Exit IDPfw
Feb 23 16:07:25 kernel: Exit chrdev /dev/idpfw with major 191
Feb 23 16:07:25 kernel: Exit chrdev /dev/idp with major 190
Feb 23 16:07:25 BWDPI: rollback fc
Feb 23 16:07:25 custom_script: Running /jffs/scripts/nat-start
Feb 23 16:07:25 custom_script: Running /jffs/scripts/firewall-start (args: eth0)

So at the end the scripts will be executed , just by having entered and leaving the QOS page where nothing is changed or configured.
@RMerlin Is the (re)-start of the scripts as intended or a bug?
I think your question might be addressed here.
 
Last edited:
Dirty upgrade from alpha 2 to beta 1 with USB plugged in, no issues so far.
I keep forgetting to "Safely Remove disk:", yet everything is still running smooth.

Full Factory Reset (manually setup router settings No Back Ups) at each FW release, to start Fresh & New.
Installed with dirty upgrade from alphas to beta (since release) with zero network issues.
 
Last edited:
I have AT&T Fiber modem in front of my Router and put the AT&T modem/router into passthrough mode and now get the external IP address on my Asus. You might check if you have similar option.
I have the same setup with Nokia 505 AT&T Fiber modem on a AC68 with 384.4 and get my external address on my AC68 in pass-through.
 
Last edited:
Status
Not open for further replies.

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