Beta Asuswrt-Merlin 3006.102.4 Beta is now available

[robinjoo1]

Al my other LEDs are off then why the wifi not noticed this suddenly

 

[bennor]

Al my other LEDs are off then why the wifi not noticed this suddenly

Did you make any changes in the router GUI right before you noticed the one or two front LED's being on while others are off?

With the 3006 firmware I (and I think a few others) have experienced an issue where if you have the LED's set to off in the GUI. Making a change in the router GUI can, for what ever reason, trigger one or two of the front LED's to switch on and stay lit. Have to cycle the LED button on then off in the GUI to get the single LED to turn off. Commented about it here in the 3006.102_34336 stock Asus firmware release discussion for the RT-AX86U Pro.

 

[robinjoo1]

@

Did you make any changes in the router GUI right before you noticed the one or two front LED's being on while others are off?

With the 3006 firmware I (and I think a few others) have experienced an issue where if you have the LED's set to off in the GUI. Making a change in the router GUI can, for what ever reason, trigger one or two of the front LED's to switch on and stay lit. Have to cycle the LED button on then off in the GUI to get the single LED to turn off. Commented about it here in the 3006.102_34336 stock Asus firmware release discussion for the RT-AX86U Pro.

I did not make a changed it lightend up after a restart u enable and disable led again
And now it's gone

 

[jksmurf]

With the 3006 firmware I (and I think a few others) have experienced an issue where if you have the LED's set to off in the GUI. Making a change in the router GUI can, for what ever reason, trigger one or two of the front LED's to switch on and stay lit.

I’m not going crazy then. I thought the LED issue had finally been fixed (perhaps off survives a reboot with no changes?), but yes, I’ve very recently noticed just one or two LEDs light up after a change (and I’m not talking about the one change in Administration which you toggle to enable them ;-) ).

 

[dave14305]

It would probably be more intuitive as well, since "Router" would truly mean "the router itself" rather than "Whatever is configured on the DHCP server, with the fallback being the router itself".

Since you seem to have decided already, don’t forget to update the text on the DNS Director ASP page describing the Router mode.

 

[pershoot]

Beta2 looks ok, initially, over here on RT-AX86U Pro.

Beta - Asuswrt-Merlin 3006.102.4 Beta is now available

Al my other LEDs are off then why the wifi not noticed this suddenly

www.snbforums.com

 

[visortgw]

Beta2 looks ok, initially, over here on RT-AX86U Pro.

Beta1? Beta2 hasn't dropped yet...

 

[jksmurf]

Beta1? Beta2 hasn't dropped yet...

Oh come on, beta versions are like round birthdays, it’s just a number

 

[pershoot]

Beta1? Beta2 hasn't dropped yet...

I built it from source.

 

[nagyimre1980]

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.Thank you, I'll try it out today.

Couldn't this be integrated into Merlin FW? The web interface's wording suggests exactly this functionality: it automatically retrieves the DNS servers. If it retrieves them, why doesn't it advertise them via the DHCP server?"

Let me know if you need further assistance!

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.

Thank you, I'll try it out today.
@RMerlin
Couldn't this be integrated into Merlin FW? The web interface's wording suggests exactly this functionality: it automatically retrieves the DNS servers. If it retrieves them, why doesn't it advertise them via the DHCP server?"

Let me know if you need further assistance!

 

[RMerlin]

Couldn't this be integrated into Merlin FW? The web interface's wording suggests exactly this functionality: it automatically retrieves the DNS servers. If it retrieves them, why doesn't it advertise them via the DHCP server?"

Because it makes little logical sense. Having the clients not using the router mean that they will be unable to resolve any LAN hostname, including the router itself. You normally want the router to obtain the ISP's DNS addresses, then have the router proxy them for your whole LAN. Caching will improve name resolution performance, in addition to resolving local hostnames.

The DHCP setting is largely intended for people who host a different resolver within their LAN, like a pihole.

 

[RMerlin]

Also, what DNS server should DHCP provide to your LAN clients if the Internet connection isn't up yet? The DHCP service starts before the Internet connection does. And if the DNS server changes, then your LAN clients will have no way of knowing it, since their leases may potentially not expire for multiple hours.

The DHCP server needs to provide a 1) static DNS server that will be up, and 2) which doesn't need to change within the LAN client's leases duration.

 

