Beta Asuswrt-Merlin 3006.102.4 Beta is now available

[alan6854321]

Just curious if you factory reset after updating to this version. I am thinking about flashing this version, but I don't want to go through the process of setting everything up after a factory reset. I will be updating from Asuswrt-Merlin 3004.388.8_4.

No factory reset, just uploaded 3006 over 3004.
Didn't even remove/add my Aimesh node.

 

[dave14305]

I am tempted to change the behaviour so "Router" would always only redirect to the router itself, and people wanting to redirect to a custom server configured on the DHCP page would then need to configure them as a Custom DNS Director target.

Or add a separate “DHCP DNS” mode in DNS Director to handle the common Pi-Hole scenario.

 

[bennor]

I am tempted to change the behaviour so "Router" would always only redirect to the router itself, and people wanting to redirect to a custom server configured on the DHCP page would then need to configure them as a Custom DNS Director target.

A question if you went down that road. Wouldn't that possibly present a problem for those who, for example, use two Pi-Hole instances on their network since the DNS Director field options only allow you to select a single Custom DNS User entry per client/guest network? Or would the DNS Director page be changed or configured to allow users to use two DNS entries per network or client?

 

[dave14305]

Or would the DNS Director page be changed or configured to allow users to use two DNS entries per network or client?

Even today, it ignores the DHCP DNS 2 entry. iptables can’t redirect to 2 different destinations.

 

[GWTechTalk]

I have tried a few different configurations in the past and they worked for my needs at the time. Main and Guest network can be the same IP block where you don't have to have a separate DHCP for guest. However, you can have a different block and just properly set the subnet masks to allow communication back and forth between both DHCP instances. Sure its a bit complex / advanced for some but it works.

Or in terms of needing two PiHoles isn't really necessary you could setup VLAN / Trunk or just have an open subnet on the PiHole to allow both instances talk back and forth to both networks. Personally, I just use the same subnet and the one thing the Guest network does for me is provide that backward compatibility to those devices that can't handle communication on a network where WP3 is optional along side WPA2, ie. older printers.

I guess I could see some instances where setup could get very complicated but those would be mostly enterprise or business situations. I'm not sure anyone thinks about ASUS in business or enterprise they normally go with Ubiquity.

DNS director only allowing a single IP redirect doesn't matter as long as that single redirect goes to an "onsite" DNS server or to the router.

 

[RMerlin]

Or add a separate “DHCP DNS” mode in DNS Director to handle the common Pi-Hole scenario.

I suspect that might lead to issues since for a majority of users the DHCP field would be empty, which means DNS Director would have no target to redirect to. I bet a lot of people would blindly select that option, and it wouldn't do anything. Probably safer to have people configure the server manually as a custom target instead, so they are fully aware of what they are doing.

 

[RMerlin]

I upgraded the GT-AX11000 Pro from the stock 3.0.0.6.102_34750 to the beta version and noticed the 160 MHz options were all missing in the wireless settings. Specifically, the checkbox "enable 160MHz" was not there and the drop down for channel bandwidth did not have 20/40/80/160 option. It showed a 20/40/80 option. Sorry I didn't capture a screenshot. I went back to factory, rebooted, and went through the upgrade again, same result. I did not do a factory reset. Interesting the wireless logs did show that 160 MHz was functioning when I selected the 20/40/80 drop down option.

Shows up just fine on my GT-AX11000_PRO. Make sure you are in a region that does allow 160 MHz channel width.

 

[nagyimre1980]

I would like a DNS setting where clients do NOT receive the router as the DNS server (e.g., 192.168.0.1) but instead use my ISP’s current DNS server, which the WAN port received.
Am I correct in seeing that there is no such option? Do I have to manually enter the DNS server addresses?
The problem with this is that if it changes, I have to update it manually. Isn’t there a way to automate this?

 

[jerry6]

Shows up just fine on my GT-AX11000_PRO. Make sure you are in a region that does allow 160 MHz channel width.

View attachment 65112

Works fine on my 1100pro as well

 

[Ripshod]

Shows up just fine on my GT-AX11000_PRO

Works fine on my 1100pro as well

I did not do a factory reset

Mmmmmm, I wonder
[/sarc]

 

[dave14305]

I noticed an oddity today with the invocation of “service-event-end” custom script. I was cleaning up a test SDN network and the action generated the following service restart with multiple services being restarted (the final one being stubby):

Apr 18 09:15:16 rc_service: cfg_server 3201:notify_rc start_sdn_del;restart_wireless;restart_qos;restart_firewall;restart_stubby;

The service-event and firewall-start scripts are invoked correctly for each service.

