Menu
What's new
By:
Filters Better Search

Beta Asuswrt-Merlin 386.4 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.
I updated a RT-AX58U at my holiday house from Stock 3.0.0.4.386.45898 to 386.4 Beta 1. All seems to be good, but I now can't connect to the VPN Server.Oh well, I'll fix it when I'm down at the house again later in the week :)
 
RT-AC68U doesn't like a factory reset with this Beta. Trying to re-add my second AC68U in mesh fails. Had to update to Asus firmware to get it to work. Works fine from a dirty flash but not WPS reset.
 
5stringdeath said:
My DDNS (google) has a big yellow exclamation point (!) as if there is an error, however it is working just fine and my internal routing resolves fine.
Click to expand...
Ok now its stopped working .. my IP is not updating in my Google domains page any longer. So is it just broken with IPV6? I have FiOS and native IPV6 has been supported (and working) for a few years :-/
 
Yota said:
I am very happy to see that Asuswrt-Merlin finally supports IPv6 on ovpn. I think your ISP now officially supports IPv6? @RMerlin ;)

edit:
:confused:Sorry i didn't see this

I am very grateful for the addition of this feature, I can expect this will be the best new feature of 386_4.
Click to expand...
Don't expect much yet, the things that need testing are if you can reach (or ping ) devices on your home network over ipv6. Note that this does not route ipv6 internet traffic. Don't expect to go to eg. test-ipv6.com and expect to have a working routable ipv6 internet connection coming from your openvpn tunnel. The ip6tables of asuswrt are still very limited including what is enabled at the kernel level for ipv6. At best, you can reach your ipv6 home network through the tunnel.
 
Dirty upgrade to 386.4_beta1 on both router and access point after 142 days on 386.3. About 48 hours in and nothing to report except that everything's working and stable.
 
umd325 said:
Going from 386.3 to 386.4 beta on two AC68Us, the 'disable LEDs' setting seems to only be working with power, wifi, and usb LEDS. The lan and wan LEDs remain on.
Click to expand...
Thanks. "et" userspace tool is missing, so the router fails to set the switch registers.
 
Code: 
Dec 18 17:38:38 kernel: Init chrdev /dev/idp with major 190
Dec 18 17:38:38 kernel: tdts: tcp_conn_max = 8000
Dec 18 17:38:38 kernel: tdts: tcp_conn_timeout = 300 sec
Dec 18 17:38:39 kernel: SHN Release Version: 2.0.1 8279cad
Dec 18 17:38:39 kernel: UDB Core Version: 0.2.20
Dec 18 17:38:39 kernel: Init chrdev /dev/idpfw with major 191
Dec 18 17:38:39 kernel: IDPfw: flush fc
Dec 18 17:38:39 kernel: IDPfw: IDPfw is ready
Dec 18 17:38:39 kernel: sizeof forward pkt param = 280
Dec 18 17:38:39 BWDPI: fun bitmap = 3
Dec 18 17:38:51 BWDPI: force to flush flowcache entries
Dec 18 17:38:51 kernel: IDPfw: Exit IDPfw
Dec 18 17:38:51 kernel: mod epilog takes 0 jiffies
Dec 18 17:38:51 kernel: IDPfw: Exit IDPfw
Dec 18 17:38:51 kernel: Exit chrdev /dev/idpfw with major 191
Dec 18 17:38:51 kernel: Exit chrdev /dev/idp with major 190
Dec 18 17:38:51 BWDPI: rollback fc

major 190/191 -> issue ?
 
Last edited:
SomeWhereOverTheRainBow said:
Don't expect much yet, the things that need testing are if you can reach (or ping ) devices on your home network over ipv6. Note that this does not route ipv6 internet traffic. Don't expect to go to eg. test-ipv6.com and expect to have a working routable ipv6 internet connection coming from your openvpn tunnel. The ip6tables of asuswrt are still very limited including what is enabled at the kernel level for ipv6. At best, you can reach your ipv6 home network through the tunnel.
Click to expand...
In fact, my needs are is simple, connecting to my home network through an IPv6 tunnel is all my needs.
www.snbforums.com

