What's new

[Fork] Asuswrt-Merlin 374.43 LTS releases (Archive)

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

Am I the only one with WiFi issues on 2.4 and 5 ghz with the latest release on a RT-AC66U (no B1)? If i check my ISP speed with ookla connected to the router with your latest LTS version I only get about 2.5 MB/s and with an older WDR4300 (N750) with DDWRT I get about 5.8 MB/s. Didn't yet tested any other of your releases since I switched back to the latest Merlin release 380.70 which is currently more or less stable for me. With Merlin I reach at least the same speed as I can get with the older WDR4300. Same Spots for testing, repeated it several times with only 1 active device in the network o_O
 
Am I the only one with WiFi issues on 2.4 and 5 ghz with the latest release on a RT-AC66U (no B1)? If i check my ISP speed with ookla connected to the router with your latest LTS version I only get about 2.5 MB/s and with an older WDR4300 (N750) with DDWRT I get about 5.8 MB/s. Didn't yet tested any other of your releases since I switched back to the latest Merlin release 380.70 which is currently more or less stable for me. With Merlin I reach at least the same speed as I can get with the older WDR4300. Same Spots for testing, repeated it several times with only 1 active device in the network o_O
Merlin and John have no control over WiFi drivers, they just use pre-compiled binaries from Asus. DD-WRT has a deal with Broadcom, so they get newest drivers.
 
Thanks that makes sense... but as I said it works fine with the Merlin release too. Something is killing the speed on the LTS release for me :/

ISP provides me with 50 Mbit. Channel bandwith is 20/40 and i forgot to mention i was using the same channel at my tests (11) as it‘s the cleanest in my neighbourhood.
 
Am I the only one with WiFi issues on 2.4 and 5 ghz with the latest release on a RT-AC66U (no B1)?
I don't chase the 'latest' wireless drivers for the fork. Haven't touched the wireless in almost a year since the KRACK fix integration.
 
I had a problem with the Oneplus 6 WIFI causes my RT66U router to reboot.
On Reddit i found a solution to turn off HW acceleration.
https://www.reddit.com/r/OnePlus6/comments/8suqm8/oneplus_6_wifi_reboots_asus_rtn66u_router/

After that i didn't had any reboots issues.

I had the same issue with my OP6. Disabling NAT acceleration solves the issue, but you get a significantly slower router with that solution. I found that you don't have to disable NAT acceleration, just change regulation mode from 802.11d+h to 802.11h on the 5ghz network.
 
I had the same issue with my OP6. Disabling NAT acceleration solves the issue, but you get a significantly slower router with that solution. I found that you don't have to disable NAT acceleration, just change regulation mode from 802.11d+h to 802.11h on the 5ghz network.
That's interesting.....802.11d (handles power level negotiation) has been deprecated. So, newer devices may get upset, although they should probably just ignore it. Older devices may require it. I have a Linksys WUMC710 Media Bridge which refuses to connect if it's not set.
 
My guess is that this is something specific to oxygen os and OP6, I didn't have this issue before the pie update. But yeah weird. Haven't had any issues with other devices since i disabled 802.11d, then again my older devices are already connected to 2.4Ghz where it's enabled.
 
That's interesting.....802.11d (handles power level negotiation) has been deprecated. So, newer devices may get upset, although they should probably just ignore it. Older devices may require it. I have a Linksys WUMC710 Media Bridge which refuses to connect if it's not set.

Nevermind, just tried connecting my wifes old S5 to the 5ghz wlan, crashed the router just like the OP6 used to do. But i can live with her having to use 2.4ghz, better than disabling NAT acceleration ;)
 
Hello John, I'm running 36EA on my AC68R. I'm having a wierd problem with (2) 2.4 ghz devices - a Samsung Gear S3 Frontier and Under Armour scale made by HTC. Both devices refuse to auto-reconnect to the network. The scale worked previous versions of your firmware, this problem may have cropped up with your April release. The watch was connected to wifi but I didn't pay attention if it ever auto reconnected previously. If I go into settings and forget the network on each device, then choose my 2.4 network and re-enter the password, both devices connect. The scale is battery operated, after it goes to sleep it won't reconnect. The watch stays connected till I leave the house. When I return, it won't reconnect. When I go into wifi settings, it shows the proper network and is stuck at "connecting..." So far I've tried changing Wireless Mode from "Auto" to "N Only" Same results. My Pixel 2 will auto connect fine on 2.4, other devices are either 5ghz or seem unaffected. Any thoughts?
 
