[Beta] Asuswrt-Merlin 384.12 Beta is now available

[Grisu]

I am having an issue on the network map page where the internet status comes up as disconnected even though the wan connection is connected. This started after making changes in the NTP Settings

I think there has been a post where changing ping test from ip to url (or vice versa) helped to solve this.

 

[bobpow]

Check what your Network Monitoring settings are on the Administration / System page. Then verify on the tools other settings page what “Wan: Use local caching server...” is set to. Should be set to no by default in 384.12 now.

Dave,
What is the purpose of the network monitoring settings, ping and dns query? I have them turned off, should they be on?

 

[hjohan13]

You probably have to do a complete factory reset once the new firmware is loaded. It must be some setting that gets messed up when you update from the old to new firmware.

I did a complete factory reset prior to installing 384.12. No old settings used. All new from vanilla.

 

[Asad Ali]

I did a complete factory reset prior to installing 384.12. No old settings used. All new from vanilla.

That's a general mistake most users make, you'll need to do a factory reset AFTER you're on the latest firmware.

 

[L&LD]

I did a complete factory reset prior to installing 384.12. No old settings used. All new from vanilla.

The proper order is flash the firmware you want first, then do an M&M config.

 

[hjohan13]

The proper order is flash the firmware you want first, then do an M&M config.

Sorry for bad English. I always do a factory reset with ALL VANILLA .... always...

 

[octopus]

Just loaded Beta2 and seems working just fine.
Uptime 0 days 0 hours 15 minute(s) 15 seconds

Thank you Rmerlin.

Okey found some with samba GUI. Anyone else see this?

 

[RDaneel]

The router doesn't expose port 445 to the WAN. If that port is visible, then either you disabled the router firewall, or you forwarded it. By default all WAN ports are blocked.

This generally indicates that the ISP is actively blocking that port, to protect their own customers

I did not disable the firewall or forward any ports, or I would have mentioned something about this (or not made the post at all ).

And I get the "closed" response means "actively rejected".

I think you have most likely hit the nail on the head with the "ISP possibly doing this themselves" bit... I will inquire further with Comcast, although getting to someone that would both understand the question and have access to the answer may be challenging.

Thanks as always, Mr Wizard!

 

[scjr]

Beta 2 has been running here for a few hours. Everything is well.

 

[L&LD]

Updated to RMerlin 384.12 Beta 2 from Beta 1 (dirty flash, all) on RT-AC86U, RT-AC3100, and RT-AC68U. No issues.

 

[Asad Ali]

I did not disable the firewall or forward any ports, or I would have mentioned something about this (or not made the post at all ).

And I get the "closed" response means "actively rejected".

I think you have most likely hit the nail on the head with the "ISP possibly doing this themselves" bit... I will inquire further with Comcast, although getting to someone that would both understand the question and have access to the answer may be challenging.

Thanks as always, Mr Wizard!

That bit is easy to check, put your PC in your router's DMZ and run the test again. If the port still show it's closed, your ISP is doing it.

 

[jerry6]

384-12 beta2 working well Net tools is back on my AC5300

 

[Billy Chaney]

Upgraded to beta 2 and all is well.

 

[rgnldo]

Okey found some with samba GUI. Anyone else see this?

View attachment 18266

It's still the BETA version. Here it is also like this. Thankfully that samba that I have customized. But worth the notice.

 

[Gar]

Beta 2 A-OK...thanks again!

 

[Deleted member 62525]

Updated to new Beta 2 and running good.
RT86U
Diversion, Skynet, OpenVPN Client

 

[bbunge]

My stubby customizations did not all function after I flashed beta2. DNSSEC in stubby works until a reboot. Not a show stopper for most.
Would like a gui setting to turn round robin on/off. On all the time is not needed as the stubby bug was fixed.

Sent from my SM-T380 using Tapatalk

 

[Deleted member 62525]

My stubby customizations did not all function after I flashed beta2. DNSSEC in stubby works until a reboot. Not a show stopper for most.
Would like a gui setting to turn round robin on/off. On all the time is not needed as the stubby bug was fixed.

Sent from my SM-T380 using Tapatalk

You can. Simply edit Stubby.yml file and set round_robin flag from 1 to 0.

 

[RDaneel]

In investigating why I am seeing a port or ports unexpectedly blocked (as in, actively rejecting connection requests as opposed to just not responding), I came across this:

https://www.xfinity.com/support/articles/list-of-blocked-ports

... which not only gives some details on what [my ISP] Comcast may choose to block on their side, but along with some related articles, like

https://business.comcast.com/help-and-support/internet/ports-blocked-on-comcast-network/

... gives us the idea that that things can be both "dynamic" and even possibly "per-customer", although the latter is supposed to be "rare".

In any case, the world is just getting a little more complicated, no longer always leaving things up to you and your router (with or without NAT) and your firewall.

Oh, and BETA 2 of 384.12 is looking fine so far - and, while it was already in BETA 1, I can also verify that the fix for RT-AX88U / IPv6 problems is apparently functioning properly, given that I removed the script-based workaround before installing either of these BETAs.

 

[bbunge]

You can. Simply edit Stubby.yml file and set round_robin flag from 1 to 0.

Nope. Not that easy...

You need /jffs/scripts/stubby.postconf with properties set to 755

#!/bin/sh
CONFIG=$1
source /usr/sbin/helper.sh
pc_replace "round_robin_upstreams: 1" "round_robin_upstreams: 0" $CONFIG

Then restart stubby...