How to prevent LAN devices from obtaining IPv6 addresses?

A long time ago, I liked public IPv4 addresses, so my router had a unique IP address, and I could connect to my OpenVPN server from anywhere. but about 3 years ago, my ISP stopped providing public IPv4 addresses. They used a technology called CGNAT to save their IPv4 resources. Instead, they...
www.snbforums.com www.snbforums.com
 
Paul Smedley said:
I updated a RT-AX58U at my holiday house from Stock 3.0.0.4.386.45898 to 386.4 Beta 1. All seems to be good, but I now can't connect to the VPN Server.Oh well, I'll fix it when I'm down at the house again later in the week :)
Click to expand...
With what are trying to connect to the router vpn server? Openvpn on Android?

Can you, if it's available, post the connection log?
 
RMerlin said:
DDNS update issues if IPv6 is enabled (received a series of patches from Asus, need to merge and test for beta 2)
Click to expand...
A hypothetical problem, I haven't tested it, but it may be a problem.

I have CGNAT, and the IPv4 address provided to me by the ISP is 100.64.0.0/10. In the router, it does not follow RFC6598 and regards it as a reserved address, so the router considers this to be a “real” public IP and registers DDNS for it.

When I have a public IPv6 address, I assume that DDNS will register two addresses at the same time, one is the IPv4 CGNAT reserved address, and the other is the IPv6 public IP address. The problem is that the client will connect to a non-existent IPv4 address after resolving DNS. So is there a way to allow only IPv6 registration on the DDNS page?
 
ColinTaylor said:
Rebooting the router erases (or overwrites) the current System Log file (/jffs/syslog).

Once rebooted the System Log - General Log does not prepend the previous log file (/jffs/syslog-1) to the output shown in the GUI. Manually restarting the logger (service restart_logger) causes the previous log file to appear in the GUI.
Click to expand...
Works for me, on two different routers.
 
RMerlin said:
Works for me, on two different routers.
Click to expand...
I'm using an RT-AX86U. I've probably rebooted a dozen times to try and determine what the problem is but the results are always the same.

