What's new

Release Asuswrt-Merlin 386.7 is now available for all models

  • 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.
You’re probably being delegated a /48 (check /tmp/wan0_bound6.env for PREFIXES=). But the firmware is hardcoding a /64 when assigning a prefix length to br0.

Hardcoded /64 into ipv6_prefix_length:

Adding IPv6 address with ipv6_prefix_length:
This was changed by a patch submitted by @Tvlz . You'll have to ask him why the LAN preset is now hardcoded to /64.
 
Just updated my trusted AC3100 to 386.7 all good. Thanks Eric. :)
 
upgraded a brand new ax86u from stock to merlinware - life's good!
  • nas smbv2 (ssd on usb)
  • <25 clients (ac, n, g) and as a result -
    • 160mhz is off
    • 2.4g set as legacy (for one pia device)
  • nordvpn (very fast but persnickety)
i had a unique problem using win 10's file explorer as it would list the nas hostname but was unable to resolve its address. if the nordvpn app was running (enabled or not), the hostname would just not resolve. the fix was in updating the hosts file with the nas hostname and voila! many thanks to eibgrad for his help there.

my ac86u has now been retired and i will surely miss its reliability. it was a late 2017 - early '18 model and solid as a rock for my limited soho use. merlinware made it much more useful -

to eric, i'm eternally grateful for your dedication and expertise.​

the ax86u seems to have a similar range as the somewhat deprecated ac86u but is significantly faster on the wireless lan/intranet when hosting nas traffic. so, we'll just have to see.

. . . long live the king!
 
AX58U

Anyone else notice AiProtection isn't logging malicious site blocks now? It was working in Beta 2, but now I'm not seeing anything logged in AiProtection. I tested that the feature is working, the blocked events show up in the system log, but not on the AiProtection tab.
 
Bit the bullet, upgraded my RT-AX68U today. No issues, Wifi working great. Though I am an access point mode user so not using about half the router's features.
 
I upgraded my RT-AC68U from 386.5_2 to 386.7 and it's going down every 4-5 hours. The basic errors are:

