Asuswrt-Merlin 378.56 is available

[fr33z0n3r]

Asus chose to limit ports to unprivileged ones for some reason. I could look into removing that restriction if it doesn't create any other problem.

The reason it "worked" with 378.55 was because of a bug in previous versions that wasn't properly checking the port.

Harumph to Asus. I'm not a fan of these types of decisions. It is quite annoying to have to enter a port. And if they are moving that to an high port due to root requirements, I can somewhat understand, but really? Is something else using port 443 by default? If so, that logic is bogus IMHO.

I'm not asking for miracles, nor demanding that you make anything a default, but I wouldn't mind the option if it is easy to undo. Thanks for the quick response!

 

[RMerlin]

It's an openssh generated RSA key, but I think it went wrong because I pasted the private key directly. I don't want to paste my real key here, but here's a newly generated similar one:

Fixed a buffer overrun with keys > 2047 characters.

 

[user1999]

Click on client_function.js and repost the content of that line.

Found the problem. I had a device name with "'" character. I renamed it and its working fine now.

 

[GoNz0]

Asus actually added a a territory code selector a few months ago.

Bootloader of the newest Broadcom devices is encrypted, so forget about hex editing in the future.

user selectable? I don't see it.

And I take it if I stick with my current bootloader they can't cripple my router?

 

[Icemanz]

Pinging by hostname works fine for me. I can ping any device that has a hostname defined on the DHCP static page, using that hostname. I even access all my development routers by their hostname defined on that page, i.e. http://rtac68:8080/ from within my LAN.

I had a similar problem and was scratching my head for a while. Here's what I've learned (all experience is based on .55).

