Recent content by Max33Verstappen

On BE88u. custom_script: Running /jffs/scripts/service-event-end (args: restart autowan) are flooding the log, no matter what is selected as the Primary WAN in the "Dual WAN" page. 3006_102.2_2 doesn't have this issue. And there's a glitch in the Desktop WebUI, a duplicate entry of the current...

No. I didn't even use the stock firmware and flashed the beta 1 the moment I got into the GUI. You mean your device is dead, suddenly?

Works well on BE88U. The only issue I experience is the spike in the "Traffic Monitor": And I found some suspicious traffic coming from nowhere: eth9 is connected to a NAS, but there's no way to have this traffic. Haven't tried the stock firmware, so don't know if it's an issue from ASUS or...

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...

Same issue on AX88U.

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...

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...

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...

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...

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.

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.

Plz refer to the attachment for the resulting output.

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...

[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.

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.