Code:
Jun 25 06:07:06 kernel: dhcpc_lease/12170: potentially unexpected fatal signal 11.
Jun 25 06:07:06 kernel: Pid: 12170, comm:          dhcpc_lease
Jun 25 06:07:06 kernel: CPU: 0    Tainted: P             (2.6.36.4brcmarm #1)
Jun 25 06:07:06 kernel: PC is at 0x4017b8e0
Jun 25 06:07:06 kernel: LR is at 0x401bd600
Jun 25 06:07:06 kernel: pc : [<4017b8e0>]    lr : [<401bd600>]    psr: 60000010
Jun 25 06:07:06 kernel: sp : bef16c18  ip : 401d3518  fp : bef16c58
Jun 25 06:07:06 kernel: r10: 00000000  r9 : 00085bb8  r8 : 00086426
Jun 25 06:07:06 kernel: r7 : 0000000b  r6 : 00086417  r5 : 00086818  r4 : bef16c74
Jun 25 06:07:06 kernel: r3 : 401d8408  r2 : 000aba50  r1 : bef16c28  r0 : fffffff4
Jun 25 06:07:06 kernel: Flags: nZCv  IRQs on  FIQs on  Mode USER_32  ISA ARM  Segment user
Jun 25 06:07:06 kernel: Control: 10c53c7d  Table: 9a99c04a  DAC: 00000015

Jun 25 06:10:22 dropbear[1093]: Error forking: Cannot allocate memory

Jun 25 06:13:53 check_watchdog: [check_watchdog] restart watchdog for no heartbeat
Jun 25 06:13:53 rc_service: check_watchdog 983:notify_rc restart_watchdog
Jun 25 06:14:00 crond[12284]: can't execute '/bin/sh' for user admin

Jun 25 06:28:56 dnsmasq-dhcp[960]: failed to write /var/lib/misc/dnsmasq.leases: No space left on device (retry in 60 s)
Jun 25 06:29:53 check_watchdog: [check_watchdog] restart watchdog for no heartbeat
Jun 25 06:29:53 rc_service: check_watchdog 983:notify_rc restart_watchdog

This was happening periodically on 386.5_2, like every 3 days or so, but now it's so often it's unusable.

This is with a basic setup and most things disabled (HW acceleration on, Adaptive QoS off, AiProtection off, no customizations). It seems to go OOM. I have no swap configured.

This only way to fix this is to hard reboot the router physically (it's impossible to access it remotely in this state). After a reboot:

NVRAM usage 57201 / 65536 bytes
JFFS 4.17 / 62.75 MB

Typically have ~14 clients on the WiFi, no IoT or anything crazy. I do have AiMesh tho with 1 other RT-AC68U node.

Going to try to downgrade the firmware back. Don't really have time to fiddle with this stuff at the moment.
 
Trying to update GT-AX11000 from 386.5_2 to 386.7 (double checked and I have downloaded the correct firmware)

When I upload the 386.7 firmware it shows: "Please wait, Applying settings" and then logs out

I have re-logged in several times but this keeps happening. Tried rebooting too and same result.

Anyone else experiencing this or knows how to resolve it?
 
Last edited:
Use a different browser, or try using yours with all extensions disabled (aka 'safe mode').
 
I have a GT-AXE11000 as main router and couple of XT8 and ET8 on mesh, and just upgraded to 386.7. Wireless connectivity has been slower and couldn't reach 100mbps. Had to roll back to 386.5_2, and now phones are getting 300+ mbps. Love the stability of 386.5_2, so sticking to this for now. Also, I noticed Cloudflare was missing from fast DNS. I had to manually type the DNS (1111/1001) on 386.7. Thanks!
 
Was the patch discussed anywhere besides the commit? I can see where a /64 is the smallest you would assign, but why not larger?
No. It was submitted over PM, and since IPv6 isn't my area of expertise I can't properly review it in depth, so I trusted him on it. actually sat on it for a few months as initially I wasn't too keen on merging IPv6 changes that I can't personally test or review properly.

Jun 25 06:10:22 dropbear[1093]: Error forking: Cannot allocate memory
Something on your setup must be causing these out of memory errors.
 
No. It was submitted over PM, and since IPv6 isn't my area of expertise I can't properly review it in depth, so I trusted him on it. actually sat on it for a few months as initially I wasn't too keen on merging IPv6 changes that I can't personally test or review properly.


Something on your setup must be causing these out of memory errors.

What setup? It's literally a vanilla install with most stuff disabled and 1 aimesh node. This has been going on for months but never as bad as 386.7. I mentioned it many times, like here in January:

Merlin 386.4 on RT-AC68U no space left with kernel errors every week | SmallNetBuilder Forums (snbforums.com)

It all seemed to start with 386. Never had this issue prior to that with the same setup on the same hardware.

I downgraded to 386.5_2 and it's back to the way it was before, at least so far the last 6 hours.
 
Clean Flash all seems well..... except for logs full of this ?


Code:
Jun 25 17:48:10 kernel: ^[[0;33;41mFCACHEfc_vblog_list_add ERROR: Duplicate blog: list blog<0xffffffc02f8c8980> JOIN blog<0xffffffc02f8b6e40>^[[0m
Jun 25 18:00:06 kernel: ^[[0;33;41mFCACHEfc_vblog_list_add ERROR: Duplicate blog: list blog<0xffffffc02f8c2980> JOIN blog<0xffffffc02f8a04c0>^[[0m
Jun 25 18:00:11 kernel: ^[[0;33;41mFCACHEfc_vblog_list_add ERROR: Duplicate blog: list blog<0xffffffc02f8aa4c0> JOIN blog<0xffffffc02f8a8000>^[[0m
Jun 25 18:08:13 kernel: ^[[0;33;41mFCACHEfc_vblog_list_add ERROR: Duplicate blog: list blog<0xffffffc02f8b0980> JOIN blog<0xffffffc02f8df7c0>^[[0m
Jun 25 18:08:13 kernel: ^[[0;33;41mFCACHEfc_vblog_list_add ERROR: Duplicate blog: list blog<0xffffffc02f8df7c0> JOIN blog<0xffffffc02f894980>^[[0m
Jun 25 18:08:50 kernel: ^[[0;33;41mFCACHEfc_vblog_list_add ERROR: Duplicate blog: list blog<0xffffffc02f8ae000> JOIN blog<0xffffffc02f8db300>^[[0m
Jun 25 18:21:16 kernel: ^[[0;33;41mFCACHEfc_vblog_list_add ERROR: Duplicate blog: list blog<0xffffffc02f8c9300> JOIN blog<0xffffffc02f89a000>^[[0m
Jun 25 18:21:16 kernel: ^[[0;33;41mFCACHEfc_vblog_list_add ERROR: Duplicate blog: list blog<0xffffffc02f89a000> JOIN blog<0xffffffc02f8e04c0>^[[0m
Jun 25 18:34:11 kernel: ^[[0;33;41mFCACHEfc_vblog_list_add ERROR: Duplicate blog: list blog<0xffffffc02f8de980> JOIN blog<0xffffffc02f8ca000>^[[0m
Jun 25 18:34:11 kernel: ^[[0;33;41mFCACHEfc_vblog_list_add ERROR: Duplicate blog: list blog<0xffffffc02f8ca000> JOIN blog<0xffffffc02f898980>^[[0m
Jun 25 18:36:51 kernel: ^[[0;33;41mFCACHEfc_vblog_list_add ERROR: Duplicate blog: list blog<0xffffffc02f8df300> JOIN blog<0xffffffc02f8a2e40>^[[0m
Jun 25 18:36:51 kernel: ^[[0;33;41mFCACHEfc_vblog_list_add ERROR: Duplicate blog: list blog<0xffffffc02f8a2e40> JOIN blog<0xffffffc02f8b6980>^[[0m
Jun 25 18:57:11 kernel: ^[[0;33;41mFCACHEfc_vblog_list_add ERROR: Duplicate blog: list blog<0xffffffc02f8d9300> JOIN blog<0xffffffc02f89f300>^[[0m
Jun 25 18:57:11 kernel: ^[[0;33;41mFCACHEfc_vblog_list_add ERROR: Duplicate blog: list blog<0xffffffc02f89f300> JOIN blog<0xffffffc02f89c980>^[[0m
Jun 25 19:00:12 kernel: ^[[0;33;41mFCACHEfc_vblog_list_add ERROR: Duplicate blog: list blog<0xffffffc02f8cb300> JOIN blog<0xffffffc02f8c64c0>^[[0m
Jun 25 19:00:12 kernel: ^[[0;33;41mFCACHEfc_vblog_list_add ERROR: Duplicate blog: list blog<0xffffffc02f8c64c0> JOIN blog<0xffffffc02f8bce40>^[[0m
Jun 25 19:05:30 kernel: ^[[0;33;41mFCACHEfc_vblog_list_add ERROR: Duplicate blog: list blog<0xffffffc02f8b6e40> JOIN blog<0xffffffc02f8a04c0>^[[0m
Jun 25 19:13:44 kernel: ^[[0;33;41mFCACHEfc_vblog_list_add ERROR: Duplicate blog: list blog<0xffffffc02f8df7c0> JOIN blog<0xffffffc02f8ae000>^[[0m
Jun 25 19:13:44 kernel: ^[[0;33;41mFCACHEfc_vblog_list_add ERROR: Duplicate blog: list blog<0xffffffc02f8b9300> JOIN blog<0xffffffc02f8ba980>^[[0m
Jun 25 19:23:50 kernel: ^[[0;33;41mFCACHEfc_vblog_list_add ERROR: Duplicate blog: list blog<0xffffffc02f8a5300> JOIN blog<0xffffffc02f8c44c0>^[[0m
Jun 25 19:23:50 kernel: ^[[0;33;41mFCACHEfc_vblog_list_add ERROR: Duplicate blog: list blog<0xffffffc02f8c44c0> JOIN blog<0xffffffc02f8a9300>^[[0m
Jun 25 19:59:31 kernel: ^[[0;33;41mFCACHEfc_vblog_list_add ERROR: Duplicate blog: list blog<0xffffffc02f8a6e40> JOIN blog<0xffffffc02f8ac980>^[[0m
Jun 25 19:59:31 kernel: ^[[0;33;41mFCACHEfc_vblog_list_add ERROR: Duplicate blog: list blog<0xffffffc02f8ac980> JOIN blog<0xffffffc02f88c4c0>^[[0m
Jun 25 20:03:51 kernel: ^[[0;33;41mFCACHEfc_vblog_list_add ERROR: Duplicate blog: list blog<0xffffffc02f884000> JOIN blog<0xffffffc02f8ac980>^[[0m
Jun 25 20:03:51 kernel: ^[[0;33;41mFCACHEfc_vblog_list_add ERROR: Duplicate blog: list blog<0xffffffc02f8ac980> JOIN blog<0xffffffc02f8a0e40>^[[0m
Jun 25 20:07:30 kernel: ^[[0;33;41mFCACHEfc_vblog_list_add ERROR: Duplicate blog: list blog<0xffffffc02f8917c0> JOIN blog<0xffffffc02f899300>^[[0m
Jun 25 20:17:54 kernel: ^[[0;33;41mFCACHEfc_vblog_list_add ERROR: Duplicate blog: list blog<0xffffffc02f8c04c0> JOIN blog<0xffffffc02f8c44c0>^[[0m
Jun 25 20:17:54 kernel: ^[[0;33;41mFCACHEfc_vblog_list_add ERROR: Duplicate blog: list blog<0xffffffc02f8c44c0> JOIN blog<0xffffffc02f8b24c0>^[[0m
Jun 25 20:21:50 kernel: ^[[0;33;41mFCACHEfc_vblog_list_add ERROR: Duplicate blog: list blog<0xffffffc02f88ae40> JOIN blog<0xffffffc02f896000>^[[0m
Jun 25 20:28:14 kernel: ^[[0;33;41mFCACHEfc_vblog_list_add ERROR: Duplicate blog: list blog<0xffffffc02f8ce980> JOIN blog<0xffffffc02f885300>^[[0m
Jun 25 20:28:14 kernel: ^[[0;33;41mFCACHEfc_vblog_list_add ERROR: Duplicate blog: list blog<0xffffffc02f885300> JOIN blog<0xffffffc02f87b7c0>^[[0m
Jun 25 20:43:50 kernel: ^[[0;33;41mFCACHEfc_vblog_list_add ERROR: Duplicate blog: list blog<0xffffffc02f8a9300> JOIN blog<0xffffffc02f8ad7c0>^[[0m
Jun 25 20:56:30 kernel: ^[[0;33;41mFCACHEfc_vblog_list_add ERROR: Duplicate blog: list blog<0xffffffc02f8be980> JOIN blog<0xffffffc02f87c980>^[[0m
Jun 25 21:00:16 kernel: ^[[0;33;41mFCACHEfc_vblog_list_add ERROR: Duplicate blog: list blog<0xffffffc02f8c8980> JOIN blog<0xffffffc02f8b77c0>^[[0m
Jun 25 21:00:16 kernel: ^[[0;33;41mFCACHEfc_vblog_list_add ERROR: Duplicate blog: list blog<0xffffffc02f8b77c0> JOIN blog<0xffffffc02f87c980>^[[0m
Jun 25 21:02:10 kernel: ^[[0;33;41mFCACHEfc_vblog_list_add ERROR: Duplicate blog: list blog<0xffffffc02f8de980> JOIN blog<0xffffffc02f88c980>^[[0m
Jun 25 21:10:10 kernel: ^[[0;33;41mFCACHEfc_vblog_list_add ERROR: Duplicate blog: list blog<0xffffffc02f895300> JOIN blog<0xffffffc02f8ab7c0>^[[0m
Jun 25 21:14:31 kernel: ^[[0;33;41mFCACHEfc_vblog_list_add ERROR: Duplicate blog: list blog<0xffffffc02f8b4980> JOIN blog<0xffffffc02f8964c0>^[[0m
Jun 25 21:14:31 kernel: ^[[0;33;41mFCACHEfc_vblog_list_add ERROR: Duplicate blog: list blog<0xffffffc02f8964c0> JOIN blog<0xffffffc02f886000>^[[0m
Jun 25 21:23:50 kernel: ^[[0;33;41mFCACHEfc_vblog_list_add ERROR: Duplicate blog: list blog<0xffffffc02f89e980> JOIN blog<0xffffffc02f8ab300>^[[0m
Jun 25 21:26:16 kernel: ^[[0;33;41mFCACHEfc_vblog_list_add ERROR: Duplicate blog: list blog<0xffffffc02f8e3300> JOIN blog<0xffffffc02f8a0000>^[[0m
Jun 25 21:26:16 kernel: ^[[0;33;41mFCACHEfc_vblog_list_add ERROR: Duplicate blog: list blog<0xffffffc02f8a0000> JOIN blog<0xffffffc02f8944c0>^[[0m
 
No. It was submitted over PM, and since IPv6 isn't my area of expertise I can't properly review it in depth, so I trusted him on it. actually sat on it for a few months as initially I wasn't too keen on merging IPv6 changes that I can't personally test or review properly.
@Tvlz must have had plans to manually assign other IPv6 subnets from the larger prefix, because even dnsmasq is told to only advertise a hard-coded 64 via stateless RAs:


Hopefully he can chime in with his design for this change. Or she.
 
Last edited:
Update from Beta 2, like on the other Betas:

Jun 24 23:20:41 kernel: CFG80211-ERROR) wl_cfg80211_hostapd_sec : No WPSIE in beacon
Jun 25 08:24:18 kernel: CFG80211-ERROR) wl_cfg80211_change_station : WLC_SCB_AUTHORIZE sta_flags_mask not set

Didnt see any Thread about WPSIE (beacon) Error on the snbforums, maybe someone could explain this to me if its normal ?

all 3 RT-AX88U working smooth since 2 Days :)

Temps at 2.4 GHz: 41°C - 5 GHz: 44°C - CPU: 60°C on a hot Day.
Buffers shows always 0.00 MB -> Standard or something wrong ?

Edit:
Just found something about a Bruteforce WPS Attack wich can be found from Beacon
hXXps://jjnetworkexpert.blogspot.com/2017/01/what-is-wps-and.html after a quick search.
Last time i had this Error was on 386.5.
 
Last edited:
@Tvlz must have had plans to manually assign other IPv6 subnets from the larger prefix, because even dnsmasq is told to only advertise a hard-coded 64 via stateless RAs:


Hopefully he can chime in with his design for this change. Or she.

Is that eventually possible to revert this change back and having the full functionality of /48 bit prefix, in case your ISP provide it?
 
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