What's new

[Beta] Asuswrt-Merlin 380.65 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.
To those having the "scanner issue": is there a consistent way to reproduce it, or is it just random?

I'm not seeing the problem on my RT-AC3200 with 380.65_beta3.

After flashing, the devices seem to work for a bit and then disappear and stop responding randomly. A reboot usually makes the device pop up for a bit, but then it goes dark again. Look at your client list on (380.64_2) and after updating to .65 and see if it becomes unstable after compared to before. Unstable meaning the number of devices changes dramatically every refresh. Users with only a couple of devices might not notice.
 
After flashing, the devices seem to work for a bit and then disappear and stop responding randomly. A reboot usually makes the device pop up for a bit, but then it goes dark again. Look at your client list on (380.64_2) and after updating to .65 and see if it becomes unstable after compared to before. Unstable meaning the number of devices changes dramatically every refresh. Users with only a couple of devices might not notice.

Thanks, I will keep an eye on it and compare it to 380.64_2. I have 8-12 clients active, depending on the time of the day, from Apple devices to printers and HomeKit power switches.

Usually, after how long do you start seeing the issue?

Also, I don't think it has anything to do with uPNP, as uPNP is only responsible for making dynamic port forwarding entries from WAN to LAN, not for local IP assignments.
 
Thanks, I will keep an eye on it and compare it to 380.64_2. I have 8-12 clients active, depending on the time of the day, from Apple devices to printers and HomeKit power switches.

Usually, after how long do you start seeing the issue?

Also, I don't think it has anything to do with uPNP, as uPNP is only responsible for making dynamic port forwarding entries from WAN to LAN, not for local IP assignments.

UPnP protocol for devices to discover and announce themselves is not the same as the UPnP setting on the router that can be considered insecure. The UPnP devices will still work on the home network with that setting off. I meant the UPnP search request and device advertisement protocol seems dysfunctional with the latest firmware.

Also, the device list should start bugging out on first boot.. it is very noticeable if you have several devices connected. Go to Network map and on the right under client status, click refresh and see if any devices are dropped and added at an abnormal rate.

Edit: Just to be clear, the Wireless Log will show that the devices have an IP assigned and the devices themselves are connected with an IP. They just don't respond or advertise themselves on the network as they should.
 
Sorry Merlin, is there any chance to implement this:

s.1485625384.jpg

Thank You :p
 
Any chance to go to Telnet and type top to see what are the processes with top CPU usage? :rolleyes:

In my case it's Transmission:
Mem: 128544K used, 126608K free, 5528K shrd, 2156K buff, 48668K cached
CPU: 0.0% usr 5.0% sys 0.0% nic 45.0% idle 50.0% io 0.0% irq 0.0% sirq
Load average: 1.14 1.10 1.11 2/84 18804
PID PPID USER STAT VSZ %VSZ CPU %CPU COMMAND
2216 1 admin S 93348 36.4 0 5.0 transmission-daemon -g /opt/etc/transmission
1780 1 admin S 8184 3.2 1 0.0 httpd -i br0
822 1 admin S 7616 2.9 0 0.0 watchdog
1 0 admin S 7548 2.9 0 0.0 /sbin/preinit

