[Beta] RT-AC68U/87U/3200 9.0.0.4_380_2295-g1423616 Beta for checking bug in Network Map

[Raw316]

Dear all,

I am ASUS software R&D, Rawny. I was new here, @Vanic and @ASUS_ASUSWRT can confirm my identification. Latest we improve the [Client list(Network Map)] in asuswrt, and we want to collect some feedbacks.
Please kindly use the beta firmware.

Please reply feedbacks focus on networkmap concerning issues in this thread.

Enhanced points:
1. Fine tune query speed and flow
2. Fix un-detected device issue
3. Update client list in real-time to react offline or sleeping (WLAN) device
4. Use OUI DB insetad of query server.
4. Move client list database from nvram to /jffs(if support, MAX size is 512KB, otherwise temporarily in /tmp) for fixing insufficient memory issue
5. Add delete offline client feature in MAC related functions setting

Beta firmware:
https://www.dropbox.com/sh/80upocxjfjiw2lj/AABudoK7XJrU3VpuFF6glarya?dl=0

How to debug:
1. upgrade to beta firmware 9.0.0.4_380_2295-g1423616 (updated in 2016/2/24)
2. mail to router_feedback@asus.com
3. *MUST* describe what problem you face
- If you don't find any bug and face any problem, not need to feedback.
4. *MUST* add mail title with [Network Map issue]
- If you don't add mail title for me, I can't search for this mail, and then I can't debug.

Known issues:
1. Strange UI view in IE
2. Unrecognized Samsung TV under media bridge
3. Unknown network service found no name in networkmap

Bugfix in beta firmware:
[bugfix] network map client list "view list" close button not work
[bugfix] incorrect client list DB format
[bugfix] move deep scan(protocol query) out hour monitor routine to avoid wake up sleep device issue
[fine tune] reduce socket timeout to avoid not saving DB file in busy network environment

Suggestion:
1. more of icons support
2. LAN > DHCP client list block view detail
3. incomplete offline client list from dhcp/static list

 

[vanic]

Hi all,
Rawny is my colleague, he has done some modification to fine-tune our network map and client list here. For example, OUI issue has fixed in this beta firmware. We are still trying to list all related bugfix.

Thanks,
Vanic

 

[tl2k2]

thanks.

 

[VANT]

Hi Rawny
Fact0ry default is required when we go from 9383 fw ? (if not read below )
I upload this fw and found one bug
In network map when i try close "view list" window using "X" i cant. No reaction

 

[Piter]

Hi Rawny
Fact0ry default is required when we go from 9383 fw ? (if not read below )
I upload this fw and found one bug
In network map when i try close "view list" window using "X" i cant. No reaction
View attachment 5111

I also has the same problem. Close button no reaction.


Maybe good option if you start working to correct network map , is add to VIEW LIST show speed to WIRED Client... ? This is very good option... Show 10Mb, 100Mb, or 1Gb.

 

[jgrove]

Close Button not working, as seen in posts above.

 

[Raw316]

Thanks for all applying.

Close button not working was fixed. We will update new beta firmware tomorrow.

Thanks Piter, we will discuss your suggestion.

 

[Piter]

Ok thanks. Good job

Very cool that the ASUS working hard on improving FW and delegate people to improve specific departments.

 

[RMerlin]

One of the recent issues that appeared a few version back is that the networkmap LAN scans seem to prevent networked printer from staying asleep. I suspect it's caused by networkmap actively probing the network.

Unfortunately I don't have a network printer to test myself, but there's been multiple report of the problem these past few months.

 

[jgrove]

One of the recent issues that appeared a few version back is that the networkmap LAN scans seem to prevent networked printer from staying asleep. I suspect it's caused by networkmap actively probing the network.

Unfortunately I don't have a network printer to test myself, but there's been multiple report of the problem these past few months.

Wake on LAN issue? Must be how the network scan is done?

Got to hand it to you all, support for these routers has been superb, i couldn't have asked for any more.

Thanks

 

[scavenger]

One of the recent issues that appeared a few version back is that the networkmap LAN scans seem to prevent networked printer from staying asleep. I suspect it's caused by networkmap actively probing the network.

Unfortunately I don't have a network printer to test myself, but there's been multiple report of the problem these past few months.