[alan6854321]

A bunch of message I've never seen before just appeared in syslog.
Any ideas what they are ?

19-Apr 02:00:30 AX SIG_UPDATE: current sig : 2450
19-Apr 02:00:30 AX SIG_UPDATE: latest sig : 2454
19-Apr 02:00:30 AX SIG_UPDATE: < sig_ver, Do upgrade
19-Apr 02:00:30 AX SIG_UPGRADE: wget trf FULL : Official
19-Apr 02:00:35 AX SIG_UPGRADE: wget sig, exit code: 0
19-Apr 02:00:41 AX SIG_UPGRADE: wget rsa, exit code: 0
19-Apr 02:00:41 AX SIG_UPGRADE: Download trf/rsa OK
19-Apr 02:00:42 AX SIG_UPGRADE: sig check OK
19-Apr 02:00:42 AX SIG_UPGRADE: mv /jffs/signature/rule.trf to jffs
19-Apr 02:00:42 AX SIG_UPGRADE: Do restart_wrs
19-Apr 02:00:42 AX rc_service: rc 31398:notify_rc restart_wrs
19-Apr 02:00:42 AX custom_script: Running /jffs/scripts/service-event (args: restart wrs)
19-Apr 02:00:45 AX BWDPI: fun bitmap = 43f
19-Apr 02:02:50 AX SIG_UPDATE: current sig : 2454
19-Apr 02:02:50 AX SIG_UPDATE: latest sig : 2454

 

[jass]

A bunch of message I've never seen before just appeared in syslog.
Any ideas what they are ?

19-Apr 02:00:30 AX SIG_UPDATE: current sig : 2450
19-Apr 02:00:30 AX SIG_UPDATE: latest sig : 2454
19-Apr 02:00:30 AX SIG_UPDATE: < sig_ver, Do upgrade
19-Apr 02:00:30 AX SIG_UPGRADE: wget trf FULL : Official
19-Apr 02:00:35 AX SIG_UPGRADE: wget sig, exit code: 0
19-Apr 02:00:41 AX SIG_UPGRADE: wget rsa, exit code: 0
19-Apr 02:00:41 AX SIG_UPGRADE: Download trf/rsa OK
19-Apr 02:00:42 AX SIG_UPGRADE: sig check OK
19-Apr 02:00:42 AX SIG_UPGRADE: mv /jffs/signature/rule.trf to jffs
19-Apr 02:00:42 AX SIG_UPGRADE: Do restart_wrs
19-Apr 02:00:42 AX rc_service: rc 31398:notify_rc restart_wrs
19-Apr 02:00:42 AX custom_script: Running /jffs/scripts/service-event (args: restart wrs)
19-Apr 02:00:45 AX BWDPI: fun bitmap = 43f
19-Apr 02:02:50 AX SIG_UPDATE: current sig : 2454
19-Apr 02:02:50 AX SIG_UPDATE: latest sig : 2454

Seems like your Trend Micro signature file has been updatet to latest version...

 

[bennor]

Beta2 looks ok, initially, over here on RT-AX86U Pro.

I built it from source.

If you compiled your own personal version of the firmware you should edit your initial post and make that very clear in your initial post where you mention a "Beta2" otherwise as indicated you are intentionally confusing people into thinking Asus-Merlin released a Beta2 when apparently he hasn't (as of this post). Further this is supposed to be a discussion about issues with Asus-Merlin Beta, not firmware one someone created and possibly modified themselves that no one else can apparently test.

 

[pershoot]

If you built your own personal version of the firmware you should edit your initial post and make that very clear in your initial post where you mention a "Beta2" otherwise as indicated you are intentionally confusing people into thinking Asus-Merlin released a Beta2 when apparently he hasn't (as of this post). Further this is supposed to be a discussion about issues with Asus-Merlin Beta, not firmware one someone created and possibly modified themselves that no one else can apparently test.

I am here to aid in testing which also may mean picking up changes in advance that RMerlin may or may not release to the bigger populous, for broader testing at a particular X time; it could be helpful / useful before dissemination. The message was directed to RMerlin. I should have added the @ sign.

If RMerlin has not made a release, it is built from source from a public repository; it is implied. RMerlin has also stated that B2 likely will have an imminent release this weekend (above) which prompted me to pick up changes for testing specifically on my end, in advance. With that being said, the message (above) has been edited to link the proceeding message reply to alleviate any potential confusion.