For my situation, transmission is not related:
Code:
Mem: 76708K used, 162964K free, 0K shrd, 11008K buff, 27740K cached
CPU:  0.5% usr  1.4% sys  0.0% nic  6.7% idle  0.0% io  0.4% irq 90.8% sirq
Load average: 2.25 1.10 0.53 4/60 1685
  PID  PPID USER     STAT   VSZ %VSZ CPU %CPU COMMAND
  247     1 VVS      S     4972  2.0   0 11.3 watchdog
  225     1 VVS      S     1220  0.5   0 10.7 /bin/eapd
    3     2 VVS      SWN      0  0.0   0 10.3 [ksoftirqd/0]
  233     1 VVS      S     1364  0.5   0  9.2 /usr/sbin/acsd
 1665  1659 VVS      R     1456  0.6   0  6.5 top
  744     1 VVS      S     1452  0.6   0  3.3 telnetd -b 192.168.1.1
  768     1 VVS      S      860  0.3   0  1.9 miniupnpd -f /etc/upnp/config
  227     1 VVS      S     4208  1.7   0  1.1 /bin/wps_monitor
  222     1 VVS      S     4972  2.0   0  0.2 /sbin/wanduck
    4     2 VVS      SW<      0  0.0   0  0.1 [events/0]
  548   546 VVS      S     6920  2.8   0  0.0 minidlna -f /etc/minidlna.conf -r
  549   548 VVS      R N   6920  2.8   0  0.0 minidlna -f /etc/minidlna.conf -r
  546     1 VVS      S     6920  2.8   0  0.0 minidlna -f /etc/minidlna.conf -r
  543     1 VVS      S     6052  2.5   0  0.0 /usr/sbin/smbd -D -s /etc/smb.conf
  540     1 VVS      S     5856  2.4   0  0.0 nmbd -D -s /etc/smb.conf
    1     0 VVS      S     4996  2.0   0  0.0 /sbin/init noinitrd
  396     1 VVS      S     4972  2.0   0  0.0 usbled
  556     1 VVS      S     4972  2.0   0  0.0 ntp
  567     1 VVS      S     4972  2.0   0  0.0 disk_monitor
  229     1 VVS      S     4972  2.0   0  0.0 wpsaide
  251   247 VVS      S     4972  2.0   0  0.0 ots
  156     1 VVS      S     4964  2.0   0  0.0 console
  764     1 VVS      S     4960  2.0   0  0.0 httpds -s -p 8443 -i br0
  765     1 VVS      S     4848  2.0   0  0.0 httpd -i br0
  542     1 VVS      S     3692  1.5   0  0.0 vsftpd /etc/vsftpd.conf
  409   407 VVS      S     2300  0.9   0  0.0 u2ec
  407     1 VVS      S     2300  0.9   0  0.0 u2ec
  410   409 VVS      S     2300  0.9   0  0.0 u2ec
  245     1 VVS      S     2296  0.9   0  0.0 rstats
  231     1 VVS      S     1648  0.6   0  0.0 nas
  309   290 VVS      S     1480  0.6   0  0.0 pppd sync nodetach noaccomp nobsdcomp nodeflate nopcomp novj novjccomp file /tmp/ppp/options.wan0 plugin pppol2tp.so pppol2tp 10
  287     1 VVS      S     1464  0.6   0  0.0 /sbin/udhcpc -i eth0 -p /var/run/udhcpc0.pid -s /tmp/udhcpc -b -O33 -O249
 1659   744 VVS      S     1460  0.6   0  0.0 -sh
  159   156 VVS      S     1460  0.6   0  0.0 /bin/sh
  740     1 VVS      S     1452  0.6   0  0.0 /sbin/klogd -c 5
  240     1 VVS      S     1452  0.6   0  0.0 crond
  738     1 VVS      S     1448  0.6   0  0.0 /sbin/syslogd -m 0 -S -O /tmp/syslog.log -s 256 -l 7
  408     1 VVS      S     1280  0.5   0  0.0 lpd br0
  236     1 nobody   S     1244  0.5   0  0.0 dnsmasq --log-async
  265     1 VVS      S     1240  0.5   0  0.0 networkmap --bootwait
  261     1 VVS      R     1224  0.5   0  0.0 lld2d br0
  241     1 VVS      S     1180  0.4   0  0.0 /usr/sbin/infosvr br0
  264     1 VVS      S     1052  0.4   0  0.0 mDNSNetMonitor
  290     1 VVS      S      936  0.3   0  0.0 /usr/sbin/l2tpd
  119     1 VVS      S      648  0.2   0  0.0 hotplug2 --persistent --no-coldplug
   98     2 VVS      SW<      0  0.0   0  0.0 [mtdblockd]
   52     2 VVS      SW       0  0.0   0  0.0 [pdflush]
  376     2 VVS      SW<      0  0.0   0  0.0 [usb-storage]
  386     2 VVS      SW<      0  0.0   0  0.0 [usb-storage]
  297     2 VVS      SW<      0  0.0   0  0.0 [khubd]
  375     2 VVS      SW<      0  0.0   0  0.0 [scsi_eh_0]
  385     2 VVS      SW<      0  0.0   0  0.0 [scsi_eh_1]
  115     2 VVS      SW<      0  0.0   0  0.0 [kmmcd]
   54     2 VVS      SW<      0  0.0   0  0.0 [aio/0]
    2     0 VVS      SW<      0  0.0   0  0.0 [kthreadd]
  161     2 VVS      SWN      0  0.0   0  0.0 [jffs2_gcd_mtd4]
   53     2 VVS      SW<      0  0.0   0  0.0 [kswapd0]
    5     2 VVS      SW<      0  0.0   0  0.0 [khelper]
   20     2 VVS      SW<      0  0.0   0  0.0 [kblockd/0]
   51     2 VVS      SW       0  0.0   0  0.0 [pdflush]
 
Last edited:
The function "Infected Device Prevention and Blocking" --> "Alert Preference" where you enter the email address to send the alerts is not working on my RT5300, I never get the email alerts, am I doing something wrong? Is there a way to reset this option to make it work, thanks

Check your configuration on GMail's end - this is working for me.
 
I see the devices in the wireless log, but the client list keeps refreshing showing 23, then 5 then 12 then 2 devices and I can't find my printers and other devices when I search or try to print or access them. I feel it's a uPnP issue introduced in 4180, but I don't know what the exact issue is and what's triggering it.

UPnP has nothing to do with networkmap's scanning. My theory is one of your clients is causing the daemon to crash on scan, because it works fine for the rest of us.
 
Sorry Merlin, is there any chance to implement this:

Thank You :p

Constantly asking me again and again for the same thing isn't gonna make me change my mind - quite the opposite. The current answer is still "No". Because that page doesn't dynamically refresh itself, because putting a text-only icon is absolutely horrible design (and I'm more than tempted to remove Asus's own "App" one there), because the generated popup could grow too large as one might have 3 or 4 clients connected, because people will constantly ask for that popup to increase the amount of information being shown. There's a VPN Status page, I deliberately made it be the default page when you click on "VPN" so it's the same as the icon you are asking for: a single mouse click will give you all the info you want.
 