Apr 18 09:15:16 custom_script: Running /jffs/scripts/service-event (args: start sdn_del)
Apr 18 09:15:16 custom_script: Running /jffs/scripts/service-event (args: restart wireless)
Apr 18 09:15:17 custom_script: Running /jffs/scripts/firewall-start (args: eth0)
Apr 18 09:15:17 custom_script: Running /jffs/scripts/firewall-start (args: eth0)
Apr 18 09:15:28 custom_script: Running /jffs/scripts/firewall-start (args: eth0)
Apr 18 09:15:29 custom_script: Running /jffs/scripts/firewall-start (args: eth0)
Apr 18 09:15:29 custom_script: Running /jffs/scripts/service-event (args: restart qos)
Apr 18 09:15:33 custom_script: Running /jffs/scripts/service-event (args: restart firewall)
Apr 18 09:15:34 custom_script: Running /jffs/scripts/firewall-start (args: eth0)
Apr 18 09:15:34 custom_script: Running /jffs/scripts/service-event (args: restart stubby)

But the service-event-end script is only invoked for the last service being restarted (stubby in this example).

Apr 18 09:15:34 custom_script: Running /jffs/scripts/service-event-end (args: restart stubby)

It looks like this command moved, perhaps unintentionally, for wifi6 devices in the GPL merge. It looks a little suspect in a3611d594af. It should be called before the goto again line.
Branch 3006.102:

asuswrt-merlin.ng/release/src/router/rc/services.c at f0090912d5a20b1bb6b4cd6f554557438dbe23d2 · RMerl/asuswrt-merlin.ng

Third party firmware for Asus routers (newer codebase) - RMerl/asuswrt-merlin.ng

github.com

Branch 3006.102-wifi6:

asuswrt-merlin.ng/release/src/router/rc/services.c at e040c85eebc5d46520a0bea29e6a96f9a07a0846 · RMerl/asuswrt-merlin.ng

Third party firmware for Asus routers (newer codebase) - RMerl/asuswrt-merlin.ng

github.com

 

[MDM]

I would like a DNS setting where clients do NOT receive the router as the DNS server (e.g., 192.168.0.1) but instead use my ISP’s current DNS server, which the WAN port received.
Am I correct in seeing that there is no such option? Do I have to manually enter the DNS server addresses?
The problem with this is that if it changes, I have to update it manually. Isn’t there a way to automate this?

That's the default behavior.

WAN - Internet Connection-WAN DNS Setting-DNS Server-(ISP - Get the DNS IP from your ISP automatically), unless you changed it...
And LAN-DNS Director should be set to default No Redirection too.

 

[nagyimre1980]

That's the default behavior.

WAN - Internet Connection-WAN DNS Setting-DNS Server-(ISP - Get the DNS IP from your ISP automatically), unless you changed it...
And LAN-DNS Director should be set to default No Redirection too.

LAN-DNS director disabled. Clients still receive the 192.168.0.1 DNS address instead of the provider's DNS servers.

 

[Ripshod]

LAN-DNS director disabled. Clients still receive the 192.168.0.1 DNS address instead of the provider's DNS servers.

There's a difference between 'disabled' and 'no redirection'.

 

[dave14305]

LAN-DNS director disabled. Clients still receive the 192.168.0.1 DNS address instead of the provider's DNS servers.

You can do this with some custom scripts.

/jffs/scripts/dnsmasq.postconf

#!/bin/sh

CONFIG="$1"
. /usr/sbin/helper.sh

for dns in $(nvram get wan0_dns_r); do
    landns="${landns+$landns,}$dns"
done

if [ -n "$landns" ]; then
    pc_delete "dhcp-option=lan,6," $CONFIG
    pc_append "dhcp-option=lan,6,$landns" $CONFIG
fi

Then restart dnsmasq with:

service restart_dnsmasq

Clients will eventually get the new DNS servers when they renew their lease, or you can reboot the router, or force a renewal on the clients if you want.

 

[dave14305]

There's a difference between 'disabled' and 'no redirection'.

Why would you need “No redirection” if the whole feature is disabled?

 

[RMerlin]

It looks like this command moved, perhaps unintentionally, for wifi6 devices in the GPL merge. It looks a little suspect in a3611d594af. It should be called before the goto again line.

Looks like a bad merge indeed. Thank you, I'll move it back up.

 

[MDM]

LAN-DNS director disabled. Clients still receive the 192.168.0.1 DNS address instead of the provider's DNS servers.

And the WAN setting?
Also LAN - DHCP Server-DNS Server 1 and 2 should be empty!

 

[dave14305]

And the WAN setting?
Also LAN - DHCP Server-DNS Server 1 and 2 should be empty!

I don’t think you’re understanding what he wants to accomplish. He wants to use the ISP DNS servers without going through dnsmasq on the router. At least that’s my interpretation. Whether that’s a useful configuration for most people is still up for debate.

 

[MDM]

I don’t think you’re understanding what he wants to accomplish. He wants to use the ISP DNS servers without going through dnsmasq on the router. At least that’s my interpretation. Whether that’s a useful configuration for most people is still up for debate.

Hmmm maybe you are right, but he didn't mention it that way...
I understood as written - he wants just to use ISP’s DNS servers.

Or, he don't understand the fact that although the clients go through the router IP, they are served ISP's DNS?