Straight up: If you're using the merlin fw dns filtering for your client (or all clients) it appears (from my limited experience) by design ALL requests get forced to go to your chosen server - this server will not know your internal server names so they'll never be able to resolve "yourcomputer". Secondly, same rule applies if you went and added ANY OTHER DNS server (your ISP's, googles etc) to your clients either manually or to be handed out via DHCP. ONLY the router will resolve yourcomputer and ONLY if it handed that name out via DHCP (or your statically defined it and then manually assigned it on the client).

Beyond that, if you're like me and just configured everything up stock there's a couple of things:

Your "single label" computer name is a nonstandard form of address. To cope with this different OS's will use different methods to turn this back into an IP (netbios, dns, other) - resulting in weird shirt. eg nslookup being able to resolve your pc name but ping will not. Or more confusingly, a windows machine will resolve the name but OSX will not. I thought this was the router's fault, it's not.

This oddity results in you being able to do things like "browse to" windows servers but be unable to "ping" them.

The quick fix I have found is to get rid of the "single label" names such as "mycomputer" and define a bogus domain (eg my.lan) and hand this out via DHCP as the default domain search suffix (or manually configure if it you use static IP's).

Doing this forces all resolutions to go via DNS because when you try to go to "mycomputer" and the othre methods fail to resolve it, it will eventually get to DNS at which point it goes "mycomputer" is bogus, I will try mycomputer.my.lan and forward it to my dns server (the router) which will resolve it.

Edit: I said parental controls, I meant dns filtering.

 

[Trebuin]

Ok, I've put my apple router into Auto 5G because the manual turns the AC system off. Now that it is on, the ASUS router does not see it, though all my other devices do. The channel keeps rolling to 132. Any ideas how to get the ASUS to see it using this firmware?

 

[RMerlin]

I also have to add that, again, chaning the icon to a custom one, makes the LAN DHCP device name to disappear...

Fixed. Asus had made a lot of changes to the networkmap in 9177, so the previous code preserving the hostname was lost in the merge.

 

[bookedirl]

Has anyone had issues with an iPhone 6S constantly dropping connection? I have an iPhone 6 that has no issues but my wifes iPhone 6S is. Not sure what's causing it. I tried both bands and they have the same result. I normally wouldn't care so much but my wife is nagging me

Running 378.56 on 87u

 

[Magnus33]

Asus AC68U update went perfectly fine but did run into one odd problem.

Suddenly i can't map network drives?

 

[hd0120]

I'm currently on Merlin Fork 14E1. What should I do to flash 378.56?
Thank you.

 

[RMerlin]

Hi RMerlin, thanks for looking into it.
That Subnet is actually on the firmware that works (54_2) and it is somehow calculated automatically (no place on the GUI to specify it).

Fixed. Static key authentication was trying to setup a subnet topology, causing the failure.

 

[RMerlin]

I'm currently on Merlin Fork 14E1. What should I do to flash 378.56?
Thank you.

Flash, then do a factory default reset and reconfigure your router.

 

[hd0120]

Flash, then do a factory default reset and reconfigure your router.

Is factory default reset the same as holding the WPS button while restarting the router?
Thanks again.

 

[RMerlin]

Is factory default reset the same as holding the WPS button while restarting the router?
Thanks again.

Yes.

 

[RMerlin]

What good are undocumented settings if they aren't documented somewhere *smile*?

You know what they say about Fight Club...

 

[RMerlin]

user selectable? I don't see it.

Go to Tools->Sysinfo and see if "loclist" is in the list of features. If not, then it means Asus might not have enabled it yet. I don't know which model has it, it gets set in a closed source component. It's also possible it might still be a work-in-progress. All I know is I saw they added code for it, and it will add a Region selector on the Wireless Professional page once enabled.

And I take it if I stick with my current bootloader they can't cripple my router?

The bootloader contains all the regional data it relies on. They've upgraded the bootloader on a few occasions, but usually that means any existing data gets copied to the new one.

 

[charlie2alpha]

By the way, there's a new firmware for the DSL-AC68U which has this interesting parts in the changelog:

ASUS DSL-AC68U Firmware version 3.0.0.4.378_9168 (This product supports both Annex A and Annex B)
Release Note
-Remove mDNSNetMonitor related debug logs.
-Fixed 802.1Q enabled with VLAN ID 0 setting cannot take effect issue, 802.1Q setting reverted back to disabled.

Seems ASUS is aware that mDNSNetMonitor floods the logs already.

 

[Marc Elser]

Hi,

Does anyone know why accessing the router through https:// is sometimes very slow. I recently disabled http:// access to the router leaving only https with port 8443 enabled as I wanted to put nginx to port 80 (which is blocked by UI otherwise). Accessing the router through http:// always worked perfectly. But since I access the router through https:// it takes sometimes ages to load a ui page (30-60secs). Strange thing is that it does not happen with every click. Some clicks work perfectly ok with no noticeable delay, and suddenly when you click somewhere you that extrem delay. Sometimes so long that chrome reports that the web page is not responding if you want to cancel or wait. I also tried with Firefox and IE with no different behaviour. I even imported the self signed ASUS certificate in chrome so that I don't get a warning when accessing the router with no change. I though might have been a bug in 378.55 but it has exactly the same behaviour in 378.56 too. Anyone experiencing the same issues or is this a known problem or so?

Thanks

 

[cowboy]

Hi,

Does anyone know why accessing the router through https:// is sometimes very slow. I recently disabled http:// access to the router leaving only https with port 8443 enabled as I wanted to put nginx to port 80 (which is blocked by UI otherwise). Accessing the router through http:// always worked perfectly. But since I access the router through https:// it takes sometimes ages to load a ui page (30-60secs). Strange thing is that it does not happen with every click. Some clicks work perfectly ok with no noticeable delay, and suddenly when you click somewhere you that extrem delay. Sometimes so long that chrome reports that the web page is not responding if you want to cancel or wait. I also tried with Firefox and IE with no different behaviour. I even imported the self signed ASUS certificate in chrome so that I don't get a warning when accessing the router with no change. I though might have been a bug in 378.55 but it has exactly the same behaviour in 378.56 too. Anyone experiencing the same issues or is this a known problem or so?

I am experiencing exactly the same behavior on my RT-AC87U when I log-in through chrome (I disabled http too). I sometimes (maybe always) refresh the page when it is taking too long because then it loads faster. This behavior is very often happening when I click on Adaptive QoS or Traffic Analyzer. But when I log-in through Microsoft Edge I don't experience the slow down.

I imported the certificate too, but I am still getting every time the warning to proceed.

 

[GoNz0]

Go to Tools->Sysinfo and see if "loclist" is in the list of features. If not, then it means Asus might not have enabled it yet. .

No, not showing in your latest AC68 release.