Dirty flash. Is this something new in dnsmasq start up log?
*can’t seem to attach code
1. What is that wsdd2 flood in logs? The message appears again and again with different pid in [].Jan 12 14:36:18 wsdd2[11216]: Terminated received.
Jan 12 14:36:18 smbd[12173]: [2023/01/12 14:36:18.395329, 0] lib/pidfile.c:146(pidfile_create)
Jan 12 14:36:18 smbd[12173]: ERROR: smbd is already running. File /var/run/samba/smbd.pid exists and process id 11210 is running.
Dirty flash. Is this something new in dnsmasq start up log?
These are normal messages when you have “Prevent client auto-DoH” and DNSPrivacy enabled.I see the same thing is this a problem ?
Unfortunately my issue with random network drops is not solved: I still cannot copy 10-20 Gb files from shared HDD on any client (just an example to reproduce, same on Internet dl/ul so it is true for any connection) without connection drops. And logs are still clear on that.Jan 12 16:37:11 networkmap: Error locking /var/lock//usr/networkmap/nmp_conv_type.js.lock: 2 No such file or directory
Jan 12 16:37:11 networkmap: Error unlocking -1: 9 Bad file descriptor
Jan 12 16:37:11 networkmap: Error locking /var/lock//usr/networkmap/nmp_vendor_type.js.lock: 2 No such file or directory
Jan 12 16:37:11 networkmap: Error unlocking -1: 9 Bad file descriptor
Jan 12 16:37:11 networkmap: Error locking /var/lock//usr/networkmap/nmp_bwdpi_type.js.lock: 2 No such file or directory
Jan 12 16:37:11 networkmap: Error unlocking -1: 9 Bad file descriptor
...
Jan 12 16:37:14 dnsmasq-script[18826]: json_object_from_file: error opening file /jffs/nmp_vc_json.js: No such file or directory
How much time does it really take to nuke the unit on upgrade vs. fighting brushfires for hours and/or days? Seriously.Dirty upgrade ... [problems] ...
It all depends on your configuration and network architecture. In the end, it's a personal choice.How much time does it really take to nuke the unit on upgrade vs. fighting brushfires for hours and/or days? Seriously.
Unfortunately the router does not allow to export all configuration in some form of text file and/or separating different parts of settings in different files (like ani *nix system does).How much time does it really take to nuke the unit on upgrade vs. fighting brushfires for hours and/or days? Seriously.
I don't get your questionDoes it never happen that an update changes behaviour (either breaking something, or finally fixing what'd never worked right), thus even the referencing of screenshots being the cause of "problem introduction"?
I'm only a little more than half a year into acquaintance with Asus routers, so I have to ask this.
I did the hard reset, WPS button method, holding down while turning on power. 388.2 alpha was still on there,
I have experienced the exact same AX86U router rebooting issue when starting or stopping a WG client with 388.2. Flashed back to 388.1 and problem does not occur.I dirty flashed 388.2 alpha over 388.1 official release. I have Astrill VPN installed and some ip route add ips and some port forwarded in /jffs/scripts/ nat-start. I notice when I would disconnect from a wireguard client, my AX86U would say 100% complete, then it would hang, then router would do a restart, but upon rebooting, it would be disconnected from the WG client (which I wanted in the first place). Sometimes I am able to connect to a VPN and minutes later disconnect without any issues, also vice versa I would connect to a WG client it would say 100%, then router would pause and then reboot, then upon rebooting I would be connected, at this point I didnt know if it was taking long to change settings or if this was a feature lol, but checking system info, it shows the router just rebooted.
I did the hard reset, WPS button method, holding down while turning on power. 388.2 alpha was still on there, all wifi settings reset even jffs cleared, I added one WG client to test, and same thing it would sometimes reboot when connecting or disconnecting from the WG client. Also did notice GUI was a bit slow at times, only on a fresh reboot.
I am new to Asus routers, so I flashed back to 388.1 release, and all was working again no problems.
Yes, I just realized that when doing the hard reset, will google how to do a clean install of the new firmware.Doing a hard reset does NOT change the installed firmware.
Yes, glad I'm not the only one experiencing this, I was thinking it could be my router memory itself.I have experienced the exact same AX86U router rebooting issue when starting or stopping a WG client with 388.2. Flashed back to 388.1 and problem does not occur.
Welcome To SNBForums
SNBForums is a community for anyone who wants to learn about or discuss the latest in wireless routers, network storage and the ins and outs of building and maintaining a small network.
If you'd like to post a question, simply register and have at it!
While you're at it, please check out SmallNetBuilder for product reviews and our famous Router Charts, Ranker and plenty more!