Last edited:
You reported a similar problem earlier in the year with PS3's.

If you have Universal Beamforming turned on you should disable it.

I turned off Universal Beamforming and it didn't appear to make any difference. However I think that turning on my Hisense smart TV might have been the thing that was killing the PS4 connections. I have no idea how. I switched my TV to use the 5G wireless network and I haven't had the issue since so it was either that or some other random variable that I didn't account for.
 
However I think that turning on my Hisense smart TV might have been the thing that was killing the PS4 connections.
Interesting. Quite plausible IMHO because, 1) smart TV's have an annoying tendency nowadays to have WiFi-Direct enabled effectively turning them into access points (on the same channel), and b) TV's tend to be placed right next to your games console - ideal for interference.
 
Is there anything suspicious in the system log?

Just before it shows up in the log, the Gear S3 was stuck at "connecting...", I rebooted it, then forgot the network and signed in. I don't see anything before it joined then. On an unrelated note, the device @ .103 is my Obi 202 voip adapter, it seems very busy. The phone is sitting idle, is that normal activity?
 

Attachments

  • Screenshot (24).png
    Screenshot (24).png
    289.5 KB · Views: 393
Just before it shows up in the log, the Gear S3 was stuck at "connecting...", I rebooted it, then forgot the network and signed in. I don't see anything before it joined then. On an unrelated note, the device @ .103 is my Obi 202 voip adapter, it seems very busy. The phone is sitting idle, is that normal activity?
Your screenshot is too small to read.
 
Just before it shows up in the log, the Gear S3 was stuck at "connecting...", I rebooted it, then forgot the network and signed in. I don't see anything before it joined then. On an unrelated note, the device @ .103 is my Obi 202 voip adapter, it seems very busy. The phone is sitting idle, is that normal activity?
Use the snipping tool in windows 10...just search for snipping. Your image text is too small
 
The next release has been posted, 37E4

LATEST RELEASE: Update-37E4/36L4
25-November-2018
Merlin fork 374.43_37E4j9527
Download http://bit.ly/1YdgUcP
============================

Changes:
  • Add DDNS ez-ipupdate support for external ip (double NAT)
  • Update OpenSSL to version 1.0.2q
  • Update Dnsmasq to version 2.80-122392e snapshot
  • Update GetDNS (used in DoT) with latest upstream fixes
  • Update udpxy to build 23
  • Increase allowable key/cert size to 4999 bytes for OpenVPN client/server
    As a reminder, NVRAM is the default location for saving OpenVPN keys/certs. To free NVRAM space, the 'ovpn2jffs' utility may be used as documented in Merlin_Fork_Options.txt
  • Add ability to select DNSSEC validation method for DoT
  • Misc WebUI formatting/content fixes

SHA256
Code:
(Default Build - All supported routers)
609b98530bcd7eee66801de92371c5dccec20016abb01b36aac1ff98c2fa2140  RT-N16_374.43_37E4j9527.trx
5fbd3ba7d27883be30c46ae57f4bb7131eab8665c225eb91f73b269b5a2d51a0  RT-AC66U_374.43_37E4j9527.trx
3a34ea8385b9a4fb34acae73b8994a0ec27c11221103c02f7d430fbd4b1c40db  RT-N66U_374.43_37E4j9527.trx
396df043cf7ff99af2a164e431377038281b6fd1c4d749761bc4a3d340912bd4  RT-AC68U_374.43_37E4j9527.trx
37ac3069c688e08f071ed9e841576f5b625fd7bc26b1b78842efa788549071ae  RT-AC56U_374.43_37E4j9527.trx

(Legacy Only Builds)
9d31c752d33488ab619155d0bb6e5326e6c273137b3c5407ef1c45cf3008180a  RT-AC68U_3.0.0.4_374.43_2-37L4j9527.trx
f6b9ad8d9e96d5773ce13f53c03991ca636ab1eb3567bb301f07af66341bbb13  RT-AC56U_3.0.0.4_374.43_2-37L4j9527.trx
516d9161ded42d679d677ce9ac76b28d86d42fd3714d89515479aafee8202756  RT-N16_3.0.0.4_374.43_2-37L4j9527.trx
6914a88daa6e11bf7b7cf73d714a0899acdc22621d203cf9de4a35712dbbe20c  RT-AC66U_3.0.0.4_374.43_2-37L4j9527.trx
9101a8617ebf0d22743188f1f193c960715bbb3530249ab4f5ec013bfeaf3ef6  RT-N66U_3.0.0.4_374.43_2-37L4j9527.trx
 

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