You just cleared up one of the great mysteries of my home network. A constant notification in Windows 10 that the "scan to computer" functionality is not available. Like clockwork, and can't turn it off. Now it makes sense, it's the printer waking up to probes from the 87U.

I wonder if these active probes are related to the Android battery drain problem we've heard so much about. Maybe we could have a MAC address blacklist to avoid probes..?

 

[RMerlin]

Wake on LAN issue? Must be how the network scan is done?

Got to hand it to you all, support for these routers has been superb, i couldn't have asked for any more.

It's not actually WOL. Printers tend to go to sleep and wake up when a print task gets submitted, or under some other scenarios. Networkmap does a few things as it probes the network, including trying to access to LPR and RAW print services, trying to access to any web service running on port 80, etc... One of these events will bring a printer out of sleep mode.

 

[VANT]

next bug.
client status list is gone....
Today morning work ok, but now not.

i try refresh buton but not help.
last part of syslog

Dec 22 12:00:23 networkmap: Starting full scan!
Dec 22 12:00:23 networkmap: reset client tables!
Dec 22 12:00:25 networkmap: Finish full scan!
Dec 22 12:01:47 networkmap: Write to DB file!
Dec 22 12:03:26 networkmap: Write to DB file!
Dec 22 12:07:38 alert mail: AiProtection send mail
Dec 22 13:00:22 networkmap: Starting full scan!
Dec 22 13:00:22 networkmap: reset client tables!
Dec 22 13:00:25 networkmap: Finish full scan!
Dec 22 13:01:31 networkmap: Write to DB file!
Dec 22 14:00:22 networkmap: Starting full scan!
Dec 22 14:00:22 networkmap: reset client tables!
Dec 22 14:00:25 networkmap: Finish full scan!
Dec 22 14:00:48 networkmap: Write to DB file!
Dec 22 14:02:02 networkmap: Write to DB file!
Dec 22 14:04:44 networkmap: Write to DB file!
Dec 22 15:00:23 networkmap: Starting full scan!
Dec 22 15:00:23 networkmap: reset client tables!
Dec 22 15:00:25 networkmap: Finish full scan!
Dec 22 15:00:49 networkmap: Write to DB file!
Dec 22 15:03:44 networkmap: Write to DB file!
Dec 22 15:16:09 networkmap: Write to DB file!
Dec 22 16:00:22 networkmap: Starting full scan!
Dec 22 16:00:22 networkmap: reset client tables!
Dec 22 16:00:24 networkmap: Finish full scan!
Dec 22 16:01:10 networkmap: Write to DB file!
Dec 22 16:07:25 networkmap: Write to DB file!
Dec 22 16:57:52 networkmap: Write to DB file!
Dec 22 17:00:22 networkmap: Starting full scan!
Dec 22 17:00:22 networkmap: reset client tables!
Dec 22 17:00:25 networkmap: Finish full scan!
Dec 22 17:01:41 networkmap: Write to DB file!
Dec 22 17:25:17 networkmap: Write to DB file!
Dec 22 18:00:21 networkmap: Starting full scan!
Dec 22 18:00:21 networkmap: reset client tables!
Dec 22 18:00:24 networkmap: Finish full scan!
Dec 22 18:01:33 networkmap: Write to DB file!
Dec 22 19:00:21 networkmap: Starting full scan!
Dec 22 19:00:21 networkmap: reset client tables!
Dec 22 19:00:24 networkmap: Finish full scan!
Dec 22 19:04:05 networkmap: Write to DB file!
Dec 22 19:24:32 networkmap: Write to DB file!
Dec 22 19:36:43 networkmap: Write to DB file!
Dec 22 20:00:23 networkmap: Starting full scan!
Dec 22 20:00:23 networkmap: reset client tables!
Dec 22 20:00:25 networkmap: Finish full scan!
Dec 22 20:02:27 networkmap: Write to DB file!
Dec 22 20:21:31 networkmap: Starting full scan!
Dec 22 20:21:33 networkmap: Finish full scan!
Dec 22 20:21:51 networkmap: Starting full scan!
Dec 22 20:21:54 networkmap: Finish full scan!
Dec 22 20:21:55 rc_service: httpd 431:notify_rc start_lltdc
Dec 22 20:21:55 rc_service: httpd 431:notify_rc start_miniupnpc
Dec 22 20:21:55 rc_service: waitting "start_lltdc" via httpd ...
Dec 22 20:22:01 networkmap: Starting full scan!
Dec 22 20:22:01 networkmap: reset client tables!
Dec 22 20:22:03 networkmap: Finish full scan!
Dec 22 20:22:13 networkmap: Starting full scan!
Dec 22 20:22:16 networkmap: Finish full scan!
Dec 22 20:22:17 rc_service: httpd 431:notify_rc start_lltdc
Dec 22 20:22:17 rc_service: httpd 431:notify_rc start_miniupnpc
Dec 22 20:22:17 rc_service: waitting "start_lltdc" via httpd ...
Dec 22 20:22:23 networkmap: Starting full scan!
Dec 22 20:22:23 networkmap: reset client tables!
Dec 22 20:22:25 networkmap: Finish full scan!
Dec 22 20:23:34 rc_service: httpd 431:notify_rc start_lltdc
Dec 22 20:23:34 rc_service: httpd 431:notify_rc start_miniupnpc
Dec 22 20:23:34 rc_service: waitting "start_lltdc" via httpd ...
Dec 22 20:23:41 networkmap: Starting full scan!
Dec 22 20:23:41 networkmap: reset client tables!
Dec 22 20:23:44 networkmap: Finish full scan!
Dec 22 20:26:04 rc_service: httpd 431:notify_rc start_lltdc
Dec 22 20:26:04 rc_service: httpd 431:notify_rc start_miniupnpc
Dec 22 20:26:04 rc_service: waitting "start_lltdc" via httpd ...
Dec 22 20:26:06 networkmap: Starting full scan!
Dec 22 20:26:06 networkmap: reset client tables!
Dec 22 20:26:07 rc_service: httpd 431:notify_rc start_lltdc
Dec 22 20:26:07 rc_service: httpd 431:notify_rc start_miniupnpc
Dec 22 20:26:07 rc_service: waitting "start_lltdc" via httpd ...
Dec 22 20:26:12 networkmap: Starting full scan!
Dec 22 20:26:12 networkmap: reset client tables!
Dec 22 20:26:15 networkmap: Finish full scan!

 

