What's new

Beta Asuswrt-Merlin 386.7 Beta is now available

  • 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!

Status
Not open for further replies.
This time after upgrading malicious website blocking stays off instead of turning it self on, i do not use it cos it gives false positives.
 
Went from 386.7_beta1 to 386.7_beta2,

Did the whole "Backup jffs / Flash new / Reformat jffs / Reboot / Restore jffs / Reboot" thing.

All looks good so far.
 
ax68u upgrading from 386.7_beta1 to 386.7_beta2 cause to lost of firewall - url filter entries.

maybe realated to
- FIXED: DNSFilter client list was limited to around 10 clients
on some models.

?
 
Last edited:
RT-AX86U - I assume cferom firmware for this model still in the Asus oven ??
 
RT-AX86U - I assume cferom firmware for this model still in the Asus oven ??

@RMerlin

Do you mean, is it still stripped out of the Beta as of B_2? Mine has not changed.

Or are you asking if ASUS has not finished the new code AND will it make it into the the Final 386.7?
 
AX86U + 386.7_beta2
IPoE 500Mbit + USB DUAL WAN GPRS (Failover)+ VPN Client(OPVPN 5 point+VPN Director) + VPN Server (OPVPN 1 point) + MESH + GuestNet +WIFI+ AQoS+AiProtect+DDnS+Public IP+ DNSFilter+Parrent Control.

No ipv6 anywere
No USB disk

Recommendations were successfully implemented.