In the past the first entry in the log would be syslogd started: BusyBox v1.25.1 but I'm not seeing that anymore. This is the start of the syslog. (Notice the date, it doesn't change to May 5 until a bit later in the log)
Code: 
Jan  1 00:00:02 kernel: ubi2: attaching mtd10
Jan  1 00:00:02 kernel: ubi2: scanning is finished
Jan  1 00:00:02 kernel: ubi2: attached mtd10 (name "misc1", size 8 MiB)
Jan  1 00:00:02 kernel: ubi2: PEB size: 131072 bytes (128 KiB), LEB size: 126976 bytes
Jan  1 00:00:02 kernel: ubi2: min./max. I/O unit sizes: 2048/2048, sub-page size 2048
Jan  1 00:00:02 kernel: ubi2: VID header offset: 2048 (aligned 2048), data offset: 4096
Jan  1 00:00:02 kernel: ubi2: good PEBs: 64, bad PEBs: 0, corrupted PEBs: 0
Jan  1 00:00:02 kernel: ubi2: user volume: 1, internal volumes: 1, max. volumes count: 128
Jan  1 00:00:02 kernel: ubi2: max/mean erase counter: 24/8, WL threshold: 4096, image sequence number: 1725884149
Jan  1 00:00:02 kernel: ubi2: available PEBs: 0, total reserved PEBs: 64, PEBs reserved for bad PEB handling: 4
Jan  1 00:00:02 kernel: ubi2: background thread "ubi_bgt2d" started, PID 411
Jan  1 00:00:03 kernel: UBIFS (ubi2:0): background thread "ubifs_bgt2_0" started, PID 426
Jan  1 00:00:03 kernel: UBIFS (ubi2:0): UBIFS: mounted UBI device 2, volume 0, name "nvram"
Jan  1 00:00:03 kernel: UBIFS (ubi2:0): LEB size: 126976 bytes (124 KiB), min./max. I/O unit sizes: 2048 bytes/2048 bytes
Jan  1 00:00:03 kernel: UBIFS (ubi2:0): FS size: 5840896 bytes (5 MiB, 46 LEBs), journal size 1396736 bytes (1 MiB, 11 LEBs)
Jan  1 00:00:03 kernel: UBIFS (ubi2:0): reserved for root: 0 bytes (0 KiB)
Jan  1 00:00:03 kernel: UBIFS (ubi2:0): media format: w4/r0 (latest is w4/r0), UUID 4B2A44DD-417E-46D8-97CE-24D278768884, small LPT model
Jan  1 00:00:03 kernel: UBIFS (ubi2:0): un-mount UBI device 2
Jan  1 00:00:03 kernel: UBIFS (ubi2:0): background thread "ubifs_bgt2_0" stops
Jan  1 00:00:03 kernel: ubi2: detaching mtd10
Jan  1 00:00:03 kernel: ubi2: mtd10 is detached
Jan  1 00:00:03 kernel: init (1): drop_caches: 1
Jan  1 00:00:03 get_ext_phy_id: 0/1/0/0
Jan  1 00:00:03 jffs2: getting the information of jffs2
Jan  1 00:00:03 jffs2: mounting jffs2
Jan  1 00:00:05 init: notice[jffs]: Loaded
Jan  1 00:00:05 jffs2: create jffs2 successfully
Jan  1 00:00:05 kernel: Loading HND Module
Jan  1 00:00:05 kernel: IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
Jan  1 00:00:05 kernel: IPv6: ADDRCONF(NETDEV_UP): eth5: link is not ready
Jan  1 00:00:06 kernel: igs_module_init:867:     IGS 29 create network socket successful
Jan  1 00:00:06 kernel: cfg80211: Calling CRDA to update world regulatory domain
Jan  1 00:00:06 kernel: dpsta_init: 17.10.157.2802 (r794271) cf953dc Jan 12 2021 15:19:57 msglevel 0x1
Jan  1 00:00:06 kernel: osl_skb_audit: PASS
Jan  1 00:00:06 kernel: wl_module_init: passivemode set to 0x1
Jan  1 00:00:06 kernel: wl_module_init: txworkq set to 0x0
Jan  1 00:00:06 kernel: ^[[0;32mwl_pktfwd_sys_init:  ^[[1m^[[34mWL_PKTFWD[1.1.0]^[[0m Success^[[0m
Jan  1 00:00:06 kernel: wl 0001:01:00.0: enabling device (0000 -> 0002)
Jan  1 00:00:06 kernel: wl0: creating kthread wl0-kthrd
Jan  1 00:00:06 kernel: BME Service Initialization
Jan  1 00:00:06 kernel: BME: M2M Core id 0x844 rev 129
Jan  1 00:00:06 kernel: M2M Service Initialization: M2M_DD_ENAB 0x00000003
Jan  1 00:00:06 kernel: M2M: M2M Core id 0x844 rev 129
Jan  1 00:00:06 kernel: M2M: SUCCESS eng 0 alloc rings <ffffffc03252e000,ffffffc02fc6a000>,ffffffc02ea77000 depth 256
Jan  1 00:00:06 kernel: M2M: SUCCESS eng 1 alloc rings <ffffffc032a74000,ffffffc0329aa000>,ffffffc02ea76000 depth 256
Jan  1 00:00:06 kernel: M2M: DMA 0 IntRcvLazy 01000000
Jan  1 00:00:06 kernel: M2M: DMA 0 RcvCtrl XmtCtrl enabled
Jan  1 00:00:06 kernel: M2M: DMA 1 IntRcvLazy 01000000
Jan  1 00:00:06 kernel: M2M: DMA 1 RcvCtrl XmtCtrl enabled
Jan  1 00:00:06 kernel: wl0: phy_radio_attach: RF Band Cap: 2G:1 5G:1
Jan  1 00:00:07 kernel: BME:register key<1010802> user RLM sel IDX set 1 mem 2 8 hi 0 0
Jan  1 00:00:07 kernel: wl0 taf_do_enable: TAF is enabled
Jan  1 00:00:07 kernel: CSIMON module registered
Jan  1 00:00:07 kernel: wfd0-thrd WL 0 FLowControl total<45756> lo<11439> hi<4575> favor prio<4>
Jan  1 00:00:07 kernel: ^[[0;31mwfd_bind: wfd0-thrd initialized pktlists: radio 0 nodes 1032 xfer wl_pktfwd_xfer_callback+0x0/0x3f0 [wl]
Jan  1 00:00:07 kernel: ^[[0m
Jan  1 00:00:07 kernel: Creating CPU ring for queue number 0 with 1024 packets descriptor=0xffffffbffc5c02c0
Jan  1 00:00:07 kernel:  Creating CPU ring for queue number 1 with 1024 packets descriptor=0xffffffbffc5c0300
Jan  1 00:00:07 kernel:  ^[[1m^[[34m wfd_bind: Dev eth%d wfd_idx 0 wl_radio_idx 0 Type skb:sll configured WFD thread wfd0-thrd minQId/maxQId (8/9), status (0) qmask 0x3^[[0m
Jan  1 00:00:07 kernel: Instantiating WFD 0 thread
Jan  1 00:00:07 kernel: ^[[0;32mwl_wfd_bind: wl0 wfd_idx 0 success^[[0m
Jan  1 00:00:07 kernel: wfd_registerdevice Successfully registered dev eth6 ifidx 0 wfd_idx 0
Jan  1 00:00:07 kernel: eth6: Broadcom BCM6710 802.11 Wireless Controller 17.10.157.2803 (r795020)
Jan  1 00:00:07 kernel: DHD_FKB_POOL size is:1280 and entry size:2816
Jan  1 00:00:07 kernel: DHD_PKTTAG POOL size is:2592 and entry size:128
Jan  1 00:00:07 kernel: ^[[0;32mdhd_pktfwd_sys_init:  ^[[1m^[[34mdhd_PKTFWD[1.0.0]^[[0m Success^[[0m
Jan  1 00:00:07 kernel: PCI_PROBE:  bus 1, slot 0,vendor 14E4, device AAA4(good PCI location)
Jan  1 00:00:07 kernel: pcieh 0000:01:00.0: enabling device (0000 -> 0002)
Jan  1 00:00:07 kernel: dor1: runner supported ring format types TxP 0x5, RxP 0x3 TxC 0x3 RxC 0x3^M
Jan  1 00:00:07 kernel: dhd_runner_attach: Tx Offload - Enabled, Ring Size = 1024
Jan  1 00:00:07 kernel: dhd_runner_attach: Rx Offload - Enabled, Ring Size = 1024
Jan  1 00:00:07 kernel: TX wakeup info: reg = <0x82299004>, val = <0x11000000>
Jan  1 00:00:07 kernel: RX wakeup info: reg = <0x8229a004>, val = <0x29000000>
Jan  1 00:00:07 kernel: CFG80211-ERROR) wl_setup_wiphy : Registering Vendor80211
Jan  1 00:00:07 kernel: dhd_attach(): thread:dhd_watchdog_thread:313 started
Jan  1 00:00:07 kernel: ^[[0;31mwfd_bind: wfd1-thrd initialized pktlists: radio 1 nodes 1032 xfer dhd_pktfwd_xfer_callback+0x0/0x798 [dhd]
Jan  1 00:00:07 kernel: ^[[0m
Jan  1 00:00:07 kernel: Creating CPU ring for queue number 2 with 1024 packets descriptor=0xffffffbffc5c0340
Jan  1 00:00:07 kernel:  Creating CPU ring for queue number 3 with 1024 packets descriptor=0xffffffbffc5c0380
Jan  1 00:00:07 kernel:  ^[[1m^[[34m wfd_bind: Dev eth%d wfd_idx 1 wl_radio_idx 1 Type fkb:sll configured WFD thread wfd1-thrd minQId/maxQId (10/11), status (0) qmask 0xc^[[0m
Jan  1 00:00:07 kernel: ^[[0;32mdhd_wfd_bind: wl1 wfd_idx 1 success^[[0m
Jan  1 00:00:07 kernel: Instantiating WFD 1 thread
Jan  1 00:00:08 kernel: dor1: MSG Ring format set to 1
Jan  1 00:00:08 kernel: dhd_runner_flowmgr_init: dhd1_rnr bootmem addr<ffffffc00a900000> size<11534336>
Jan  1 00:00:08 kernel: dhd_runner_profile_init: profile = 3 1024/0512 2048/1024 1024/0512 0512/0512 0512/0512
Jan  1 00:00:08 kernel: ^[[0;33;40mRunner DHD PCIE: vendor<0x14e4> device<0xaaa4> bus<1> slot<0>^[[0m
Jan  1 00:00:08 kernel: Initial configuration
Jan  1 00:00:08 kernel: =================================
Jan  1 00:00:08 kernel:     rx_post_flow_ring_base_addr : ffffffc02dcb2000
Jan  1 00:00:08 kernel:     tx_post_flow_ring_base_addr : ffffffc00a8d8000
Jan  1 00:00:08 kernel:     rx_complete_flow_ring_base_addr : ffffffc02dcb6000
Jan  1 00:00:08 kernel:     tx_complete_flow_ring_base_addr : ffffffc02dcb4000
Jan  1 00:00:08 kernel:     r2d_wr_arr_base_addr : ffffff80024a9000
Jan  1 00:00:08 kernel:     d2r_rd_arr_base_addr : ffffff80024a9802
Jan  1 00:00:08 kernel:     r2d_rd_arr_base_addr : ffffff80024aa000
Jan  1 00:00:08 kernel:     d2r_wr_arr_base_addr : ffffff80024a9c02
Jan  1 00:00:08 kernel:     tx_post_mgmt_arr_base_addr : ffffff80024aa800
Jan  1 00:00:08 kernel:     tx_post_mgmt_arr_base_phys_addr : 0x2efa1800
Jan  1 00:00:08 kernel:     r2d_wr_arr_base_phys_addr : 0x2efa0000
Jan  1 00:00:08 kernel:     d2r_rd_arr_base_phys_addr : 0x2efa0802
Jan  1 00:00:08 kernel:     r2d_rd_arr_base_phys_addr : 0x2efa1000
Jan  1 00:00:08 kernel:     d2r_wr_arr_base_phys_addr : 0x2efa0c02
Jan  1 00:00:08 kernel:     Doorbell Post Wakeup register : phy_addr: 0xc0802160, virt_addr: ffffff80024a2160
Jan  1 00:00:08 kernel:     Doorbell Complete Wakeup register : phy_addr: 0xc0802164, virt_addr: ffffff80024a2164
Jan  1 00:00:08 kernel:     Doorbell ISR : ffffffbffcf40ab0
Jan  1 00:00:08 kernel:     Doorbell CTX : ffffffc030063400
Jan  1 00:00:08 kernel:     flow_ring_format : 1
Jan  1 00:00:08 kernel:     idma_active : 1
Jan  1 00:00:08 kernel: Backup queue configuration:
Jan  1 00:00:08 kernel: ========================================
Jan  1 00:00:08 kernel: Base virt address = ffffffc00df00000, physical address =  DF00000
Jan  1 00:00:08 kernel: Index stack virt address = ffffffc00dfe38c0, physical address =  DFE38C0
Jan  1 00:00:08 kernel: Backup queue entries: total = 58250  shared by all radios
Jan  1 00:00:08 kernel: ========================================
 
ColinTaylor said:
In the past the first entry in the log would be syslogd started: BusyBox v1.25.1 but I'm not seeing that anymore. This is the start of the syslog. (Notice the date, it doesn't change to May 5 until a bit later in the log)
Click to expand...
Maybe corruption in your JFFS partition where the logs are stored. Try deleting the two syslog files in /jffs then reboot.

Also make sure you aren't having a separate busybox instance installed through Entware, which might override the firmware's syslog daemon.
 
RMerlin said:
Maybe corruption in your JFFS partition where the logs are stored. Try deleting the two syslog files in /jffs then reboot.
Click to expand...
Already tried that, no difference. I also did a factory reset with initialise followed by a minimal configuration and it was exactly the same.

RMerlin said:
Also make sure you aren't having a separate busybox instance installed through Entware, which might override the firmware's syslog daemon.
Click to expand...
No I've never installed another version of BusyBox.
 
ColinTaylor said:
Already tried that, no difference. I also did a factory reset with initialise followed by a minimal configuration and it was exactly the same.


No I've never installed another version of BusyBox.
Click to expand...
Seems unique to the RT-AX86U. Since Broadcom likes to dump ANSI sequences into syslog (...), I wouldn't be surprised if one of the components of that model would send syslog a sequence that completely borked it. I remember in the past there was a similar sequence that prevented the webui from displaying the log, while it would show up fine over ssh.

Not sure what I can do about it if this is the case.
 
ColinTaylor said:
Test it first and then report any actual problems that you've experienced with this beta firmware.
Click to expand...

Sorry, but I can’t perform the test because of the "DDNS update issues". When I enable IPv6, I cannot get an IPv6 address and DDNS will not register. This conjecture may need to be confirmed by 386.4 Beta 2.
3.PNG



In addition, I did do some tests a few minutes ago, including back to 386.3_2. Under 386.3_2, I cannot register IPv6 addresses for DDNS. Even though I already have IPv6, lookups can only return IPv4 addresses. Of course, it is CGNAT.

2.png
 
Yota said:
Sorry, but I can’t perform the test because of the "DDNS update issues". When I enable IPv6, I cannot get an IPv6 address and DDNS will not register. This conjecture may need to be confirmed by 386.4 Beta 2.
Click to expand...
Set WAN retrieval IP mode to "External" instead of "Internal", and see what happens.
 
Running dirty flashed beta 1 on an AX88U with an AX68U node, and I've had no issues at all for ~24hrs. Thanks for your hard work!
 
Status
Not open for further replies.

Similar threads

RMerlin
  • Locked
Beta Asuswrt-Merlin 386.14 beta is now available
2
Replies
35
Views
9K
RMerlin
RMerlin
RMerlin
  • Locked
Beta Asuswrt-Merlin 3006.102.2 Beta is now available for Wifi 7 devices
2 3 4
Replies
70
Views
12K
RMerlin
RMerlin
RMerlin
Release Asuswrt-Merlin 3006.102.2 is now available for Wifi 7 devices
2 3 4
Replies
62
Views
7K
RMerlin
RMerlin
octopus
  • Locked
[ 386.14_1 Build(s) ] available build(s)
Replies
13
Views
1K
octopus
octopus
RMerlin
  • Locked
Beta Asuswrt-Merlin 3004.388.7 beta is now available
5 6 7
Replies
123
Views
17K
RMerlin
RMerlin
Similar threads
Thread starter Title Forum Replies Date
B Unable to establish VPN connection to my PiVPN (ovpn) from my Asus RT-AC86U running Asuswrt-Merlin 386.14 Asuswrt-Merlin 1
RMerlin Release Asuswrt-Merlin 386.14 is now available for AC models Asuswrt-Merlin 209
RMerlin Beta Asuswrt-Merlin 386.14 beta is now available Asuswrt-Merlin 35
RMerlin Release Asuswrt-Merlin 386.13 / 386.13_2 is now available for AC models Asuswrt-Merlin 79
RMerlin Beta Asuswrt-Merlin 386.13 beta is now available for AC models Asuswrt-Merlin 32
RMerlin Release Asuswrt-Merlin 386.12_6 is now available for AC models Asuswrt-Merlin 168
RMerlin Release Asuswrt-Merlin 3004.388.8_4 is now available Asuswrt-Merlin 72
RMerlin Release Asuswrt-Merlin 3006.102.2 is now available for Wifi 7 devices Asuswrt-Merlin 62
F Several Questions Re:Asuswrt-Merlin Feature Implementation Asuswrt-Merlin 2
Yota How to enable port randomization in Asuswrt-Merlin? Asuswrt-Merlin 4

Similar threads

Latest threads

Support SNBForums w/ Amazon

If you'd like to support SNBForums, just use this link and buy anything on Amazon. Thanks!

Sign Up For SNBForums Daily Digest

Get an update of what's new every day delivered to your mailbox. Sign up here!

Members online

Total: 818 (members: 13, guests: 805)
Top