Recent content by Max33Verstappen

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

  1. Max33Verstappen

    Release Asuswrt-Merlin 3004.388.4 is now available

    This is probably a bug in this release. The "ddns_updated=1" in nvram is not unset when you disconnect and reconnect the WAN from the GUI, so the "ddns-start" won't be called by the watchdog. Adding something like "nvram unset ddns_updated" in the "wan-event" script can temporarily work around...
  2. Max33Verstappen

    [ 386.4 alpha Build(s) ] Testing available build(s)

    As for the new wsdd2 problem. Tried with "-W" option. After starting, the following appear: starting. ifname br0, ifindex 24 hostname XXXXX, netbios name XXXXX, workgroup WORKGROUP wsdd-mcast-v4 udp port 3702 239.255.255.250 192.168.33.1 @ br0 wsdd-mcast-v6 udp port 3702 ff02::c...
  3. Max33Verstappen

    [ 386.4 alpha Build(s) ] Testing available build(s)

    Test the alpha 2 (v3) on ax88u. "/jffs/configs/shadow.add" doesn't get imported to the "/ etc/shadow" in this version. And the new wsdd2 apparently has some compatibility issues, at least in my case. It keeps disappearing from "Network" in windows. (Restart the wsdd2, it re-appears, but after a...
  4. Max33Verstappen

    [ 386.4 alpha Build(s) ] Testing available build(s)

    By testing the old wsdd2 binary on this alpha FW. The problem seems from the new wsdd2. With the old wsdd2, after the WAN restart, I don't have to restart it, and the router appears again in Windows Network. (With either version of wsdd2, after manual wan disconnection, the router disappears...
  5. Max33Verstappen

    [ 386.4 alpha Build(s) ] Testing available build(s)

    As for this change -- "No longer restart nasapps/wsdd2 on WAN start." On AX88U, immediately after manual WAN disconnection, the router disappears from Windows Network, and I must restart wsdd2 to make it appear again. Similarly, after WAN restart, I must restart wsdd2 again to make it appear...
  6. Max33Verstappen

    Beta Asuswrt-Merlin 386.2 Beta is now available

    It seems like a bug in beta 2. If you accidentally left any ipv4 addresses in "LAN -> DNSFilter -> Custom (user-defined) DNS x", these thing will end up in /etc/dnsmasq.conf like somthing as "dhcp-option=dnsf8,option6:23,[1.0.0.1]", which will cause this issue. It's not the case in beta 1.
  7. Max33Verstappen

    Beta Asuswrt-Merlin 386.1 Beta (stage 2) is now available

    Is this problem specific to me? coz I didn't see anybody else have this problem. I've removed extra interface I add manually. But the problem persists. Thx.
  8. Max33Verstappen

    Beta Asuswrt-Merlin 386.1 Beta (stage 2) is now available

    Plz refer to the attachment for the resulting output.
  9. Max33Verstappen

    Beta Asuswrt-Merlin 386.1 Beta (stage 2) is now available

    Here it is: bond0 Link encap:Ethernet HWaddr 04:D4:C4:50:81:C0 inet6 addr: fe80::6d4:c4ff:fe50:81c0/64 Scope:Link UP BROADCAST RUNNING ALLMULTI MASTER MULTICAST MTU:1500 Metric:1 RX packets:15892376 errors:0 dropped:44 overruns:0 frame:0 TX...
  10. Max33Verstappen

    Beta Asuswrt-Merlin 386.1 Beta (stage 2) is now available

    [AX-88U] "/usr/sbin/wsdd2" from beta 5 has problems. USB device shared via samba is invisible though can be accessed by manually typing the \\xxxx. I used binary from beta4b, and the problem is gone. I noticed wsdd2.c has been modified a couple days ago.
  11. Max33Verstappen

    Beta Asuswrt-Merlin 386.1 Beta is now available

    Unfortunately, on Ax88U, still got these traffic spike from interface "br0", just like what was starting since 384.18. Must exclude this interface as a workaround.
  12. Max33Verstappen

    [Thread-1] [ 386.1_Alpha Build(s) ] Testing available build(s)

    AX88U on alpha 3 (also present on alpha 2). If I changed "IPv6 states" from "Native" to "Disabled" or vice versa, then no wireless client can connect (maybe they immediately get disconnected once connected). The log filled with messages shown in the attachment.
  13. Max33Verstappen

    Release [ 384.19_Alpha Build(s) ] Testing available build(s)

    Experienced spike on "Traffic Monitor" chart running 384.18. The problem gone on "RT-AX88U_384.19_alpha1-g9ca4b67bb0". But it's back again on 2nd alpha (g2546f95291). Don't use this QoS stuff.
  14. Max33Verstappen

    [Beta] Asuswrt-Merlin 384.16 beta (and 384.13_5) are available

    AX88U: On beta1, this issue persists (starting from alpha 2): There's sth wrong about the scaling of the chart of 24hr traffic monitor. It just scales up for no reason. The ceiling value is now 1361462.40KB/s, rendering it useless. After restart the 'rstats', it starts normally, but gradually...
Top