Jun 18 14:44:14 kernel: nf_conntrack: automatic helper assignment is deprecated and it will be removed soon. Use the iptables CT target to attach helpers instead.
Jun 18 14:44:15 wlceventd: wlceventd_proc_event(469): eth7: Deauth_ind 00:BB:60:3E:C0:D3, status: 0, reason: Station requesting (re)association is not authenticated with responding station (9)
Jun 18 14:44:15 wlceventd: wlceventd_proc_event(486): eth7: Disassoc 00:BB:60:3E:C0:D3, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8)
Jun 18 14:44:15 hostapd: eth7: STA 00:bb:60:3e:c0:d3 IEEE 802.11: disassociated
Jun 18 14:44:18 wlceventd: wlceventd_proc_event(505): eth7: Auth 00:BB:60:3E:C0:D3, status: Successful (0)
Jun 18 14:44:18 hostapd: eth7: STA 00:bb:60:3e:c0:d3 IEEE 802.11: associated
Jun 18 14:44:18 wlceventd: wlceventd_proc_event(515): eth7: ReAssoc 00:BB:60:3E:C0:D3, status: Successful (0)
Jun 18 14:44:18 hostapd: eth7: STA 00:bb:60:3e:c0:d3 RADIUS: starting accounting session 6D52CAB0D3B47F13
Jun 18 14:44:18 hostapd: eth7: STA 00:bb:60:3e:c0:d3 WPA: pairwise key handshake completed (RSN)
Jun 18 14:44:18 kernel: ^[[0;33;41mFCACHEfc_vblog_list_add ERROR: Duplicate blog: list blog<0xffffffc02f8bc980> JOIN blog<0xffffffc02f8c44c0>^[[0m
Jun 18 14:44:18 kernel: ^[[0;33;41mFCACHEfc_vblog_list_add ERROR: Duplicate blog: list blog<0xffffffc02f8c44c0> JOIN blog<0xffffffc02f8c37c0>^[[0m
Jun 18 14:44:19 kernel: ^[[0;33;41mFCACHEfc_vblog_list_add ERROR: Duplicate blog: list blog<0xffffffc02f8a84c0> JOIN blog<0xffffffc02f8bc980>^[[0m
Jun 18 14:44:19 kernel: ^[[0;33;41mFCACHEfc_vblog_list_add ERROR: Duplicate blog: list blog<0xffffffc02f8bc980> JOIN blog<0xffffffc02f8c44c0>^[[0m
Jun 18 14:44:20 kernel: ^[[0;33;41mFCACHEfc_vblog_list_add ERROR: Duplicate blog: list blog<0xffffffc02f8a84c0> JOIN blog<0xffffffc02f8ace40>^[[0m
Jun 18 14:44:20 kernel: ^[[0;33;41mFCACHEfc_vblog_list_add ERROR: Duplicate blog: list blog<0xffffffc02f8ace40> JOIN blog<0xffffffc02f8c44c0>^[[0m

Should I be worried or is this not a problem?
 
Last edited:
Flashed my AX86U from FW 386.5_2 to FW 386.7_Beta2. Following "Backup JFFS * Flash Beta 2 * Reformat JFFS * Reboot * Restore JFFS * Reboot" with great results. All working OK. Thank You.
 
Updated RT-AX86U and erase and formated /jffs working fine. Thanks for Console spamming log removing.
Update RT-AX58U and working fine.

Tank you! @RMerlin
 
This may not be beta related but I have been getting this in the log for a while now on my AX86U. I flashed the beta to see if it was resolved, but no:

Jun 18 07:41:03 acsd: acs_candidate_score_intf(1108): eth7: intf check failed for chanspec: 0xe832 (36/160)
Jun 18 07:41:03 acsd: acs_candidate_score_bgnoise(1573): eth7: bgnoise check failed for chanspec: 0xe832 (36/160)
Jun 18 07:41:03 acsd: acs_candidate_score_txop(1831): eth7: txop check failed for chanspec: 0xe832 (36/160)
Jun 18 07:41:03 acsd: acs_candidate_score_intf(1108): eth7: intf check failed for chanspec: 0xe932 (40/160)
Jun 18 07:41:03 acsd: acs_candidate_score_bgnoise(1573): eth7: bgnoise check failed for chanspec: 0xe932 (40/160)
Jun 18 07:41:03 acsd: acs_candidate_score_txop(1831): eth7: txop check failed for chanspec: 0xe932 (40/160)
Jun 18 07:41:03 acsd: acs_candidate_score_intf(1108): eth7: intf check failed for chanspec: 0xea32 (44/160)
Jun 18 07:41:03 acsd: acs_candidate_score_bgnoise(1573): eth7: bgnoise check failed for chanspec: 0xea32 (44/160)
Jun 18 07:41:03 acsd: acs_candidate_score_txop(1831): eth7: txop check failed for chanspec: 0xea32 (44/160)
Jun 18 07:41:03 acsd: acs_candidate_score_intf(1108): eth7: intf check failed for chanspec: 0xeb32 (48/160)
Jun 18 07:41:03 acsd: acs_candidate_score_bgnoise(1573): eth7: bgnoise check failed for chanspec: 0xeb32 (48/160)
Jun 18 07:41:03 acsd: acs_candidate_score_txop(1831): eth7: txop check failed for chanspec: 0xeb32 (48/160)

Does this mean that auto channel select isn't working on 5GHz?
 
All my AX58U & AC68U Units BETA 2 Working good.
 
Updating AX88U*2 to B2.
Hope for the best!
 
Updated from beta 1 to beta 2, I get this error on my Axus AX86U
/tmp/home/root# amtm
/jffs/addons/amtm/a_fw/amtm.mod: line 627: syntax error: unterminated quoted string
this is line 627
#nano /jffs/addons/amtm/a_fw/amtm.mod

[ -z "$updcheck" ] && printf "${GN_BG}awm${NC} %-15s%-15s%${COR}s\\n\\n" "Asuswrt-Merlin" "$availRel" " ${stcol}$awmStable${NC}"
 
Updated my system- AX88U router and AiMesh Node.
Dirty flash B1 to B2.
Bit of a bumpy ride I guess, once It was up and running my WAN DHCP got suddenly disconnected, for a weird reason.
Once I did my whole- dirty upgrade to Node, then dirty upgrade to router, then system reboot- it seems quite and running.

An immediate improvement I can tell:
The syslog is now not flooded with KERNEL logs, and hopefully the clients will not disconnect further-on like in B1.
IPv6 is fetched right away once the reboot is complete, not like in B1 that I had to disable-enable for a few times.
IPv6 connected services and websites are running way more faster and smoother, for now anyway.
Will check it further on after continuous usage.

For now after 11 mins of running in B2, @RMerlin, thank you for your hard work!
 
Last edited:
Jun 18 15:39:02 dnsmasq-script[4150]: json_object_from_file: error opening file /jffs/nmp_vc_json.js: No such file or directory

saw few of these entries not sure if there from before or after beta 1 on beta 2 now
Probably after i do not have entries i think from before beta 2

AX88U btw
 
Last edited:
Put on some popcorn in the microwave. That might do it, tho here I have a Roomba parked right next to my microwave, and it still keeps its 2.4 GHz connection to the router at the other end of the apartment :)
LOL! My Nest Cameras (all 2.4GHz) go wonky when we make popcorn... sigh...
 
Asuswrt-Merlin 386.7 Beta is now available for all supported models. This release focuses on GPL merges and component updates.

June 17th: Beta 2 has now been uploaded. Make sure you read the following note!
Changes since beta 1:
Code:
89778ae369 Updated documentation
5e7fd8632e rc: fix re-enabling wifi LEDs on the RT-AX86S
8fe761e94a HND5.02L07p2: replace dhd with build without debug enabled for RT-AX86U and GT-AXE11000
3605922c04 webui: change notification message shown if trying to enable AuraRGB while LEDs are disabled
0a54a8cf57 rc: don't re-enable AuraRGB when toggling LED stealth mode if it was previously disabled; remove dead code from setup_leds()
626bf4f117 HND5.02L07p2: fix mtd partition layout
45f552f233 httpd: fix wireless client log issue with guests (issue introduced with 67be92ce6b)
e8e525fd13 Bump version to beta 2


The highlights:
  • Merged with GPL 386_49335 (for the RT-AC5300) and 386_48966 (for all other models).
  • DNSFilter can now also intercept and redirect IPv6 DNS queries on HND models. You can also specify IPv6 DNS servers for the three custom settings.
  • Component updates: openssl 1.1.1o, haveged 1.9.18, openvpn 2.5.7 and tor 0.4.7.7.
  • Fixed CVE-2022-0934 and CVE-2022-26376.
  • And a few other fixes

Also for those not using a GT-AX6000 or XT12, this also includes the changes from 386.6, such as the improved IPv6 support for OpenVPN servers. Please review the 386.6 changelog for mode details.

Things in particular need of testing in this release:
  • DNSFilter and IPv6 support (also ensure no regression on older models)
  • IPv6 support with the OpenVPN server

Please keep the discussion on this particular release. Off-topic posts will be moved, deleted or ignored depending on my mood at the time.

Downloads are here.
Changelog is here.
Upgraded my RT-AC5300 from 386.7 B1 to B2. All seems OK except for the VPN Server - OpenVPN web page for configuring the server. There appear to be a number of errors on the web page, no apply button, nothing happens when you switch VPN Details from General to Advanced Settings in the dropdown etc. as per attached screenshot. Unfortunately didn't test if the same issue was on B1 version as well.
 

Attachments

  • Open_VPN_Config_Error.PNG
    Open_VPN_Config_Error.PNG
    61.9 KB · Views: 76
Well that is odd. Like super odd
My VOIP adaptor gone crazy for the last few days, and I had no idea why.
For no reason, it is just lost connection to my VOIP supplier on B1- and I thought that my adaptor is dead.
Thankfully, The B2 solved that as well- it is back to life like nothing happened.

LOL, thank you again @RMerlin!
 
Something's abnormal with your setup if your RT-AC68U lost its JFFS content.

As for DDNS, from what I remember other people wrote to you earlier in the thread that the Go link was normal when using DNS-o-Matic.
I'd not updated my profile to AX86u but did mention it in the original post. It used to show my domain prior to this beta.
 
Any other known memory hoarders?
Not that I can think of, unless you run something that generates a lot of logging in /tmp.

The last 4 updates to the software have prevented accessing the modem through the router at address: 192.168.100.1
Could be the ISP securing the modem to prevent access from a different subnet, in the light of the security issues that affected various modems a few months ago.
 
Status
Not open for further replies.

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