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!

IS what I consider a bug guys, I expect it also exists in asus and non forked merlin firmwares.

If disabling ping's in the firewall, they still are allowed on ipv6 traffic (with ipv6 firewall enabled of course)..
Properly replying to IPv6 ping requests is required according to the RFC. So this is by design and not a bug.

Sent from my Nexus 4 using Tapatalk
 
interesting.

Its a bug in my view until asus display a notice or warning of some sort showing it wont be blocked when the on option is used.
 
I have worse wifi signal with The latest version compared to The first fork version :|

Skickat med Sony Z2 via Tapatalk pro
 
Just want to check back in. Several days in a row now on 03 and I couldn't be any more happy. This is truly the best my router has ever ran. No more reboots to get my speed back up. Now my son's Wii U in the far bedroom no longer has issues, and his Roku 3 in that same room gets a full 5 bars (was getting 2 bars on latest official release). The minidlna is running super smooth and quick. Video's load up almost instantly now and without hiccups, dropouts, etc.

Great job and thanks again for all your hard work john!
 
I have worse wifi signal with The latest version compared to The first fork version :|

Skickat med Sony Z2 via Tapatalk pro

Well....don't know what to say. You can see the changelog (or go to github) and see that nothing was changed with respect to wifi. Maybe your neighbor got a new wireless telephone or microwave that happened to be on?
 
Just want to check back in. Several days in a row now on 03 and I couldn't be any more happy. This is truly the best my router has ever ran. No more reboots to get my speed back up. Now my son's Wii U in the far bedroom no longer has issues, and his Roku 3 in that same room gets a full 5 bars (was getting 2 bars on latest official release). The minidlna is running super smooth and quick. Video's load up almost instantly now and without hiccups, dropouts, etc.

Great job and thanks again for all your hard work john!

The opposing opinion (versus the previous post) :) Thanks for the positive feedback....much appreciated.
 
John, I've been up for 16 days on v1 with my AC66R. The only messages in my system log after my first reboot are my devices' DHCP requests. No errors, no dropouts, and a strong 5GHz signal.

I've read your changelogs on v2 and v3 and, for my uses, there's no reason to upgrade further. I can finally just use my network without having to tweak, investigate, or wonder if it's working at peak performance. I have set it and now I can forget it. :D

Big thanks to you (and Merlin of course :) ) for all your hard work!
 
I've read your changelogs on v2 and v3 and, for my uses, there's no reason to upgrade further. I can finally just use my network without having to tweak, investigate, or wonder if it's working at peak performance. I have set it and now I can forget it. :D

Exactly one of the goals of this fork, to fix a couple of things and get to that state. Thanks!
 
This could be an issue already exists.



I setup https login at the admin page. I was configuring all other settings. When I turned on qos, I was no longer able to get to the UI. Saw the "settings have been updated......... Use updated IP and port".



Since I couldn't get to the UI, I reset the router. I went back to the admin config and set it to use http and HTTPS. I then logged in his https. I then changed my lan up address on the router. I tried to access the router at the new address over https. I again got the same message as above. "settings have been updated......... Use updated IP and port".



I logged in via http and tried switching the login auth in the admin page to http and thn back to both. This resulted in not being able to access the UI over http or https.



Anybody else see this?
 
.... I then changed my lan up address on the router. I tried to access the router at the new address over https. I again got the same message as above. "settings have been updated......... Use updated IP and port"....

You didn't say what addressing you tried to set up for the router, but I've read in other posts that the router definitely doesn't like anything other than netmask 255.255.255.0, and sometimes has problems even changing from the default 192.168.1.1 router address. If you leave those at the defaults, does everything work OK?
 
I did notice when I switch the UI login to both or https, the UI just sits there saying "processing" but it never shows progress. I eventually have to log back in.
 
I left the netmask alone. I'll see if it is ok if i leave the lan up default.



No, I just set the login to use both HTTPS and http while my lan ip is 192.168.1.1. I can login on http, but https gives me the error in my original post.
 
No, I just set the login to use both HTTPS and http while my lan ip is 192.168.1.1. I can login on http, but https gives me the error in my original post.

I think I may have figured it out....the router 'remembers' the last connection and type....if you are trying to switch between logging on with http and then https, make sure you hit the 'Logout' button on the top of the screen first.
 
i run v1 from the begining without any problem, is there a good reason to switch to v3?

If there is nothing in v3 that you think is applicable to you and your are running without any problems, no good reason. I don't believe that are any gaping security issues in v1 (as compared to the other releases) and it contains the fixes for the problems someone was most likely to see.

(see post #268 for someone else who just did the same analysis and came to the conclusion to stay on v1)
 
Last edited:

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