UPnP has nothing to do with networkmap's scanning. My theory is one of your clients is causing the daemon to crash on scan, because it works fine for the rest of us.

Doesn't work for me either. Happens with official 4180. My client list goes nuts on my ac3100 and could be why airprint stops working after about 10 minutes.

EDIT: I checked the list of devices connected and one of them stands out. I have a device with the name "The Chamberlain Group, Inc" . . . could this be causing an issue suddenly? It works fine on older versions of firmware. All other devices have no special characters or even spaces in them.
 
Last edited:
Thanks, what else should I check? I have already ON the less secure apps option

Allow less secure apps: ON

Make sure you don't use 2F authentication - not sure if it's compatible with it.

Beyond that I don't know. I don't use that feature, I only enabled it last week to test something out.
 
EDIT: I checked the list of devices connected and one of them stands out. I have a device with the name "The Chamberlain Group, Inc" . . . could this be causing an issue suddenly? It works fine on older versions of firmware. All other devices have no special characters or even spaces in them.

It's a pretty long name indeed. Try unplugging that device to see if it helps stabilizing things out.

People have been reporting various client list issues for well over a year now, it's definitely nothing new in 4180.
 
Make sure you don't use 2F authentication - not sure if it's compatible with it.

Beyond that I don't know. I don't use that feature, I only enabled it last week to test something out.
This is weird I do not have 2FA in Google and I just changed to AOL email account and I got the email confirmation on AOL that the email was registered, but it is not blocking anything
 
Would it be an idea, if its possible and not too much of a hassle, to add a checkbox next to the factory reset button, that would clear nvram at the same time? Would be pretty neat.

A factory reset does indeed clear nvram hence the use of the word "factory". The router is rendered into the state in which it left the factory.

Not really, it resets the firmware installed, be it Asus stock or Asuswrt-Merlin.
I am not aware of the term "factory reset" being defined as reverting to the firmware version that the item left the factory with. My understanding has been that a "factory reset" meant the nvram settings are restored to their state they are when leaving the factory. If I am wrong then I hope that someone will civilly inform me and cite an example. I have reset my RT-AC87U using the factory reset on the Administration|Restore/Save/Upload Setting page.
 
I see the devices in the wireless log, but the client list keeps refreshing showing 23, then 5 then 12 then 2 devices and I can't find my printers and other devices when I search or try to print or access them. I feel it's a uPnP issue introduced in 4180, but I don't know what the exact issue is and what's triggering it.

This problem with disappearing printers and the fluctuating client list seems to be model-specific. As I said in my earlier post, I'm seeing this on an RT-AC3100 with official 380_4180 or the Merlin 380.65 betas. But NO issues with those same firmware versions on an RT-AC66U.

I see from their posts and signatures that the others complaining of this, effortless, kibosh, and bradbort, are all using the AC3100 as well.
 
UPnP has nothing to do with networkmap's scanning. My theory is one of your clients is causing the daemon to crash on scan, because it works fine for the rest of us.

I'm not referring to the UPnP option that configures ports through the firewall... I'm talking about network discovery (UPnP). It certainly has something to do with how printers and other devices on a network can advertise and discover each other... it was standardized in 1999 just for that purpose.
Reference: UPnP Forum, What is UPnP, UPnP in Windows


If it was one of my clients, then why does it work on the older firmware perfectly and not the new one. There had to be a change that caused the problem.

Also, I am not the only one with this issue. There have been at least 3-4 others in this same thread and there are several in the Asus firmware forum here as well as Asus' own forum with the same exact problem:

https://vip.asus.com/forum/view.asp...d_id=11&model=RT-AC88U&page=1&SLanguage=en-us

https://vip.asus.com/forum/view.asp..._id=11&model=RT-AC5300&page=1&SLanguage=en-us

https://www.snbforums.com/threads/asus-rt-5300-version-3-0-0-4-380-3941.34015/page-3
 
It's a pretty long name indeed. Try unplugging that device to see if it helps stabilizing things out.

People have been reporting various client list issues for well over a year now, it's definitely nothing new in 4180.

Removing the device with the crazy long name doesn't help. The client list still goes nuts. Airprint no longer works either :(

This problem with disappearing printers and the fluctuating client list seems to be model-specific. As I said in my earlier post, I'm seeing this on an RT-AC3100 with official 380_4180 or the Merlin 380.65 betas. But NO issues with those same firmware versions on an RT-AC66U.

I see from their posts and signatures that the others complaining of this, effortless, kibosh, and bradbort, are all using the AC3100 as well.

Yup . . . sure seems like this is an exclusive "feature" of the ac3100.
 
Removing the device with the crazy long name doesn't help. The client list still goes nuts. Airprint no longer works either :(



Yup . . . sure seems like this is an exclusive "feature" of the ac3100.

I'd also add the AC88U (which is pretty much the AC3100) and AC5300.
 
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