I am not modifying the source at all; I am a consumer (currently). If I had or do so, I would certainly not post any reports about it because it would be a deviation. In that case, I would submit a PR for assessment and the discussion would be housed there (GitHub). If there is a changeset I may be having an issue with I would post here (for awareness) and there, for discussion and remediation therein, to aid in a particular development stage.

If there is confusion, please do reply back so it can be (further) clarified.

 

[RMerlin]

Beta 2 has been uploaded. It contains a few minor fixes, but also a newer GPL for the RT-BE92U which will address the CPU-related issues of the former GPL that was used.

I have also updated the wireless drivers for the RT-BE96U and GT-BE98_PRO. They were previously using an older wireless driver extracted from a firmware release because their GPLs were missing it. I have now extracted the drivers from the 102_37812 firmwares. I don't really expect any difference, the files are the same size, but there are a few changed bytes in them, so it's possible their radio calibration tables may have been tweaked over the previous version.

Changelogs for all three branches:

Wifi 6:

fe104c9774 (3006.102) webui: updated DNS Director notes
dcef132c02 Update RT-BE96U and GT-BE98_PRO wireless dongle driver to 102_37812 builds
1cc4127a8d miniupnpd: fix building (missing header file)
85c9d353af miniupnpd: update to 2.3.8
198e89a5e8 rc: move service-event-end back within again: loop
170d2e48b5 rc: Have DNS Director "Router" mode use REDIRECT target instead of DNAT to LAN IP in iptables.
8d40fbd7f2 Bumped revision to beta 2
879ad023d4 webui: fix missing button to remove Offline Client List entries
c77742afb1 webui: cleanup sysdep Wireless pages that are no longer existant

Wifi 7:

fe104c9774 (3006.102) webui: updated DNS Director notes
dcef132c02 Update RT-BE96U and GT-BE98_PRO wireless dongle driver to 102_37812 builds
1cc4127a8d miniupnpd: fix building (missing header file)
85c9d353af miniupnpd: update to 2.3.8
170d2e48b5 rc: Have DNS Director "Router" mode use REDIRECT target instead of DNAT to LAN IP in iptables.
8d40fbd7f2 Bumped revision to beta 2
879ad023d4 webui: fix missing button to remove Offline Client List entries
c77742afb1 webui: cleanup sysdep Wireless pages that are no longer existant

RT-BE92U:

fe104c9774 (3006.102) webui: updated DNS Director notes
dcef132c02 Update RT-BE96U and GT-BE98_PRO wireless dongle driver to 102_37812 builds
1cc4127a8d miniupnpd: fix building (missing header file)
85c9d353af miniupnpd: update to 2.3.8
170d2e48b5 rc: Have DNS Director "Router" mode use REDIRECT target instead of DNAT to LAN IP in iptables.
8d40fbd7f2 Bumped revision to beta 2
9fe89ff9b6 httpd: fix CPU temperature report on BCM4916
cb50c47eff Merge RT-BE92U binary blobs from 37526
789a111d63 Merge with GPL 102_37526 (RT-BE92U)
879ad023d4 webui: fix missing button to remove Offline Client List entries
c77742afb1 webui: cleanup sysdep Wireless pages that are no longer existant

 

[pershoot]

Beta 2 has been uploaded. It contains a few minor fixes, but also a newer GPL for the RT-BE92U which will address the CPU-related issues of the former GPL that was used.

...

All good here, thus far (Uptime: 0d16h32m39s). Thank you for your efforts!

 

[dave14305]

170d2e48b5 rc: Have DNS Director "Router" mode use REDIRECT target instead of DNAT to LAN IP in iptables.

So I see both DNAT and REDIRECT. REDIRECT for a client, and DNAT for the Global mode. Intended?

-A DNSFILTER -m mac --mac-source 4C:03:DE:AD:BE:EF -j REDIRECT
-A DNSFILTER -j DNAT --to-destination 192.168.1.1

 

[dave14305]

And a heads-up for Pi-Hole users that rely on DNS Director to force clients to use the Pi Hole, you need to now add the Pi-Hole IP from LAN DHCP DNS 1 as a "User defined DNS" in DNS Director and set that mode instead of Router.