[VANT]

continous

client list is gone everywhere where is used like aiprotection/parental control etc.
after router restart, start work normally.

I should make factory default when i go from official 9383 fw ?

 

[bradbort]

One of the recent issues that appeared a few version back is that the networkmap LAN scans seem to prevent networked printer from staying asleep. I suspect it's caused by networkmap actively probing the network.

Unfortunately I don't have a network printer to test myself, but there's been multiple report of the problem these past few months.

Interesting. I have not had this problem, and have two brother networked printer wirelessly attached.

 

[Raw316]

continous
View attachment 5142
client list is gone everywhere where is used like aiprotection/parental control etc.
after router restart, start work normally.

I should make factory default when i go from official 9383 fw ?

Hi VANT,

According to your system log, the reset flag from nvram was set to clean client list.
And the flag did not unset by the networkmap daemon, the suggestion is making factory default to unset some unused nvram values. If you still have the same problem, please sent feedback to @ASUS_ASUSWRT.

Thanks for your applying.

 

[vanic]

I also has the same problem. Close button no reaction.


Maybe good option if you start working to correct network map , is add to VIEW LIST show speed to WIRED Client... ? This is very good option... Show 10Mb, 100Mb, or 1Gb.
View attachment 5117

Hi Piter,
We don't implement wired linked rate here because we can't detect cascade device, only can detect the device connected to router directly. This must be a future work.

Thanks,
Vanic

 

[Piter]

Hi
Ok but maybe now implement to show rate only for devices connected to router directly...?

And please add to your plans to future

 

[vanic]

Ok but maybe now implement to show rate only for devices connected to router directly...?
=> It's not a good idea, user will ask why not to support all, only connected? It brings us spending more time to clarify. If we can't fix all, we don't bring more side effect on this part.

 

[Piter]

Ok but maybe now implement to show rate only for devices connected to router directly...?
=> It's not a good idea, user will ask why not to support all, only connected? It brings us spending more time to clarify. If we can't fix all, we don't bring more side effect on this part.

Add info to changelog that now only support devices connected directly to router and it was info for user.