Jump to content
Netduma Admin

New XR700 Firmware Version v1.0.1.10

Recommended Posts

19 hours ago, Netduma Admin said:

Honestly best to downgrade back to .8 if you’re having issues with .10. This .10 firmwarevwas mostky for anyone having WAN disconnects. If you were not having this then please go back to .8

OK, Just so You know, I downgraded to the one before this latest one Version 10 to Version 8, and yea, talk about issues, here's the detailed log file and you will see there are still issues present 😒😒😒:

 

[DumaOS] Starting process manager, Monday, April 01, 2019 01:27:26
[DumaOS] subscribe to 'com.netdumasoftware.arpwatch' from 'com.netdumasoftware.neighwatch', Monday, April 01, 2019 01:27:29
[DumaOS] DHCP new event., Monday, April 01, 2019 01:27:29
[DumaOS] DHCP new lease allocated., Monday, April 01, 2019 01:27:29
[DumaOS] DHCP new event., Monday, April 01, 2019 01:27:29
[DumaOS] DHCP new lease allocated., Monday, April 01, 2019 01:27:29
[DumaOS] DHCP new event., Monday, April 01, 2019 01:27:29
[DumaOS] DHCP new lease allocated., Monday, April 01, 2019 01:27:29
[DumaOS] DHCP new event., Monday, April 01, 2019 01:27:29
[DumaOS] DHCP new lease allocated., Monday, April 01, 2019 01:27:29
[DumaOS] DHCP new event., Monday, April 01, 2019 01:27:29
[DumaOS] DHCP new lease allocated., Monday, April 01, 2019 01:27:29
[DumaOS] App 'com.netdumasoftware.neighwatch' initialised & starting., Monday, April 01, 2019 01:27:29
[DumaOS] Ubus object 'com.netdumasoftware.neighwatch' added, attempting to bind pending, Monday, April 01, 2019 01:27:29
[DumaOS] Ubus object 'com.netdumasoftware.systeminfo' added, attempting to bind pending, Monday, April 01, 2019 01:27:29
[DumaOS] App 'com.netdumasoftware.systeminfo' initialised & starting., Monday, April 01, 2019 01:27:29
[DumaOS] Ubus object 'com.netdumasoftware.systeminfo' added, attempting to bind pending, Monday, April 01, 2019 01:27:29
[DumaOS] Non-existent publish method 'licence_permitted', Monday, April 01, 2019 01:27:29
[DumaOS] App 'com.netdumasoftware.procmanager' initialised & starting., Monday, April 01, 2019 01:27:29
[DumaOS] Ubus object 'com.netdumasoftware.procmanager' added, attempting to bind pending, Monday, April 01, 2019 01:27:29
[DumaOS] Ubus object 'com.netdumasoftware.neighwatch' added, attempting to bind pending, Monday, April 01, 2019 01:27:29
[DumaOS] Ubus object 'com.netdumasoftware.systeminfo' added, attempting to bind pending, Monday, April 01, 2019 01:27:29
[DumaOS] Ubus object 'com.netdumasoftware.procmanager' added, attempting to bind pending, Monday, April 01, 2019 01:27:29
[DumaOS] pending subscription for package 'com.netdumasoftware.devicemanager', Monday, April 01, 2019 01:27:29
[DumaOS] Waiting for 'com.netdumasoftware.devicemanager' to run before starting, Monday, April 01, 2019 01:27:29
[DumaOS] Waiting for 'com.netdumasoftware.autoadmin' to run before starting, Monday, April 01, 2019 01:27:29
[DumaOS] App 'com.netdumasoftware.qos' initialised & starting., Monday, April 01, 2019 01:27:29
[DumaOS] pending subscription for package 'com.netdumasoftware.devicemanager', Monday, April 01, 2019 01:27:29
[DumaOS] Waiting for 'com.netdumasoftware.devicemanager' to run before starting, Monday, April 01, 2019 01:27:29
[DumaOS] Waiting for 'com.netdumasoftware.autoadmin' to run before starting, Monday, April 01, 2019 01:27:29
[DumaOS] App 'com.netdumasoftware.hybridvpn' initialised & starting., Monday, April 01, 2019 01:27:29
[DumaOS] pending subscription for package 'com.netdumasoftware.devicemanager', Monday, April 01, 2019 01:27:29
[DumaOS] pending subscription for package 'com.netdumasoftware.dpiclass', Monday, April 01, 2019 01:27:29
[DumaOS] Waiting for 'com.netdumasoftware.devicemanager' to run before starting, Monday, April 01, 2019 01:27:29
[DumaOS] Waiting for 'com.netdumasoftware.autoadmin' to run before starting, Monday, April 01, 2019 01:27:29
[DumaOS] App 'com.netdumasoftware.geofilter' initialised & starting., Monday, April 01, 2019 01:27:29
[DumaOS] Ubus object 'com.netdumasoftware.networkmonitor' added, attempting to bind pending, Monday, April 01, 2019 01:27:29
[DumaOS] App 'com.netdumasoftware.networkmonitor' initialised & starting., Monday, April 01, 2019 01:27:29
[DumaOS] Ubus object 'com.netdumasoftware.networkmonitor' added, attempting to bind pending, Monday, April 01, 2019 01:27:29
[DumaOS] subscribe to 'com.netdumasoftware.neighwatch' from 'com.netdumasoftware.devicemanager', Monday, April 01, 2019 01:27:30
[DumaOS] pending subscription for package 'com.netdumasoftware.dpiclass', Monday, April 01, 2019 01:27:30
[DumaOS] Waiting for 'com.netdumasoftware.autoadmin' to run before starting, Monday, April 01, 2019 01:27:30
[DumaOS] App 'com.netdumasoftware.devicemanager' initialised & starting., Monday, April 01, 2019 01:27:30
[DumaOS] config write 'com.netdumasoftware.desktop.database', Monday, April 01, 2019 01:27:30
[DumaOS] config write 'com.netdumasoftware.desktop.database', Monday, April 01, 2019 01:27:30
[DumaOS] Ubus object 'com.netdumasoftware.neighsync' added, attempting to bind pending, Monday, April 01, 2019 01:27:30
[DumaOS] App 'com.netdumasoftware.neighsync' initialised & starting., Monday, April 01, 2019 01:27:30
[DumaOS] Ubus object 'com.netdumasoftware.networkmonitor' added, attempting to bind pending, Monday, April 01, 2019 01:27:30
[DumaOS] Ubus object 'com.netdumasoftware.neighsync' added, attempting to bind pending, Monday, April 01, 2019 01:27:30
[DumaOS] Cloudsync Themes result 'false','All mirrors are down', Monday, April 01, 2019 01:27:30
[DumaOS] Resync R-App store cloud, Monday, April 01, 2019 01:27:30
[DumaOS] Ubus object 'com.netdumasoftware.autoadmin' added, attempting to bind pending, Monday, April 01, 2019 01:27:30
[DumaOS] Dependency loaded 'com.netdumasoftware.autoadmin', Monday, April 01, 2019 01:27:30
[DumaOS] Ubus object 'com.netdumasoftware.autoadmin' added, attempting to bind pending, Monday, April 01, 2019 01:27:30
[DumaOS] Dependency loaded 'com.netdumasoftware.autoadmin', Monday, April 01, 2019 01:27:30
[DumaOS] Ubus object 'com.netdumasoftware.autoadmin' added, attempting to bind pending, Monday, April 01, 2019 01:27:30
[DumaOS] Dependency loaded 'com.netdumasoftware.autoadmin', Monday, April 01, 2019 01:27:30
[DumaOS] Ubus object 'com.netdumasoftware.autoadmin' added, attempting to bind pending, Monday, April 01, 2019 01:27:30
[DumaOS] HTTP download failed with code '404', Monday, April 01, 2019 01:27:30
[DumaOS] R-App store cloud sync failed, Monday, April 01, 2019 01:27:30
[DumaOS] Ubus object 'com.netdumasoftware.rappstore' added, attempting to bind pending, Monday, April 01, 2019 01:27:30
[DumaOS] App 'com.netdumasoftware.rappstore' initialised & starting., Monday, April 01, 2019 01:27:30
[DumaOS] Ubus object 'com.netdumasoftware.rappstore' added, attempting to bind pending, Monday, April 01, 2019 01:27:30
[DumaOS] Ubus object 'com.netdumasoftware.networkmonitor' added, attempting to bind pending, Monday, April 01, 2019 01:27:30
[DumaOS] Ubus object 'com.netdumasoftware.neighsync' added, attempting to bind pending, Monday, April 01, 2019 01:27:30
[DumaOS] Ubus object 'com.netdumasoftware.desktop' added, attempting to bind pending, Monday, April 01, 2019 01:27:30
[DumaOS] App 'com.netdumasoftware.desktop' initialised & starting., Monday, April 01, 2019 01:27:30
[DumaOS] Ubus object 'com.netdumasoftware.desktop' added, attempting to bind pending, Monday, April 01, 2019 01:27:30
[DumaOS] Ubus object 'com.netdumasoftware.networkmonitor' added, attempting to bind pending, Monday, April 01, 2019 01:27:30
[DumaOS] Ubus object 'com.netdumasoftware.desktop' added, attempting to bind pending, Monday, April 01, 2019 01:27:30
[DumaOS] Ubus object 'com.netdumasoftware.neighsync' added, attempting to bind pending, Monday, April 01, 2019 01:27:30
[DumaOS] Ubus object 'com.netdumasoftware.desktop' added, attempting to bind pending, Monday, April 01, 2019 01:27:30
[DumaOS] config write 'com.netdumasoftware.devicemanager.database', Monday, April 01, 2019 01:27:31
[DumaOS] config write 'com.netdumasoftware.devicemanager.database', Monday, April 01, 2019 01:27:31
[DumaOS] Cloudsync DPI result 'false','All mirrors are down', Monday, April 01, 2019 01:27:34
[DumaOS] Ubus object 'com.netdumasoftware.dpiclass' added, attempting to bind pending, Monday, April 01, 2019 01:27:34
[DumaOS] Ubus object 'com.netdumasoftware.dpiclass' now bound, Monday, April 01, 2019 01:27:34
[DumaOS] Ubus object 'com.netdumasoftware.dpiclass' added, attempting to bind pending, Monday, April 01, 2019 01:27:34
[DumaOS] Ubus object 'com.netdumasoftware.devicemanager' added, attempting to bind pending, Monday, April 01, 2019 01:27:36
[DumaOS] Dependency loaded 'com.netdumasoftware.devicemanager', Monday, April 01, 2019 01:27:36
[DumaOS] Ubus object 'com.netdumasoftware.devicemanager' added, attempting to bind pending, Monday, April 01, 2019 01:27:36
[DumaOS] Ubus object 'com.netdumasoftware.rappstore' added, attempting to bind pending, Monday, April 01, 2019 01:27:36
[DumaOS] All dependencies loaded, starting, Monday, April 01, 2019 01:27:36
[DumaOS] Ubus object 'com.netdumasoftware.desktop' added, attempting to bind pending, Monday, April 01, 2019 01:27:36
[DumaOS] Ubus object 'com.netdumasoftware.dpiclass' added, attempting to bind pending, Monday, April 01, 2019 01:27:36
[DumaOS] Ubus object 'com.netdumasoftware.devicemanager' added, attempting to bind pending, Monday, April 01, 2019 01:27:36
[DumaOS] All dependencies loaded, starting, Monday, April 01, 2019 01:27:36
[DumaOS] Ubus object 'com.netdumasoftware.dpiclass' now bound, Monday, April 01, 2019 01:27:36
[DumaOS] Ubus object 'com.netdumasoftware.devicemanager' added, attempting to bind pending, Monday, April 01, 2019 01:27:36
[DumaOS] Dependency loaded 'com.netdumasoftware.devicemanager', Monday, April 01, 2019 01:27:36
[DumaOS] All dependencies loaded, starting, Monday, April 01, 2019 01:27:36
[DumaOS] Ubus object 'com.netdumasoftware.devicemanager' added, attempting to bind pending, Monday, April 01, 2019 01:27:36
[DumaOS] Ubus object 'com.netdumasoftware.devicemanager' added, attempting to bind pending, Monday, April 01, 2019 01:27:36
[DumaOS] Ubus object 'com.netdumasoftware.hybridvpn' added, attempting to bind pending, Monday, April 01, 2019 01:27:36
[DumaOS] Ubus object 'com.netdumasoftware.devicemanager' now bound, Monday, April 01, 2019 01:27:36
[DumaOS] Ubus object 'com.netdumasoftware.hybridvpn' added, attempting to bind pending, Monday, April 01, 2019 01:27:36
[DumaOS] Ubus object 'com.netdumasoftware.devicemanager' added, attempting to bind pending, Monday, April 01, 2019 01:27:37
[DumaOS] Ubus object 'com.netdumasoftware.hybridvpn' added, attempting to bind pending, Monday, April 01, 2019 01:27:37
[DumaOS] applying qos for zone wan, Monday, April 01, 2019 01:27:38
[DumaOS] applying qos for zone lan, Monday, April 01, 2019 01:27:38
[DumaOS] Ubus object 'com.netdumasoftware.qos' added, attempting to bind pending, Monday, April 01, 2019 01:27:39
[DumaOS] Ubus object 'com.netdumasoftware.devicemanager' now bound, Monday, April 01, 2019 01:27:39
[DumaOS] Ubus object 'com.netdumasoftware.hybridvpn' added, attempting to bind pending, Monday, April 01, 2019 01:27:39
[DumaOS] Ubus object 'com.netdumasoftware.qos' added, attempting to bind pending, Monday, April 01, 2019 01:27:39
[DumaOS] DHCP new event., Monday, April 01, 2019 01:27:40
[DumaOS] DHCP new lease allocated., Monday, April 01, 2019 01:27:40
[DumaOS] Geo-Filter cloudsync result 'true','nil', Monday, April 01, 2019 01:27:41
[DumaOS] DHCP new event., Monday, April 01, 2019 01:27:43
[DumaOS] DHCP new lease allocated., Monday, April 01, 2019 01:27:43
[DumaOS] DHCP new event., Monday, April 01, 2019 01:27:43
[DumaOS] DHCP new lease allocated., Monday, April 01, 2019 01:27:43
[DumaOS] DHCP new event., Monday, April 01, 2019 01:27:43
[DumaOS] DHCP new lease allocated., Monday, April 01, 2019 01:27:43
[DumaOS] DHCP new event., Monday, April 01, 2019 01:27:44
[DumaOS] DHCP new lease allocated., Monday, April 01, 2019 01:27:44
[DumaOS] applying qos for zone wan, Monday, April 01, 2019 01:27:51
[DumaOS] applying qos for zone lan, Monday, April 01, 2019 01:27:51
[DumaOS] Ubus object 'com.netdumasoftware.geofilter' added, attempting to bind pending, Monday, April 01, 2019 01:27:53
[DumaOS] Ubus object 'com.netdumasoftware.devicemanager' now bound, Monday, April 01, 2019 01:27:53
[DumaOS] Ubus object 'com.netdumasoftware.hybridvpn' added, attempting to bind pending, Monday, April 01, 2019 01:27:53
[DumaOS] Ubus object 'com.netdumasoftware.qos' added, attempting to bind pending, Monday, April 01, 2019 01:27:53
[DumaOS] Ubus object 'com.netdumasoftware.geofilter' added, attempting to bind pending, Monday, April 01, 2019 01:27:53
[DumaOS] config write 'com.netdumasoftware.devicemanager.database', Monday, April 01, 2019 01:27:54
[DumaOS] DHCP new event., Monday, April 01, 2019 01:27:55
[DumaOS] DHCP new lease allocated., Monday, April 01, 2019 01:27:55
[DumaOS] DHCP new event., Monday, April 01, 2019 01:27:56
[DumaOS] DHCP lease change., Monday, April 01, 2019 01:27:56
[DumaOS] DHCP new event., Monday, April 01, 2019 01:27:57
[DumaOS] DHCP new lease allocated., Monday, April 01, 2019 01:27:57
[DumaOS] DHCP new event., Monday, April 01, 2019 01:27:58
[DumaOS] DHCP new lease allocated., Monday, April 01, 2019 01:27:58
[DumaOS] DHCP new event., Monday, April 01, 2019 01:27:59
[DumaOS] DHCP new lease allocated., Monday, April 01, 2019 01:27:59
[DumaOS] DHCP new event., Monday, April 01, 2019 01:30:44
[DumaOS] DHCP new lease allocated., Monday, April 01, 2019 01:30:44
[DumaOS] config write 'com.netdumasoftware.qos.settings', Monday, April 01, 2019 01:42:53
[DumaOS] applying qos for zone wan, Monday, April 01, 2019 01:42:53
[DumaOS] applying qos for zone lan, Monday, April 01, 2019 01:42:54
[DumaOS] config write 'com.netdumasoftware.qos.settings', Monday, April 01, 2019 01:43:39
[DumaOS] DHCP new event., Monday, April 01, 2019 01:45:37
[DumaOS] DHCP lease change., Monday, April 01, 2019 01:45:37
[DumaOS] DHCP new event., Monday, April 01, 2019 01:45:39
[DumaOS] DHCP lease change., Monday, April 01, 2019 01:45:39
[DumaOS] DHCP new event., Monday, April 01, 2019 01:45:46
[DumaOS] DHCP lease change., Monday, April 01, 2019 01:45:46
[DumaOS] DHCP new event., Monday, April 01, 2019 01:45:47
[DumaOS] DHCP lease change., Monday, April 01, 2019 01:45:47
[DumaOS] DHCP new event., Monday, April 01, 2019 01:45:48
[DumaOS] DHCP lease change., Monday, April 01, 2019 01:45:48
[DumaOS] DHCP new event., Monday, April 01, 2019 01:45:48
[DumaOS] DHCP lease change., Monday, April 01, 2019 01:45:48
[DumaOS] DHCP new event., Monday, April 01, 2019 01:45:49
[DumaOS] DHCP lease change., Monday, April 01, 2019 01:45:49
[DumaOS] DHCP new event., Monday, April 01, 2019 01:45:49
[DumaOS] DHCP lease change., Monday, April 01, 2019 01:45:49
[DumaOS] DHCP new event., Monday, April 01, 2019 01:45:50
[DumaOS] DHCP lease change., Monday, April 01, 2019 01:45:50
[DumaOS] DHCP new event., Monday, April 01, 2019 01:45:59
[DumaOS] DHCP lease change., Monday, April 01, 2019 01:45:59
[DumaOS] applying qos for zone wan, Monday, April 01, 2019 01:48:22
[DumaOS] applying qos for zone lan, Monday, April 01, 2019 01:48:22
[DoS Attack: RST Scan] from source: 50.63.243.230, port 80, Monday, April 01, 2019 01:48:27
[DumaOS] Backing up settings to config partition., Monday, April 01, 2019 01:48:49
[DumaOS] config write 'com.netdumasoftware.hybridvpn.settings', Monday, April 01, 2019 01:48:49
[DumaOS] Backing up settings to config partition., Monday, April 01, 2019 01:49:00
[DumaOS] config write 'com.netdumasoftware.hybridvpn.settings', Monday, April 01, 2019 01:49:00
[DumaOS] Backing up settings to config partition., Monday, April 01, 2019 01:49:09
[DumaOS] config write 'com.netdumasoftware.hybridvpn.settings', Monday, April 01, 2019 01:49:09
[DumaOS] DHCP lease change., Monday, April 01, 2019 01:50:52
[DumaOS] config write 'com.netdumsoftware.geofilter.settings', Monday, April 01, 2019 01:51:24
[DumaOS] applying qos for zone wan, Monday, April 01, 2019 01:51:25
[DumaOS] applying qos for zone lan, Monday, April 01, 2019 01:51:25
[DumaOS] applying qos for zone wan, Monday, April 01, 2019 01:51:26
[DumaOS] applying qos for zone lan, Monday, April 01, 2019 01:51:27
[DumaOS] config write 'com.netdumsoftware.geofilter.settings', Monday, April 01, 2019 01:51:35
[DumaOS] config write 'com.netdumasoftware.qos.settings', Monday, April 01, 2019 01:51:35
[DumaOS] applying qos for zone wan, Monday, April 01, 2019 01:51:35
[DumaOS] applying qos for zone lan, Monday, April 01, 2019 01:51:36
[DumaOS] config write 'com.netdumasoftware.devicemanager.database', Monday, April 01, 2019 01:51:37
[DumaOS] DHCP new event., Monday, April 01, 2019 01:54:13
[DumaOS] DHCP lease change., Monday, April 01, 2019 01:54:13
[DumaOS] Exception caught in 'com.netdumasoftware.devicemanager': ERROR: Ubus error: 4 stack traceback: ^I?: in function '__new,_' ^I?: in function '?' ^I?: in function <?:469> ^I(tail call): ? ^I?: in function 'long_call' ^I?: in function <?:204> ^I?: in function 'mass_mark_type' ^I?: in function <?:251> ^I?: in function 'on_type_change' ^I?: in function 'interface_update' ^I?: in function '?' ^I... ^I[C]: in function 'run' ^I?: in function <?:345> ^I[C]: in function 'xpcall' ^I?: in function 'try' ^I?: in function <?:261> ^I(tail call): ? ^I/dumaos/api/cli.lua:48: in function </dumaos/api/cli.lua:30> ^I[C]: in function 'xpcall' ^I/dumaos/api/cli.lua:59: in main chunk ^I[C]: ? Monday, April 01, 2019 01:55:06
[DumaOS] recovering state com.netdumasoftware.dpiclass, Monday, April 01, 2019 01:55:06
[DumaOS] App 'com.netdumasoftware.devicemanager' cleanup finished, Monday, April 01, 2019 01:55:07
[DumaOS] recovering state com.netdumasoftware.devicemanager, Monday, April 01, 2019 01:55:07
[DumaOS] subscribe to 'com.netdumasoftware.neighwatch' from 'com.netdumasoftware.devicemanager', Monday, April 01, 2019 01:55:07
[DumaOS] pending subscription for package 'com.netdumasoftware.dpiclass', Monday, April 01, 2019 01:55:07
[DumaOS] Exception caught in 'com.netdumasoftware.devicemanager': ERROR: No slots available. stack traceback: ^I?: in function ,__new__' ^I?: in function '?' ^I?: in function <?:469> ^I(tail call): ? ^I?: in function 'long_call' ^I?: in function <?:343> ^I[C]: in function 'xpcall' ^I?: in function 'try' ^I?: in function 'init' ^I?: in function '?' ^I?: in function <?:345> ^I[C]: in function 'xpcall' ^I?: in function 'try' ^I?: in function <?:261> ^I(tail call): ? ^I/dumaos/api/cli.lua:48: in function </dumaos/api/cli.lua:30> ^I[C]: in function 'xpcall' ^I/dumaos/api/cli.lua:59: in main chunk ^I[C]: ? Monday, April 01, 2019 01:55:07
[DumaOS] Long call 'del_rule' exception 'ERROR: Rule not found in chain stack traceback: ^I?: in function '__new__' ^I?: in fun,tion '?' ^I?: in function <?:469> ^I(tail call): ? ^I?: in main chunk ^I[C]: in function 'require' ^I?: in main chunk ^I[C]: in function 'require' ^I?: in main chunk ^I?: in function <?:261> ^I(tail call): ? ^I/dumaos/api/cli.lua:48: in function </dumaos/api/cli.lua:30> ^I[C]: in function 'xpcall' ^I/dumaos/api/cli.lua:59: in main chunk ^I[C]: ?' Monday, April 01, 2019 01:55:07
[DumaOS] Exception caught in cleanup 'com.netdumasoftware.devicemanager': ERROR: Rule not found in chain stack traceback: ^I?: ,n function '__new__' ^I?: in function '?' ^I?: in function <?:469> ^I(tail call): ? ^I?: in function 'long_call' ^I?: in function '?' ^I?: in function '?' ^I?: in function 'cleanup' ^I?: in function '?' ^I?: in function <?:367> ^I[C]: in function 'xpcall' ^I?: in function 'try' ^I?: in function <?:364> ^I?: in function 'try' ^I?: in function <?:261> ^I(tail call): ? ^I/dumaos/api/cli.lua:48: in function </dumaos/api/cli.lua:30> ^I[C]: in function 'xpcall' ^I/dumaos/api/cli.lua:59: in main chunk ^I[C]: ? Monday, April 01, 2019 01:55:07
[DumaOS] Restarting 'com.netdumasoftware.devicemanager' for 1 time, Monday, April 01, 2019 01:55:07
[DumaOS] subscribe to 'com.netdumasoftware.neighwatch' from 'com.netdumasoftware.devicemanager', Monday, April 01, 2019 01:55:07
[DumaOS] pending subscription for package 'com.netdumasoftware.dpiclass', Monday, April 01, 2019 01:55:07
[DumaOS] Long call 'dualreserve' exception 'ERROR: No slots available. stack traceback: ^I?: in function '__new__' ^I?: in func,ion '?' ^I?: in function <?:469> ^I(tail call): ? ^I?: in function 'dual_reserve' ^I?: in function '?' ^I?: in function <?:48> ^I[C]: in function 'xpcall' ^I?: in function 'try' ^I?: in function <?:46> ^I[C]: in function 'run' ^I?: in function <?:345> ^I[C]: in function 'xpcall' ^I?: in function 'try' ^I?: in function <?:261> ^I(tail call): ? ^I/dumaos/api/cli.lua:48: in function </dumaos/api/cli.lua:30> ^I[C]: in function 'xpcall' ^I/dumaos/api/cli.lua:59: in main chunk ^I[C]: ?' Monday, April 01, 2019 01:55:07
[DumaOS] Exception caught in 'com.netdumasoftware.devicemanager': ERROR: No slots available. stack traceback: ^I?: in function ,__new__' ^I?: in function '?' ^I?: in function <?:469> ^I(tail call): ? ^I?: in function 'long_call' ^I?: in function <?:343> ^I[C]: in function 'xpcall' ^I?: in function 'try' ^I?: in function 'init' ^I?: in function '?' ^I?: in function <?:345> ^I[C]: in function 'xpcall' ^I?: in function 'try' ^I?: in function <?:261> ^I(tail call): ? ^I/dumaos/api/cli.lua:48: in function </dumaos/api/cli.lua:30> ^I[C]: in function 'xpcall' ^I/dumaos/api/cli.lua:59: in main chunk ^I[C]: ? Monday, April 01, 2019 01:55:07
[DumaOS] Long call 'del_rule' exception 'ERROR: Rule not found in chain stack traceback: ^I?: in function '__new__' ^I?: in fun,tion '?' ^I?: in function <?:469> ^I(tail call): ? ^I?: in main chunk ^I[C]: in function 'require' ^I?: in main chunk ^I[C]: in function 'require' ^I?: in main chunk ^I?: in function <?:261> ^I(tail call): ? ^I/dumaos/api/cli.lua:48: in function </dumaos/api/cli.lua:30> ^I[C]: in function 'xpcall' ^I/dumaos/api/cli.lua:59: in main chunk ^I[C]: ?' Monday, April 01, 2019 01:55:07
[DumaOS] Exception caught in cleanup 'com.netdumasoftware.devicemanager': ERROR: Rule not found in chain stack traceback: ^I?: ,n function '__new__' ^I?: in function '?' ^I?: in function <?:469> ^I(tail call): ? ^I?: in function 'long_call' ^I?: in function '?' ^I?: in function '?' ^I?: in function 'cleanup' ^I?: in function '?' ^I?: in function <?:367> ^I[C]: in function 'xpcall' ^I?: in function 'try' ^I?: in function <?:364> ^I?: in function 'try' ^I?: in function <?:261> ^I(tail call): ? ^I/dumaos/api/cli.lua:48: in function </dumaos/api/cli.lua:30> ^I[C]: in function 'xpcall' ^I/dumaos/api/cli.lua:59: in main chunk ^I[C]: ? Monday, April 01, 2019 01:55:07
[DumaOS] Restarting 'com.netdumasoftware.devicemanager' for 2 time, Monday, April 01, 2019 01:55:07
[DumaOS] subscribe to 'com.netdumasoftware.neighwatch' from 'com.netdumasoftware.devicemanager', Monday, April 01, 2019 01:55:07
[DumaOS] pending subscription for package 'com.netdumasoftware.dpiclass', Monday, April 01, 2019 01:55:07
[DumaOS] Long call 'dualreserve' exception 'ERROR: No slots available. stack traceback: ^I?: in function '__new__' ^I?: in func,ion '?' ^I?: in function <?:469> ^I(tail call): ? ^I?: in function 'dual_reserve' ^I?: in function '?' ^I?: in function <?:48> ^I[C]: in function 'xpcall' ^I?: in function 'try' ^I?: in function <?:46> ^I[C]: in function 'run' ^I?: in function <?:345> ^I[C]: in function 'xpcall' ^I?: in function 'try' ^I?: in function <?:261> ^I(tail call): ? ^I/dumaos/api/cli.lua:48: in function </dumaos/api/cli.lua:30> ^I[C]: in function 'xpcall' ^I/dumaos/api/cli.lua:59: in main chunk ^I[C]: ?' Monday, April 01, 2019 01:55:07
[DumaOS] Exception caught in 'com.netdumasoftware.devicemanager': ERROR: No slots available. stack traceback: ^I?: in function ,__new__' ^I?: in function '?' ^I?: in function <?:469> ^I(tail call): ? ^I?: in function 'long_call' ^I?: in function <?:343> ^I[C]: in function 'xpcall' ^I?: in function 'try' ^I?: in function 'init' ^I?: in function '?' ^I?: in function <?:345> ^I[C]: in function 'xpcall' ^I?: in function 'try' ^I?: in function <?:261> ^I(tail call): ? ^I/dumaos/api/cli.lua:48: in function </dumaos/api/cli.lua:30> ^I[C]: in function 'xpcall' ^I/dumaos/api/cli.lua:59: in main chunk ^I[C]: ? Monday, April 01, 2019 01:55:07
[DumaOS] Long call 'del_rule' exception 'ERROR: Rule not found in chain stack traceback: ^I?: in function '__new__' ^I?: in fun,tion '?' ^I?: in function <?:469> ^I(tail call): ? ^I?: in main chunk ^I[C]: in function 'require' ^I?: in main chunk ^I[C]: in function 'require' ^I?: in main chunk ^I?: in function <?:261> ^I(tail call): ? ^I/dumaos/api/cli.lua:48: in function </dumaos/api/cli.lua:30> ^I[C]: in function 'xpcall' ^I/dumaos/api/cli.lua:59: in main chunk ^I[C]: ?' Monday, April 01, 2019 01:55:07
[DumaOS] Exception caught in cleanup 'com.netdumasoftware.devicemanager': ERROR: Rule not found in chain stack traceback: ^I?: ,n function '__new__' ^I?: in function '?' ^I?: in function <?:469> ^I(tail call): ? ^I?: in function 'long_call' ^I?: in function '?' ^I?: in function '?' ^I?: in function 'cleanup' ^I?: in function '?' ^I?: in function <?:367> ^I[C]: in function 'xpcall' ^I?: in function 'try' ^I?: in function <?:364> ^I?: in function 'try' ^I?: in function <?:261> ^I(tail call): ? ^I/dumaos/api/cli.lua:48: in function </dumaos/api/cli.lua:30> ^I[C]: in function 'xpcall' ^I/dumaos/api/cli.lua:59: in main chunk ^I[C]: ? Monday, April 01, 2019 01:55:07
[DumaOS] Giving up restarting 'com.netdumasoftware.devicemanager', Monday, April 01, 2019 01:55:07
[DumaOS] applying qos for zone wan, Monday, April 01, 2019 01:57:26
[DumaOS] applying qos for zone lan, Monday, April 01, 2019 01:57:27
 

Share this post


Link to post
Share on other sites
1 hour ago, Netduma Fraser said:

Is .8 performing worse for you than .10?

yep ever since I downgraded it from 10, And even doing a factory reset I would see this in the Router Log File, I hope 10 didn't break or brick this router partially 🙄 ANd the when going thru the setupinterfacee setting everything back up, it was taking forever just to get to the next page, and I'm hard wired to the router.

Share this post


Link to post
Share on other sites
1 hour ago, Netduma Fraser said:

Is .8 performing worse for you than .10?

here's what it's doing now in the log since the downgrade and factory default reset:

[DumaOS] Marking device that is marked 192.168.1.9 8 10., Tuesday, April 02, 2019 12:35:20
[DumaOS] Marking device that is marked 192.168.1.7 7 8., Tuesday, April 02, 2019 12:35:21
[DumaOS] Marking device that is marked 192.168.1.6 10 7., Tuesday, April 02, 2019 12:35:23
[DumaOS] Marking device that is marked 192.168.1.2 4 2., Tuesday, April 02, 2019 12:36:12
[DumaOS] Marking device that is marked 192.168.1.7 7 8., Tuesday, April 02, 2019 12:36:14
[DumaOS] Marking device that is marked 192.168.1.9 8 10., Tuesday, April 02, 2019 12:36:20
[DumaOS] Marking device that is marked 192.168.1.6 10 7., Tuesday, April 02, 2019 12:36:23
[DumaOS] DHCP new event., Tuesday, April 02, 2019 12:36:49
[DumaOS] DHCP lease change., Tuesday, April 02, 2019 12:36:49
[DHCP IP: 192.168.1.14][Device Name: ANDROID-9F4ADA825FB003FF] to MAC address c0:bd:d1:ac:6d:09, Tuesday, April 02, 2019 12:36:49
[DumaOS] Marking device that is marked 192.168.1.7 7 8., Tuesday, April 02, 2019 12:37:10
[DumaOS] Marking device that is marked 192.168.1.9 8 10., Tuesday, April 02, 2019 12:37:20
[DumaOS] Marking device that is marked 192.168.1.6 10 7., Tuesday, April 02, 2019 12:37:23
[DumaOS] Marking device that is marked 192.168.1.7 7 8., Tuesday, April 02, 2019 12:38:04
[DumaOS] Marking device that is marked 192.168.1.9 8 10., Tuesday, April 02, 2019 12:38:20
[DumaOS] Marking device that is marked 192.168.1.6 10 7., Tuesday, April 02, 2019 12:38:23
[DumaOS] Marking device that is marked 192.168.1.2 4 2., Tuesday, April 02, 2019 12:38:28
[DumaOS] Marking device that is marked 192.168.1.2 4 2., Tuesday, April 02, 2019 12:38:35
[DumaOS] Marking device that is marked 192.168.1.7 7 8., Tuesday, April 02, 2019 12:38:59
[DumaOS] Marking device that is marked 192.168.1.2 4 2., Tuesday, April 02, 2019 12:39:16
[DumaOS] Marking device that is marked 192.168.1.9 8 10., Tuesday, April 02, 2019 12:39:20
[DumaOS] Marking device that is marked 192.168.1.6 10 7., Tuesday, April 02, 2019 12:39:23
[DumaOS] Marking device that is marked 192.168.1.7 7 8., Tuesday, April 02, 2019 12:39:54
[DumaOS] Marking device that is marked 192.168.1.9 8 10., Tuesday, April 02, 2019 12:40:20
[DumaOS] Marking device that is marked 192.168.1.6 10 7., Tuesday, April 02, 2019 12:40:23
[DumaOS] Marking device that is marked 192.168.1.2 4 2., Tuesday, April 02, 2019 12:40:48
[DumaOS] Marking device that is marked 192.168.1.7 7 8., Tuesday, April 02, 2019 12:40:50
[DumaOS] Marking device that is marked 192.168.1.9 8 10., Tuesday, April 02, 2019 12:41:20
[DumaOS] Marking device that is marked 192.168.1.6 10 7., Tuesday, April 02, 2019 12:41:23
[DumaOS] Marking device that is marked 192.168.1.7 7 8., Tuesday, April 02, 2019 12:41:59
[DumaOS] Marking device that is marked 192.168.1.9 8 10., Tuesday, April 02, 2019 12:42:20
[DumaOS] Marking device that is marked 192.168.1.6 10 7., Tuesday, April 02, 2019 12:42:23
[DumaOS] Marking device that is marked 192.168.1.2 4 2., Tuesday, April 02, 2019 12:42:29
[DumaOS] Marking device that is marked 192.168.1.7 7 8., Tuesday, April 02, 2019 12:42:59
[DumaOS] Marking device that is marked 192.168.1.9 8 10., Tuesday, April 02, 2019 12:43:20
[DumaOS] Marking device that is marked 192.168.1.6 10 7., Tuesday, April 02, 2019 12:43:23
[DumaOS] Marking device that is marked 192.168.1.7 7 8., Tuesday, April 02, 2019 12:43:59
[DumaOS] Marking device that is marked 192.168.1.9 8 10., Tuesday, April 02, 2019 12:44:20
[DumaOS] Marking device that is marked 192.168.1.2 4 2., Tuesday, April 02, 2019 12:44:22
[DumaOS] Marking device that is marked 192.168.1.6 10 7., Tuesday, April 02, 2019 12:44:23
[DumaOS] Marking device that is marked 192.168.1.7 7 8., Tuesday, April 02, 2019 12:44:59
[DumaOS] Marking device that is marked 192.168.1.9 8 10., Tuesday, April 02, 2019 12:45:20
[DumaOS] Marking device that is marked 192.168.1.6 10 7., Tuesday, April 02, 2019 12:45:23
[DumaOS] Marking device that is marked 192.168.1.2 4 2., Tuesday, April 02, 2019 12:45:35
[DumaOS] Marking device that is marked 192.168.1.7 7 8., Tuesday, April 02, 2019 12:45:59
[DumaOS] Marking device that is marked 192.168.1.9 8 10., Tuesday, April 02, 2019 12:46:20
[DumaOS] Marking device that is marked 192.168.1.6 10 7., Tuesday, April 02, 2019 12:46:23
[DumaOS] Marking device that is marked 192.168.1.7 7 8., Tuesday, April 02, 2019 12:46:59
[DumaOS] Marking device that is marked 192.168.1.9 8 10., Tuesday, April 02, 2019 12:47:20
[DumaOS] Marking device that is marked 192.168.1.2 4 2., Tuesday, April 02, 2019 12:47:22
[DumaOS] Marking device that is marked 192.168.1.6 10 7., Tuesday, April 02, 2019 12:47:23
[DumaOS] Marking device that is marked 192.168.1.7 7 8., Tuesday, April 02, 2019 12:47:59
[DumaOS] Marking device that is marked 192.168.1.9 8 10., Tuesday, April 02, 2019 12:48:20
[DumaOS] Marking device that is marked 192.168.1.6 10 7., Tuesday, April 02, 2019 12:48:23
[DumaOS] Marking device that is marked 192.168.1.2 4 2., Tuesday, April 02, 2019 12:48:29
[DumaOS] Marking device that is marked 192.168.1.7 7 8., Tuesday, April 02, 2019 12:48:54
[DumaOS] Marking device that is marked 192.168.1.9 8 10., Tuesday, April 02, 2019 12:49:20
[DumaOS] Marking device that is marked 192.168.1.6 10 7., Tuesday, April 02, 2019 12:49:23
[DumaOS] Marking device that is marked 192.168.1.4 2 4., Tuesday, April 02, 2019 12:49:58
[DumaOS] Marking device that is marked 192.168.1.7 7 8., Tuesday, April 02, 2019 12:49:59
[DumaOS] Marking device that is marked 192.168.1.2 4 2., Tuesday, April 02, 2019 12:50:00
[DumaOS] Marking device that is marked 192.168.1.9 8 10., Tuesday, April 02, 2019 12:50:20
[DumaOS] Marking device that is marked 192.168.1.6 10 7., Tuesday, April 02, 2019 12:50:23
[DumaOS] Marking device that is marked 192.168.1.7 7 8., Tuesday, April 02, 2019 12:50:54
[DumaOS] DHCP new event., Tuesday, April 02, 2019 12:51:15
[DumaOS] DHCP lease change., Tuesday, April 02, 2019 12:51:15
[DHCP IP: 192.168.1.14][Device Name: ANDROID-9F4ADA825FB003FF] to MAC address c0:bd:d1:ac:6d:09, Tuesday, April 02, 2019 12:51:15
[DumaOS] Marking device that is marked 192.168.1.9 8 10., Tuesday, April 02, 2019 12:51:20
[DumaOS] Marking device that is marked 192.168.1.6 10 7., Tuesday, April 02, 2019 12:51:23
[DumaOS] Marking device that is marked 192.168.1.2 4 2., Tuesday, April 02, 2019 12:51:32
[DumaOS] Marking device that is marked 192.168.1.7 7 8., Tuesday, April 02, 2019 12:51:51
[DumaOS] Marking device that is marked 192.168.1.9 8 10., Tuesday, April 02, 2019 12:52:20
[DumaOS] Marking device that is marked 192.168.1.6 10 7., Tuesday, April 02, 2019 12:52:23
[DumaOS] Marking device that is marked 192.168.1.7 7 8., Tuesday, April 02, 2019 12:52:59
[DumaOS] Marking device that is marked 192.168.1.2 4 2., Tuesday, April 02, 2019 12:53:04
[DumaOS] Marking device that is marked 192.168.1.9 8 10., Tuesday, April 02, 2019 12:53:20
[DumaOS] Marking device that is marked 192.168.1.6 10 7., Tuesday, April 02, 2019 12:53:23
[DumaOS] Marking device that is marked 192.168.1.7 7 8., Tuesday, April 02, 2019 12:53:59
[DumaOS] Marking device that is marked 192.168.1.9 8 10., Tuesday, April 02, 2019 12:54:20
[DumaOS] Marking device that is marked 192.168.1.6 10 7., Tuesday, April 02, 2019 12:54:23
[DumaOS] Marking device that is marked 192.168.1.2 4 2., Tuesday, April 02, 2019 12:54:36
[DumaOS] Marking device that is marked 192.168.1.7 7 8., Tuesday, April 02, 2019 12:54:59
[DumaOS] Marking device that is marked 192.168.1.9 8 10., Tuesday, April 02, 2019 12:55:20
[DumaOS] Marking device that is marked 192.168.1.6 10 7., Tuesday, April 02, 2019 12:55:23
[DumaOS] Marking device that is marked 192.168.1.7 7 8., Tuesday, April 02, 2019 12:55:59
[DumaOS] Marking device that is marked 192.168.1.9 8 10., Tuesday, April 02, 2019 12:56:20
[DumaOS] Marking device that is marked 192.168.1.2 4 2., Tuesday, April 02, 2019 12:56:22
[DumaOS] Marking device that is marked 192.168.1.6 10 7., Tuesday, April 02, 2019 12:56:23
[DumaOS] Marking device that is marked 192.168.1.7 7 8., Tuesday, April 02, 2019 12:56:59
[DumaOS] Marking device that is marked 192.168.1.9 8 10., Tuesday, April 02, 2019 12:57:20
[DumaOS] Marking device that is marked 192.168.1.6 10 7., Tuesday, April 02, 2019 12:57:23
[DumaOS] Marking device that is marked 192.168.1.2 4 2., Tuesday, April 02, 2019 12:57:41
[DumaOS] Marking device that is marked 192.168.1.7 7 8., Tuesday, April 02, 2019 12:57:53
[DumaOS] Marking device that is marked 192.168.1.9 8 10., Tuesday, April 02, 2019 12:58:20
[DumaOS] Marking device that is marked 192.168.1.6 10 7., Tuesday, April 02, 2019 12:58:23
[DumaOS] Marking device that is marked 192.168.1.7 7 8., Tuesday, April 02, 2019 12:59:00
[DumaOS] Marking device that is marked 192.168.1.9 8 10., Tuesday, April 02, 2019 12:59:20
[DumaOS] Marking device that is marked 192.168.1.6 10 7., Tuesday, April 02, 2019 12:59:23
[DumaOS] Marking device that is marked 192.168.1.2 4 2., Tuesday, April 02, 2019 12:59:29
[DumaOS] Marking device that is marked 192.168.1.7 7 8., Tuesday, April 02, 2019 13:00:00
[DumaOS] Marking device that is marked 192.168.1.9 8 10., Tuesday, April 02, 2019 13:00:20
[DumaOS] Marking device that is marked 192.168.1.6 10 7., Tuesday, April 02, 2019 13:00:23
[DumaOS] Marking device that is marked 192.168.1.2 4 2., Tuesday, April 02, 2019 13:00:44
[DumaOS] Marking device that is marked 192.168.1.7 7 8., Tuesday, April 02, 2019 13:01:00
[DumaOS] Marking device that is marked 192.168.1.9 8 10., Tuesday, April 02, 2019 13:01:20
[DumaOS] Marking device that is marked 192.168.1.6 10 7., Tuesday, April 02, 2019 13:01:23
[DumaOS] Marking device that is marked 192.168.1.7 7 8., Tuesday, April 02, 2019 13:01:59
[DumaOS] Marking device that is marked 192.168.1.2 4 2., Tuesday, April 02, 2019 13:02:16
[DumaOS] Marking device that is marked 192.168.1.9 8 10., Tuesday, April 02, 2019 13:02:20
[DumaOS] Marking device that is marked 192.168.1.6 10 7., Tuesday, April 02, 2019 13:02:23
[DumaOS] Marking device that is marked 192.168.1.2 4 2., Tuesday, April 02, 2019 13:02:31
[DumaOS] Marking device that is marked 192.168.1.7 7 8., Tuesday, April 02, 2019 13:02:50
[DumaOS] Marking device that is marked 192.168.1.9 8 10., Tuesday, April 02, 2019 13:03:20
[DumaOS] Marking device that is marked 192.168.1.6 10 7., Tuesday, April 02, 2019 13:03:23
[DumaOS] Marking device that is marked 192.168.1.7 7 8., Tuesday, April 02, 2019 13:03:44
[DumaOS] Marking device that is marked 192.168.1.2 4 2., Tuesday, April 02, 2019 13:04:20
[DumaOS] Marking device that is marked 192.168.1.9 8 10., Tuesday, April 02, 2019 13:04:20
[DumaOS] Marking device that is marked 192.168.1.6 10 7., Tuesday, April 02, 2019 13:04:23
[DumaOS] Marking device that is marked 192.168.1.7 7 8., Tuesday, April 02, 2019 13:04:41
[DumaOS] Marking device that is marked 192.168.1.9 8 10., Tuesday, April 02, 2019 13:05:20
[DumaOS] Marking device that is marked 192.168.1.6 10 7., Tuesday, April 02, 2019 13:05:23
[DumaOS] Marking device that is marked 192.168.1.2 4 2., Tuesday, April 02, 2019 13:05:26
[DumaOS] DHCP new event., Tuesday, April 02, 2019 13:05:42
[DumaOS] DHCP lease change., Tuesday, April 02, 2019 13:05:42
[DHCP IP: 192.168.1.14][Device Name: ANDROID-9F4ADA825FB003FF] to MAC address c0:bd:d1:ac:6d:09, Tuesday, April 02, 2019 13:05:42
[DumaOS] Marking device that is marked 192.168.1.7 7 8., Tuesday, April 02, 2019 13:05:58
[DumaOS] Marking device that is marked 192.168.1.9 8 10., Tuesday, April 02, 2019 13:06:20
[DumaOS] Marking device that is marked 192.168.1.6 10 7., Tuesday, April 02, 2019 13:06:23
[DumaOS] Marking device that is marked 192.168.1.7 7 8., Tuesday, April 02, 2019 13:06:59
[DumaOS] Marking device that is marked 192.168.1.2 4 2., Tuesday, April 02, 2019 13:07:11
[DumaOS] Marking device that is marked 192.168.1.9 8 10., Tuesday, April 02, 2019 13:07:20
[DumaOS] Marking device that is marked 192.168.1.6 10 7., Tuesday, April 02, 2019 13:07:23
[DumaOS] Marking device that is marked 192.168.1.7 7 8., Tuesday, April 02, 2019 13:07:59
[DumaOS] Marking device that is marked 192.168.1.9 8 10., Tuesday, April 02, 2019 13:08:20
[DumaOS] Marking device that is marked 192.168.1.6 10 7., Tuesday, April 02, 2019 13:08:23
[DumaOS] Marking device that is marked 192.168.1.2 4 2., Tuesday, April 02, 2019 13:08:29
[DumaOS] Marking device that is marked 192.168.1.7 7 8., Tuesday, April 02, 2019 13:08:59
[DumaOS] Marking device that is marked 192.168.1.9 8 10., Tuesday, April 02, 2019 13:09:20
[DumaOS] Marking device that is marked 192.168.1.6 10 7., Tuesday, April 02, 2019 13:09:23
[DumaOS] Marking device that is marked 192.168.1.7 7 8., Tuesday, April 02, 2019 13:09:58
[DumaOS] Marking device that is marked 192.168.1.9 8 10., Tuesday, April 02, 2019 13:10:20
[DumaOS] Marking device that is marked 192.168.1.6 10 7., Tuesday, April 02, 2019 13:10:23
[DumaOS] Marking device that is marked 192.168.1.7 7 8., Tuesday, April 02, 2019 13:10:54
[DumaOS] Marking device that is marked 192.168.1.2 4 2., Tuesday, April 02, 2019 13:10:59
[DumaOS] Marking device that is marked 192.168.1.9 8 10., Tuesday, April 02, 2019 13:11:21
[DumaOS] Marking device that is marked 192.168.1.6 10 7., Tuesday, April 02, 2019 13:11:23
[DumaOS] Marking device that is marked 192.168.1.7 7 8., Tuesday, April 02, 2019 13:11:50
[DumaOS] Marking device that is marked 192.168.1.2 4 2., Tuesday, April 02, 2019 13:12:07
[DumaOS] Marking device that is marked 192.168.1.9 8 10., Tuesday, April 02, 2019 13:12:20
[DumaOS] Marking device that is marked 192.168.1.6 10 7., Tuesday, April 02, 2019 13:12:23
[DumaOS] Marking device that is marked 192.168.1.7 7 8., Tuesday, April 02, 2019 13:13:00
[DumaOS] Marking device that is marked 192.168.1.9 8 10., Tuesday, April 02, 2019 13:13:20
[DumaOS] Marking device that is marked 192.168.1.6 10 7., Tuesday, April 02, 2019 13:13:23
[DumaOS] Marking device that is marked 192.168.1.2 4 2., Tuesday, April 02, 2019 13:13:39
[DumaOS] Marking device that is marked 192.168.1.7 7 8., Tuesday, April 02, 2019 13:13:59
[DumaOS] Marking device that is marked 192.168.1.9 8 10., Tuesday, April 02, 2019 13:14:20
[DumaOS] Marking device that is marked 192.168.1.6 10 7., Tuesday, April 02, 2019 13:14:23
[DumaOS] Marking device that is marked 192.168.1.7 7 8., Tuesday, April 02, 2019 13:14:59
[DumaOS] Marking device that is marked 192.168.1.2 4 2., Tuesday, April 02, 2019 13:15:12
[DumaOS] Marking device that is marked 192.168.1.9 8 10., Tuesday, April 02, 2019 13:15:20
[DumaOS] Marking device that is marked 192.168.1.6 10 7., Tuesday, April 02, 2019 13:15:23
[DumaOS] Marking device that is marked 192.168.1.7 7 8., Tuesday, April 02, 2019 13:15:59
[DumaOS] Marking device that is marked 192.168.1.9 8 10., Tuesday, April 02, 2019 13:16:20
[DumaOS] Marking device that is marked 192.168.1.6 10 7., Tuesday, April 02, 2019 13:16:23
[DumaOS] Marking device that is marked 192.168.1.2 4 2., Tuesday, April 02, 2019 13:16:43
[DumaOS] Marking device that is marked 192.168.1.7 7 8., Tuesday, April 02, 2019 13:16:56
[DumaOS] Marking device that is marked 192.168.1.9 8 10., Tuesday, April 02, 2019 13:17:20
[DumaOS] Marking device that is marked 192.168.1.6 10 7., Tuesday, April 02, 2019 13:17:23
[DumaOS] Marking device that is marked 192.168.1.7 7 8., Tuesday, April 02, 2019 13:17:59
[DumaOS] Marking device that is marked 192.168.1.2 4 2., Tuesday, April 02, 2019 13:18:15
[DumaOS] Marking device that is marked 192.168.1.9 8 10., Tuesday, April 02, 2019 13:18:20
[DumaOS] Marking device that is marked 192.168.1.6 10 7., Tuesday, April 02, 2019 13:18:23
[DumaOS] Marking device that is marked 192.168.1.7 7 8., Tuesday, April 02, 2019 13:18:58
[DumaOS] Marking device that is marked 192.168.1.9 8 10., Tuesday, April 02, 2019 13:19:20
[DumaOS] Marking device that is marked 192.168.1.6 10 7., Tuesday, April 02, 2019 13:19:23
[DumaOS] Marking device that is marked 192.168.1.2 4 2., Tuesday, April 02, 2019 13:19:47
[DumaOS] Marking device that is marked 192.168.1.7 7 8., Tuesday, April 02, 2019 13:19:59
[DumaOS] DHCP new event., Tuesday, April 02, 2019 13:20:08
[DumaOS] DHCP lease change., Tuesday, April 02, 2019 13:20:08
[DHCP IP: 192.168.1.14][Device Name: ANDROID-9F4ADA825FB003FF] to MAC address c0:bd:d1:ac:6d:09, Tuesday, April 02, 2019 13:20:08
[DumaOS] Marking device that is marked 192.168.1.9 8 10., Tuesday, April 02, 2019 13:20:20
[DumaOS] Marking device that is marked 192.168.1.6 10 7., Tuesday, April 02, 2019 13:20:23
[DumaOS] Marking device that is marked 192.168.1.7 7 8., Tuesday, April 02, 2019 13:20:58
[DumaOS] Marking device that is marked 192.168.1.2 4 2., Tuesday, April 02, 2019 13:21:19
[DumaOS] Marking device that is marked 192.168.1.9 8 10., Tuesday, April 02, 2019 13:21:21
[DumaOS] Marking device that is marked 192.168.1.6 10 7., Tuesday, April 02, 2019 13:21:23
[DumaOS] Marking device that is marked 192.168.1.7 7 8., Tuesday, April 02, 2019 13:21:59
[DumaOS] Marking device that is marked 192.168.1.9 8 10., Tuesday, April 02, 2019 13:22:20
[DumaOS] Marking device that is marked 192.168.1.6 10 7., Tuesday, April 02, 2019 13:22:23
[DumaOS] Marking device that is marked 192.168.1.2 4 2., Tuesday, April 02, 2019 13:22:51
[DumaOS] Marking device that is marked 192.168.1.7 7 8., Tuesday, April 02, 2019 13:22:59
[DumaOS] Marking device that is marked 192.168.1.4 2 4., Tuesday, April 02, 2019 13:23:09
[DumaOS] Marking device that is marked 192.168.1.9 8 10., Tuesday, April 02, 2019 13:23:20
[DumaOS] Marking device that is marked 192.168.1.6 10 7., Tuesday, April 02, 2019 13:23:23
[DumaOS] DHCP new event., Tuesday, April 02, 2019 13:23:54
[DumaOS] DHCP lease change., Tuesday, April 02, 2019 13:23:54
[DHCP IP: 192.168.1.2][Device Name: CORSAIR-PC] to MAC address e0:d5:5e:23:4f:75, Tuesday, April 02, 2019 13:23:54
[DumaOS] Marking device that is marked 192.168.1.2 4 2., Tuesday, April 02, 2019 13:23:55
[DumaOS] DHCP new event., Tuesday, April 02, 2019 13:23:55
[DumaOS] DHCP lease change., Tuesday, April 02, 2019 13:23:55
[DHCP IP: 192.168.1.2][Device Name: CORSAIR-PC] to MAC address e0:d5:5e:23:4f:75, Tuesday, April 02, 2019 13:23:55
[DumaOS] Marking device that is marked 192.168.1.2 4 2., Tuesday, April 02, 2019 13:23:56
[DumaOS] Marking device that is marked 192.168.1.7 7 8., Tuesday, April 02, 2019 13:23:59
[DumaOS] Marking device that is marked 192.168.1.9 8 10., Tuesday, April 02, 2019 13:24:21
[DumaOS] Marking device that is marked 192.168.1.6 10 7., Tuesday, April 02, 2019 13:24:23
[DumaOS] Marking device that is marked 192.168.1.7 7 8., Tuesday, April 02, 2019 13:24:59
[DumaOS] Marking device that is marked 192.168.1.2 4 2., Tuesday, April 02, 2019 13:25:08
[DumaOS] Marking device that is marked 192.168.1.2 4 2., Tuesday, April 02, 2019 13:25:13
[DumaOS] Marking device that is marked 192.168.1.9 8 10., Tuesday, April 02, 2019 13:25:20
[DumaOS] Marking device that is marked 192.168.1.6 10 7., Tuesday, April 02, 2019 13:25:23
[DumaOS] Marking device that is marked 192.168.1.2 4 2., Tuesday, April 02, 2019 13:25:55
[DumaOS] Marking device that is marked 192.168.1.7 7 8., Tuesday, April 02, 2019 13:25:59
[DumaOS] Marking device that is marked 192.168.1.9 8 10., Tuesday, April 02, 2019 13:26:20
[DumaOS] Marking device that is marked 192.168.1.6 10 7., Tuesday, April 02, 2019 13:26:23
[DumaOS] Marking device that is marked 192.168.1.7 7 8., Tuesday, April 02, 2019 13:26:50
[DumaOS] Marking device that is marked 192.168.1.9 8 10., Tuesday, April 02, 2019 13:27:20
[DumaOS] Marking device that is marked 192.168.1.6 10 7., Tuesday, April 02, 2019 13:27:24
[DumaOS] Marking device that is marked 192.168.1.2 4 2., Tuesday, April 02, 2019 13:27:27
[Internet connected] IP address: 24.89.53.205, Tuesday, April 02, 2019 13:27:37
[DumaOS] Marking device that is marked 192.168.1.7 7 8., Tuesday, April 02, 2019 13:27:46
[DumaOS] Marking device that is marked 192.168.1.9 8 10., Tuesday, April 02, 2019 13:28:20
[DumaOS] Marking device that is marked 192.168.1.6 10 7., Tuesday, April 02, 2019 13:28:23
[DumaOS] Marking device that is marked 192.168.1.7 7 8., Tuesday, April 02, 2019 13:28:42
[DumaOS] Marking device that is marked 192.168.1.2 4 2., Tuesday, April 02, 2019 13:28:59
[DumaOS] Marking device that is marked 192.168.1.9 8 10., Tuesday, April 02, 2019 13:29:20
[DumaOS] Marking device that is marked 192.168.1.6 10 7., Tuesday, April 02, 2019 13:29:23
[DumaOS] Marking device that is marked 192.168.1.7 7 8., Tuesday, April 02, 2019 13:29:58
[DumaOS] Marking device that is marked 192.168.1.9 8 10., Tuesday, April 02, 2019 13:30:20
[DumaOS] Marking device that is marked 192.168.1.6 10 7., Tuesday, April 02, 2019 13:30:23
[DumaOS] Marking device that is marked 192.168.1.2 4 2., Tuesday, April 02, 2019 13:30:32
[DumaOS] Marking device that is marked 192.168.1.7 7 8., Tuesday, April 02, 2019 13:30:52
[DumaOS] DHCP new event., Tuesday, April 02, 2019 13:31:09
[DumaOS] DHCP lease change., Tuesday, April 02, 2019 13:31:09
[DHCP IP: 192.168.1.2][Device Name: CORSAIR-PC] to MAC address e0:d5:5e:23:4f:75, Tuesday, April 02, 2019 13:31:09
[DumaOS] Marking device that is marked 192.168.1.2 4 2., Tuesday, April 02, 2019 13:31:10
[DumaOS] DHCP new event., Tuesday, April 02, 2019 13:31:11
[DumaOS] DHCP lease change., Tuesday, April 02, 2019 13:31:11
[DHCP IP: 192.168.1.2][Device Name: CORSAIR-PC] to MAC address e0:d5:5e:23:4f:75, Tuesday, April 02, 2019 13:31:11
[DumaOS] Marking device that is marked 192.168.1.2 4 2., Tuesday, April 02, 2019 13:31:12
[DumaOS] Marking device that is marked 192.168.1.9 8 10., Tuesday, April 02, 2019 13:31:20
[DumaOS] Marking device that is marked 192.168.1.6 10 7., Tuesday, April 02, 2019 13:31:23
[DumaOS] Marking device that is marked 192.168.1.7 7 8., Tuesday, April 02, 2019 13:31:59
[DumaOS] Marking device that is marked 192.168.1.9 8 10., Tuesday, April 02, 2019 13:32:20
[DumaOS] Marking device that is marked 192.168.1.2 4 2., Tuesday, April 02, 2019 13:32:23
[DumaOS] Marking device that is marked 192.168.1.6 10 7., Tuesday, April 02, 2019 13:32:24
[DumaOS] DHCP new event., Tuesday, April 02, 2019 13:32:34
[DumaOS] DHCP lease change., Tuesday, April 02, 2019 13:32:34
[DHCP IP: 192.168.1.2][Device Name: CORSAIR-PC] to MAC address e0:d5:5e:23:4f:75, Tuesday, April 02, 2019 13:32:34
[DumaOS] Marking device that is marked 192.168.1.2 4 2., Tuesday, April 02, 2019 13:32:35
[DumaOS] Marking device that is marked 192.168.1.7 7 8., Tuesday, April 02, 2019 13:32:54
[DumaOS] Marking device that is marked 192.168.1.9 8 10., Tuesday, April 02, 2019 13:33:20
[DumaOS] Marking device that is marked 192.168.1.6 10 7., Tuesday, April 02, 2019 13:33:23
[DumaOS] DHCP new event., Tuesday, April 02, 2019 13:33:30
[DumaOS] DHCP lease change., Tuesday, April 02, 2019 13:33:30
[DHCP IP: 192.168.1.2][Device Name: CORSAIR-PC] to MAC address e0:d5:5e:23:4f:75, Tuesday, April 02, 2019 13:33:30
[DumaOS] Marking device that is marked 192.168.1.2 4 2., Tuesday, April 02, 2019 13:33:31
[DumaOS] DHCP new event., Tuesday, April 02, 2019 13:33:31
[DumaOS] DHCP lease change., Tuesday, April 02, 2019 13:33:31
[DHCP IP: 192.168.1.2][Device Name: CORSAIR-PC] to MAC address e0:d5:5e:23:4f:75, Tuesday, April 02, 2019 13:33:31
[DumaOS] Marking device that is marked 192.168.1.2 4 2., Tuesday, April 02, 2019 13:33:31
[DumaOS] Marking device that is marked 192.168.1.7 7 8., Tuesday, April 02, 2019 13:33:59
[DumaOS] Marking device that is marked 192.168.1.9 8 10., Tuesday, April 02, 2019 13:34:20
[DumaOS] Marking device that is marked 192.168.1.6 10 7., Tuesday, April 02, 2019 13:34:23
[DumaOS] DHCP new event., Tuesday, April 02, 2019 13:34:35
[DumaOS] DHCP lease change., Tuesday, April 02, 2019 13:34:35
[DHCP IP: 192.168.1.14][Device Name: ANDROID-9F4ADA825FB003FF] to MAC address c0:bd:d1:ac:6d:09, Tuesday, April 02, 2019 13:34:35
[DumaOS] Marking device that is marked 192.168.1.7 7 8., Tuesday, April 02, 2019 13:34:54
[DumaOS] Marking device that is marked 192.168.1.2 4 2., Tuesday, April 02, 2019 13:35:07
[DumaOS] Marking device that is marked 192.168.1.9 8 10., Tuesday, April 02, 2019 13:35:20
[DumaOS] Marking device that is marked 192.168.1.6 10 7., Tuesday, April 02, 2019 13:35:23
[DumaOS] Marking device that is marked 192.168.1.7 7 8., Tuesday, April 02, 2019 13:35:59
[DumaOS] Marking device that is marked 192.168.1.9 8 10., Tuesday, April 02, 2019 13:36:20
[DumaOS] Marking device that is marked 192.168.1.6 10 7., Tuesday, April 02, 2019 13:36:24
[DumaOS] Marking device that is marked 192.168.1.2 4 2., Tuesday, April 02, 2019 13:36:39
[DumaOS] Marking device that is marked 192.168.1.7 7 8., Tuesday, April 02, 2019 13:36:56
[DumaOS] Marking device that is marked 192.168.1.9 8 10., Tuesday, April 02, 2019 13:37:20
[DumaOS] Marking device that is marked 192.168.1.6 10 7., Tuesday, April 02, 2019 13:37:23
[DumaOS] Marking device that is marked 192.168.1.7 7 8., Tuesday, April 02, 2019 13:37:50
[DumaOS] Marking device that is marked 192.168.1.2 4 2., Tuesday, April 02, 2019 13:38:11
[DumaOS] Marking device that is marked 192.168.1.9 8 10., Tuesday, April 02, 2019 13:38:20
[DumaOS] Marking device that is marked 192.168.1.6 10 7., Tuesday, April 02, 2019 13:38:23
[DumaOS] Marking device that is marked 192.168.1.7 7 8., Tuesday, April 02, 2019 13:38:46
[DumaOS] Marking device that is marked 192.168.1.9 8 10., Tuesday, April 02, 2019 13:39:20
[DumaOS] Marking device that is marked 192.168.1.6 10 7., Tuesday, April 02, 2019 13:39:23
[DumaOS] Marking device that is marked 192.168.1.7 7 8., Tuesday, April 02, 2019 13:39:41
[DumaOS] Marking device that is marked 192.168.1.2 4 2., Tuesday, April 02, 2019 13:39:43
[DumaOS] Marking device that is marked 192.168.1.9 8 10., Tuesday, April 02, 2019 13:40:20
[DumaOS] Marking device that is marked 192.168.1.6 10 7., Tuesday, April 02, 2019 13:40:23
[DumaOS] Marking device that is marked 192.168.1.7 7 8., Tuesday, April 02, 2019 13:40:36
[DumaOS] Marking device that is marked 192.168.1.2 4 2., Tuesday, April 02, 2019 13:41:15
[DumaOS] Marking device that is marked 192.168.1.9 8 10., Tuesday, April 02, 2019 13:41:20
[DumaOS] Marking device that is marked 192.168.1.6 10 7., Tuesday, April 02, 2019 13:41:23
[DumaOS] Marking device that is marked 192.168.1.7 7 8., Tuesday, April 02, 2019 13:41:29
[DumaOS] Marking device that is marked 192.168.1.9 8 10., Tuesday, April 02, 2019 13:42:20
[DumaOS] Marking device that is marked 192.168.1.6 10 7., Tuesday, April 02, 2019 13:42:23
[DumaOS] Marking device that is marked 192.168.1.7 7 8., Tuesday, April 02, 2019 13:42:26
[DumaOS] Marking device that is marked 192.168.1.2 4 2., Tuesday, April 02, 2019 13:42:47
[DumaOS] Marking device that is marked 192.168.1.9 8 10., Tuesday, April 02, 2019 13:43:20
[DumaOS] Marking device that is marked 192.168.1.7 7 8., Tuesday, April 02, 2019 13:43:21
[DumaOS] Marking device that is marked 192.168.1.6 10 7., Tuesday, April 02, 2019 13:43:23
[DumaOS] Marking device that is marked 192.168.1.2 4 2., Tuesday, April 02, 2019 13:44:19
[DumaOS] Marking device that is marked 192.168.1.6 10 7., Tuesday, April 02, 2019 13:44:23
[DumaOS] Marking device that is marked 192.168.1.9 8 10., Tuesday, April 02, 2019 13:44:24
[DumaOS] Marking device that is marked 192.168.1.7 7 8., Tuesday, April 02, 2019 13:44:29
[DumaOS] Marking device that is marked 192.168.1.9 8 10., Tuesday, April 02, 2019 13:45:20
[DumaOS] Marking device that is marked 192.168.1.6 10 7., Tuesday, April 02, 2019 13:45:23
[DumaOS] Marking device that is marked 192.168.1.7 7 8., Tuesday, April 02, 2019 13:45:29
[DumaOS] Marking device that is marked 192.168.1.2 4 2., Tuesday, April 02, 2019 13:45:51
[DumaOS] Marking device that is marked 192.168.1.9 8 10., Tuesday, April 02, 2019 13:46:20
[DumaOS] Marking device that is marked 192.168.1.6 10 7., Tuesday, April 02, 2019 13:46:23
[DumaOS] Marking device that is marked 192.168.1.7 7 8., Tuesday, April 02, 2019 13:46:29
[DumaOS] Marking device that is marked 192.168.1.9 8 10., Tuesday, April 02, 2019 13:47:20
[DumaOS] Marking device that is marked 192.168.1.7 7 8., Tuesday, April 02, 2019 13:47:22
[DumaOS] Marking device that is marked 192.168.1.6 10 7., Tuesday, April 02, 2019 13:47:23
[DumaOS] Marking device that is marked 192.168.1.2 4 2., Tuesday, April 02, 2019 13:47:24
[DumaOS] Marking device that is marked 192.168.1.7 7 8., Tuesday, April 02, 2019 13:48:18
[DumaOS] Marking device that is marked 192.168.1.9 8 10., Tuesday, April 02, 2019 13:48:20
[DumaOS] Marking device that is marked 192.168.1.6 10 7., Tuesday, April 02, 2019 13:48:23
[DumaOS] DHCP new event., Tuesday, April 02, 2019 13:48:30
[DumaOS] DHCP lease change., Tuesday, April 02, 2019 13:48:30
[DHCP IP: 192.168.1.2][Device Name: CORSAIR-PC] to MAC address e0:d5:5e:23:4f:75, Tuesday, April 02, 2019 13:48:30
[DumaOS] Marking device that is marked 192.168.1.2 4 2., Tuesday, April 02, 2019 13:48:31
[DumaOS] DHCP new event., Tuesday, April 02, 2019 13:48:32
[DumaOS] DHCP lease change., Tuesday, April 02, 2019 13:48:32
[DHCP IP: 192.168.1.2][Device Name: CORSAIR-PC] to MAC address e0:d5:5e:23:4f:75, Tuesday, April 02, 2019 13:48:32
[DumaOS] Marking device that is marked 192.168.1.2 4 2., Tuesday, April 02, 2019 13:48:33
[DumaOS] DHCP new event., Tuesday, April 02, 2019 13:49:01
[DumaOS] DHCP lease change., Tuesday, April 02, 2019 13:49:01
[DHCP IP: 192.168.1.14][Device Name: ANDROID-9F4ADA825FB003FF] to MAC address c0:bd:d1:ac:6d:09, Tuesday, April 02, 2019 13:49:01
[DumaOS] Marking device that is marked 192.168.1.7 7 8., Tuesday, April 02, 2019 13:49:12
[DumaOS] Marking device that is marked 192.168.1.2 4 2., Tuesday, April 02, 2019 13:49:15
[DumaOS] Marking device that is marked 192.168.1.9 8 10., Tuesday, April 02, 2019 13:49:20
[DumaOS] Marking device that is marked 192.168.1.6 10 7., Tuesday, April 02, 2019 13:49:23
[DumaOS] Marking device that is marked 192.168.1.7 7 8., Tuesday, April 02, 2019 13:50:09
[DumaOS] Marking device that is marked 192.168.1.4 2 4., Tuesday, April 02, 2019 13:50:17
[DumaOS] Marking device that is marked 192.168.1.9 8 10., Tuesday, April 02, 2019 13:50:20
[DumaOS] Marking device that is marked 192.168.1.6 10 7., Tuesday, April 02, 2019 13:50:23
[DumaOS] Marking device that is marked 192.168.1.2 4 2., Tuesday, April 02, 2019 13:50:27
[DumaOS] Marking device that is marked 192.168.1.7 7 8., Tuesday, April 02, 2019 13:50:59
[DumaOS] Marking device that is marked 192.168.1.9 8 10., Tuesday, April 02, 2019 13:51:20
[DumaOS] Marking device that is marked 192.168.1.6 10 7., Tuesday, April 02, 2019 13:51:23
[DumaOS] Marking device that is marked 192.168.1.7 7 8., Tuesday, April 02, 2019 13:51:58
[DumaOS] Marking device that is marked 192.168.1.2 4 2., Tuesday, April 02, 2019 13:52:00
[DumaOS] Marking device that is marked 192.168.1.9 8 10., Tuesday, April 02, 2019 13:52:20
[DumaOS] Marking device that is marked 192.168.1.6 10 7., Tuesday, April 02, 2019 13:52:23
[DumaOS] Marking device that is marked 192.168.1.7 7 8., Tuesday, April 02, 2019 13:52:59
[DumaOS] Marking device that is marked 192.168.1.9 8 10., Tuesday, April 02, 2019 13:53:20
[DumaOS] Marking device that is marked 192.168.1.6 10 7., Tuesday, April 02, 2019 13:53:23
[DumaOS] Marking device that is marked 192.168.1.2 4 2., Tuesday, April 02, 2019 13:53:31
[DumaOS] Marking device that is marked 192.168.1.7 7 8., Tuesday, April 02, 2019 13:53:58
[DumaOS] Marking device that is marked 192.168.1.9 8 10., Tuesday, April 02, 2019 13:54:20
[DumaOS] Marking device that is marked 192.168.1.6 10 7., Tuesday, April 02, 2019 13:54:23
[DumaOS] Marking device that is marked 192.168.1.7 7 8., Tuesday, April 02, 2019 13:54:59
[DumaOS] Marking device that is marked 192.168.1.2 4 2., Tuesday, April 02, 2019 13:55:03
[DumaOS] Marking device that is marked 192.168.1.9 8 10., Tuesday, April 02, 2019 13:55:20
[DumaOS] Marking device that is marked 192.168.1.6 10 7., Tuesday, April 02, 2019 13:55:23
[DumaOS] Marking device that is marked 192.168.1.7 7 8., Tuesday, April 02, 2019 13:55:59
[DumaOS] Marking device that is marked 192.168.1.9 8 10., Tuesday, April 02, 2019 13:56:20
[DumaOS] Marking device that is marked 192.168.1.6 10 7., Tuesday, April 02, 2019 13:56:23
[DumaOS] Marking device that is marked 192.168.1.2 4 2., Tuesday, April 02, 2019 13:56:35
[DumaOS] Marking device that is marked 192.168.1.7 7 8., Tuesday, April 02, 2019 13:56:59
[DumaOS] Marking device that is marked 192.168.1.9 8 10., Tuesday, April 02, 2019 13:57:20
[DumaOS] Marking device that is marked 192.168.1.6 10 7., Tuesday, April 02, 2019 13:57:23
[DumaOS] Marking device that is marked 192.168.1.7 7 8., Tuesday, April 02, 2019 13:57:50
[DumaOS] Marking device that is marked 192.168.1.2 4 2., Tuesday, April 02, 2019 13:58:07
[DumaOS] Marking device that is marked 192.168.1.9 8 10., Tuesday, April 02, 2019 13:58:20
[DumaOS] Marking device that is marked 192.168.1.6 10 7., Tuesday, April 02, 2019 13:58:23
[DoS Attack: RST Scan] from source: 87.236.16.44, port 80, Tuesday, April 02, 2019 13:58:30
[DumaOS] Marking device that is marked 192.168.1.7 7 8., Tuesday, April 02, 2019 13:58:59
[DumaOS] Marking device that is marked 192.168.1.9 8 10., Tuesday, April 02, 2019 13:59:20
[DumaOS] Marking device that is marked 192.168.1.6 10 7., Tuesday, April 02, 2019 13:59:23
[DumaOS] Marking device that is marked 192.168.1.2 4 2., Tuesday, April 02, 2019 13:59:40
[DumaOS] Marking device that is marked 192.168.1.7 7 8., Tuesday, April 02, 2019 13:59:59
[DumaOS] Marking device that is marked 192.168.1.9 8 10., Tuesday, April 02, 2019 14:00:20
[DumaOS] Marking device that is marked 192.168.1.6 10 7., Tuesday, April 02, 2019 14:00:23
[DumaOS] Marking device that is marked 192.168.1.7 7 8., Tuesday, April 02, 2019 14:00:59
[DumaOS] Marking device that is marked 192.168.1.2 4 2., Tuesday, April 02, 2019 14:01:11
[DumaOS] Marking device that is marked 192.168.1.9 8 10., Tuesday, April 02, 2019 14:01:20
[DumaOS] Marking device that is marked 192.168.1.6 10 7., Tuesday, April 02, 2019 14:01:23
[DumaOS] Marking device that is marked 192.168.1.7 7 8., Tuesday, April 02, 2019 14:01:53
[DumaOS] Marking device that is marked 192.168.1.9 8 10., Tuesday, April 02, 2019 14:02:20
[DumaOS] Marking device that is marked 192.168.1.6 10 7., Tuesday, April 02, 2019 14:02:23
[DumaOS] Marking device that is marked 192.168.1.2 4 2., Tuesday, April 02, 2019 14:02:43
[DumaOS] Marking device that is marked 192.168.1.7 7 8., Tuesday, April 02, 2019 14:02:59
[DumaOS] Marking device that is marked 192.168.1.9 8 10., Tuesday, April 02, 2019 14:03:20
[DumaOS] Marking device that is marked 192.168.1.6 10 7., Tuesday, April 02, 2019 14:03:23
[DumaOS] DHCP new event., Tuesday, April 02, 2019 14:03:28
[DumaOS] DHCP lease change., Tuesday, April 02, 2019 14:03:28
[DHCP IP: 192.168.1.14][Device Name: ANDROID-9F4ADA825FB003FF] to MAC address c0:bd:d1:ac:6d:09, Tuesday, April 02, 2019 14:03:28
[DumaOS] Marking device that is marked 192.168.1.7 7 8., Tuesday, April 02, 2019 14:03:52
[DumaOS] Marking device that is marked 192.168.1.9 8 10., Tuesday, April 02, 2019 14:04:20
[DumaOS] Marking device that is marked 192.168.1.2 4 2., Tuesday, April 02, 2019 14:04:22
[DumaOS] Marking device that is marked 192.168.1.6 10 7., Tuesday, April 02, 2019 14:04:23
[DumaOS] Marking device that is marked 192.168.1.7 7 8., Tuesday, April 02, 2019 14:04:59
[DumaOS] Marking device that is marked 192.168.1.9 8 10., Tuesday, April 02, 2019 14:05:20
[DumaOS] DHCP new event., Tuesday, April 02, 2019 14:05:21
[DumaOS] DHCP lease change., Tuesday, April 02, 2019 14:05:21
[DHCP IP: 192.168.1.2][Device Name: CORSAIR-PC] to MAC address e0:d5:5e:23:4f:75, Tuesday, April 02, 2019 14:05:21
[DumaOS] Marking device that is marked 192.168.1.2 4 2., Tuesday, April 02, 2019 14:05:22
[DumaOS] Marking device that is marked 192.168.1.6 10 7., Tuesday, April 02, 2019 14:05:23
[DumaOS] DHCP new event., Tuesday, April 02, 2019 14:05:23
[DumaOS] DHCP lease change., Tuesday, April 02, 2019 14:05:23
[DHCP IP: 192.168.1.2][Device Name: CORSAIR-PC] to MAC address e0:d5:5e:23:4f:75, Tuesday, April 02, 2019 14:05:23
[DumaOS] Marking device that is marked 192.168.1.2 4 2., Tuesday, April 02, 2019 14:05:25
[DumaOS] DHCP new event., Tuesday, April 02, 2019 14:05:56
[DumaOS] DHCP lease change., Tuesday, April 02, 2019 14:05:56
[DHCP IP: 192.168.1.2][Device Name: CORSAIR-PC] to MAC address e0:d5:5e:23:4f:75, Tuesday, April 02, 2019 14:05:56
[DumaOS] Marking device that is marked 192.168.1.2 4 2., Tuesday, April 02, 2019 14:05:57
[DumaOS] DHCP new event., Tuesday, April 02, 2019 14:05:59
[DumaOS] DHCP lease change., Tuesday, April 02, 2019 14:05:59
[DHCP IP: 192.168.1.2][Device Name: CORSAIR-PC] to MAC address e0:d5:5e:23:4f:75, Tuesday, April 02, 2019 14:05:59
[DumaOS] Marking device that is marked 192.168.1.7 7 8., Tuesday, April 02, 2019 14:05:59
[DumaOS] Marking device that is marked 192.168.1.2 4 2., Tuesday, April 02, 2019 14:06:00
[DumaOS] Marking device that is marked 192.168.1.9 8 10., Tuesday, April 02, 2019 14:06:20
[DumaOS] Marking device that is marked 192.168.1.6 10 7., Tuesday, April 02, 2019 14:06:23
[DumaOS] Marking device that is marked 192.168.1.7 7 8., Tuesday, April 02, 2019 14:06:59
[DumaOS] Marking device that is marked 192.168.1.9 8 10., Tuesday, April 02, 2019 14:07:20
[DumaOS] Marking device that is marked 192.168.1.6 10 7., Tuesday, April 02, 2019 14:07:24
[DumaOS] Marking device that is marked 192.168.1.2 4 2., Tuesday, April 02, 2019 14:07:42
[DumaOS] Marking device that is marked 192.168.1.7 7 8., Tuesday, April 02, 2019 14:07:55
[DumaOS] Marking device that is marked 192.168.1.9 8 10., Tuesday, April 02, 2019 14:08:20
[DumaOS] Marking device that is marked 192.168.1.6 10 7., Tuesday, April 02, 2019 14:08:23
[DumaOS] Marking device that is marked 192.168.1.7 7 8., Tuesday, April 02, 2019 14:08:50
[DumaOS] Marking device that is marked 192.168.1.2 4 2., Tuesday, April 02, 2019 14:08:51
[DumaOS] Marking device that is marked 192.168.1.9 8 10., Tuesday, April 02, 2019 14:09:20
[DumaOS] Marking device that is marked 192.168.1.6 10 7., Tuesday, April 02, 2019 14:09:23
[DumaOS] Marking device that is marked 192.168.1.7 7 8., Tuesday, April 02, 2019 14:09:44
[DumaOS] Marking device that is marked 192.168.1.9 8 10., Tuesday, April 02, 2019 14:10:20
[DumaOS] Marking device that is marked 192.168.1.6 10 7., Tuesday, April 02, 2019 14:10:23
[DumaOS] Marking device that is marked 192.168.1.2 4 2., Tuesday, April 02, 2019 14:10:24
[DumaOS] Marking device that is marked 192.168.1.7 7 8., Tuesday, April 02, 2019 14:10:59
[DumaOS] Marking device that is marked 192.168.1.9 8 10., Tuesday, April 02, 2019 14:11:20
[DumaOS] Marking device that is marked 192.168.1.6 10 7., Tuesday, April 02, 2019 14:11:23
[DumaOS] Marking device that is marked 192.168.1.2 4 2., Tuesday, April 02, 2019 14:11:56
[DumaOS] Marking device that is marked 192.168.1.7 7 8., Tuesday, April 02, 2019 14:11:59
[DumaOS] Marking device that is marked 192.168.1.9 8 10., Tuesday, April 02, 2019 14:12:20
[DumaOS] Marking device that is marked 192.168.1.6 10 7., Tuesday, April 02, 2019 14:12:23
[DumaOS] Marking device that is marked 192.168.1.7 7 8., Tuesday, April 02, 2019 14:13:00
[DumaOS] Marking device that is marked 192.168.1.9 8 10., Tuesday, April 02, 2019 14:13:21
[DumaOS] Marking device that is marked 192.168.1.6 10 7., Tuesday, April 02, 2019 14:13:23
[DumaOS] Marking device that is marked 192.168.1.2 4 2., Tuesday, April 02, 2019 14:13:29
[DumaOS] Marking device that is marked 192.168.1.7 7 8., Tuesday, April 02, 2019 14:13:59
[DumaOS] Marking device that is marked 192.168.1.9 8 10., Tuesday, April 02, 2019 14:14:20
[DumaOS] Marking device that is marked 192.168.1.6 10 7., Tuesday, April 02, 2019 14:14:23
[DumaOS] Marking device that is marked 192.168.1.7 7 8., Tuesday, April 02, 2019 14:14:52
[DumaOS] Marking device that is marked 192.168.1.9 8 10., Tuesday, April 02, 2019 14:15:20
[DumaOS] Marking device that is marked 192.168.1.6 10 7., Tuesday, April 02, 2019 14:15:23
[DumaOS] Marking device that is marked 192.168.1.2 4 2., Tuesday, April 02, 2019 14:15:33
[DumaOS] Marking device that is marked 192.168.1.7 7 8., Tuesday, April 02, 2019 14:15:48
[DumaOS] Marking device that is marked 192.168.1.9 8 10., Tuesday, April 02, 2019 14:16:20
[DumaOS] Marking device that is marked 192.168.1.6 10 7., Tuesday, April 02, 2019 14:16:23
[DumaOS] Marking device that is marked 192.168.1.2 4 2., Tuesday, April 02, 2019 14:16:32
[DumaOS] Marking device that is marked 192.168.1.7 7 8., Tuesday, April 02, 2019 14:16:43
[DumaOS] Marking device that is marked 192.168.1.9 8 10., Tuesday, April 02, 2019 14:17:20
[DumaOS] Marking device that is marked 192.168.1.6 10 7., Tuesday, April 02, 2019 14:17:23
[DumaOS] Marking device that is marked 192.168.1.7 7 8., Tuesday, April 02, 2019 14:17:49
[DumaOS] DHCP new event., Tuesday, April 02, 2019 14:17:54
[DumaOS] DHCP lease change., Tuesday, April 02, 2019 14:17:54
[DHCP IP: 192.168.1.14][Device Name: ANDROID-9F4ADA825FB003FF] to MAC address c0:bd:d1:ac:6d:09, Tuesday, April 02, 2019 14:17:54
[DumaOS] Marking device that is marked 192.168.1.2 4 2., Tuesday, April 02, 2019 14:18:18
[DumaOS] Marking device that is marked 192.168.1.9 8 10., Tuesday, April 02, 2019 14:18:20
[DumaOS] Marking device that is marked 192.168.1.6 10 7., Tuesday, April 02, 2019 14:18:23
[DumaOS] Marking device that is marked 192.168.1.7 7 8., Tuesday, April 02, 2019 14:18:59
[DumaOS] Marking device that is marked 192.168.1.9 8 10., Tuesday, April 02, 2019 14:19:20
[DumaOS] Marking device that is marked 192.168.1.6 10 7., Tuesday, April 02, 2019 14:19:23
[DumaOS] Marking device that is marked 192.168.1.2 4 2., Tuesday, April 02, 2019 14:19:36
[DumaOS] Marking device that is marked 192.168.1.2 4 2., Tuesday, April 02, 2019 14:19:46
[DumaOS] Marking device that is marked 192.168.1.7 7 8., Tuesday, April 02, 2019 14:19:50
[DumaOS] Marking device that is marked 192.168.1.9 8 10., Tuesday, April 02, 2019 14:20:20
[DumaOS] Marking device that is marked 192.168.1.6 10 7., Tuesday, April 02, 2019 14:20:23
[DumaOS] Marking device that is marked 192.168.1.7 7 8., Tuesday, April 02, 2019 14:20:56
[DumaOS] Marking device that is marked 192.168.1.2 4 2., Tuesday, April 02, 2019 14:21:09
[DumaOS] Marking device that is marked 192.168.1.9 8 10., Tuesday, April 02, 2019 14:21:21
[DumaOS] Marking device that is marked 192.168.1.6 10 7., Tuesday, April 02, 2019 14:21:23
[DumaOS] Marking device that is marked 192.168.1.7 7 8., Tuesday, April 02, 2019 14:21:59
[DumaOS] Marking device that is marked 192.168.1.9 8 10., Tuesday, April 02, 2019 14:22:20
[DumaOS] Marking device that is marked 192.168.1.6 10 7., Tuesday, April 02, 2019 14:22:23
[DumaOS] Marking device that is marked 192.168.1.7 7 8., Tuesday, April 02, 2019 14:22:56
[DumaOS] Marking device that is marked 192.168.1.4 2 4., Tuesday, April 02, 2019 14:23:18
[DumaOS] Marking device that is marked 192.168.1.9 8 10., Tuesday, April 02, 2019 14:23:20
[DumaOS] Marking device that is marked 192.168.1.2 4 2., Tuesday, April 02, 2019 14:23:21
[DumaOS] Marking device that is marked 192.168.1.6 10 7., Tuesday, April 02, 2019 14:23:23
[DumaOS] Marking device that is marked 192.168.1.7 7 8., Tuesday, April 02, 2019 14:23:52
[DumaOS] Marking device that is marked 192.168.1.9 8 10., Tuesday, April 02, 2019 14:24:20
[DumaOS] Marking device that is marked 192.168.1.6 10 7., Tuesday, April 02, 2019 14:24:23
[DumaOS] Marking device that is marked 192.168.1.2 4 2., Tuesday, April 02, 2019 14:24:29
[DumaOS] Marking device that is marked 192.168.1.7 7 8., Tuesday, April 02, 2019 14:24:46
[DumaOS] Marking device that is marked 192.168.1.9 8 10., Tuesday, April 02, 2019 14:25:20
[DumaOS] Marking device that is marked 192.168.1.6 10 7., Tuesday, April 02, 2019 14:25:23
[DumaOS] Marking device that is marked 192.168.1.2 4 2., Tuesday, April 02, 2019 14:25:47
[DumaOS] Marking device that is marked 192.168.1.7 7 8., Tuesday, April 02, 2019 14:25:59
[DumaOS] Marking device that is marked 192.168.1.9 8 10., Tuesday, April 02, 2019 14:26:20
[DumaOS] Marking device that is marked 192.168.1.6 10 7., Tuesday, April 02, 2019 14:26:23
[DumaOS] Marking device that is marked 192.168.1.7 7 8., Tuesday, April 02, 2019 14:26:59
[DumaOS] Marking device that is marked 192.168.1.2 4 2., Tuesday, April 02, 2019 14:27:16
[DumaOS] Marking device that is marked 192.168.1.9 8 10., Tuesday, April 02, 2019 14:27:20
[DumaOS] Marking device that is marked 192.168.1.6 10 7., Tuesday, April 02, 2019 14:27:23
[Internet connected] IP address: 24.89.53.205, Tuesday, April 02, 2019 14:27:38
[DumaOS] Marking device that is marked 192.168.1.7 7 8., Tuesday, April 02, 2019 14:27:54
[DumaOS] Marking device that is marked 192.168.1.9 8 10., Tuesday, April 02, 2019 14:28:20
[DumaOS] Marking device that is marked 192.168.1.6 10 7., Tuesday, April 02, 2019 14:28:23
[DumaOS] DHCP new event., Tuesday, April 02, 2019 14:28:24
[DumaOS] DHCP lease change., Tuesday, April 02, 2019 14:28:24
[DHCP IP: 192.168.1.7][Device Name: ESP_570147] to MAC address 60:01:94:57:01:47, Tuesday, April 02, 2019 14:28:24
[DumaOS] Marking device that is marked 192.168.1.7 7 8., Tuesday, April 02, 2019 14:28:25
[DumaOS] Marking device that is marked 192.168.1.7 7 8., Tuesday, April 02, 2019 14:28:59
[DumaOS] DHCP new event., Tuesday, April 02, 2019 14:29:12
[DumaOS] DHCP lease change., Tuesday, April 02, 2019 14:29:12
[DHCP IP: 192.168.1.8][Device Name: ESP_4AEC92] to MAC address 2c:3a:e8:4a:ec:92, Tuesday, April 02, 2019 14:29:12
[DumaOS] Marking device that is marked 192.168.1.2 4 2., Tuesday, April 02, 2019 14:29:18
[DumaOS] Marking device that is marked 192.168.1.9 8 10., Tuesday, April 02, 2019 14:29:20
[DumaOS] Marking device that is marked 192.168.1.6 10 7., Tuesday, April 02, 2019 14:29:23
[DumaOS] DHCP new event., Tuesday, April 02, 2019 14:29:33
[DumaOS] DHCP lease change., Tuesday, April 02, 2019 14:29:33
[DHCP IP: 192.168.1.9][Device Name: ESP_858746] to MAC address dc:4f:22:85:87:46, Tuesday, April 02, 2019 14:29:33
[DumaOS] Marking device that is marked 192.168.1.9 8 10., Tuesday, April 02, 2019 14:29:33
[DumaOS] DHCP new event., Tuesday, April 02, 2019 14:29:56
[DumaOS] DHCP lease change., Tuesday, April 02, 2019 14:29:56
[DHCP IP: 192.168.1.6][Device Name: ESP_8619BF] to MAC address dc:4f:22:86:19:bf, Tuesday, April 02, 2019 14:29:56
[DumaOS] Marking device that is marked 192.168.1.6 10 7., Tuesday, April 02, 2019 14:29:57
[DumaOS] Marking device that is marked 192.168.1.7 7 8., Tuesday, April 02, 2019 14:29:59
[DumaOS] Marking device that is marked 192.168.1.9 8 10., Tuesday, April 02, 2019 14:30:21
[DumaOS] Marking device that is marked 192.168.1.6 10 7., Tuesday, April 02, 2019 14:30:23
[DumaOS] Marking device that is marked 192.168.1.2 4 2., Tuesday, April 02, 2019 14:30:26
[DumaOS] Marking device that is marked 192.168.1.7 7 8., Tuesday, April 02, 2019 14:30:59
[DumaOS] Marking device that is marked 192.168.1.9 8 10., Tuesday, April 02, 2019 14:31:20
[DumaOS] Marking device that is marked 192.168.1.6 10 7., Tuesday, April 02, 2019 14:31:23
[DumaOS] Marking device that is marked 192.168.1.7 7 8., Tuesday, April 02, 2019 14:31:56
[DumaOS] Marking device that is marked 192.168.1.2 4 2., Tuesday, April 02, 2019 14:32:09
[DumaOS] Marking device that is marked 192.168.1.9 8 10., Tuesday, April 02, 2019 14:32:20
[DumaOS] DHCP new event., Tuesday, April 02, 2019 14:32:21
[DumaOS] DHCP lease change., Tuesday, April 02, 2019 14:32:21
[DHCP IP: 192.168.1.14][Device Name: ANDROID-9F4ADA825FB003FF] to MAC address c0:bd:d1:ac:6d:09, Tuesday, April 02, 2019 14:32:21
[DumaOS] Marking device that is marked 192.168.1.6 10 7., Tuesday, April 02, 2019 14:32:23
[DumaOS] Marking device that is marked 192.168.1.7 7 8., Tuesday, April 02, 2019 14:32:59
[DumaOS] Marking device that is marked 192.168.1.9 8 10., Tuesday, April 02, 2019 14:33:20
[DumaOS] Marking device that is marked 192.168.1.6 10 7., Tuesday, April 02, 2019 14:33:23
[DumaOS] Marking device that is marked 192.168.1.2 4 2., Tuesday, April 02, 2019 14:33:29
[DumaOS] Marking device that is marked 192.168.1.7 7 8., Tuesday, April 02, 2019 14:33:59
[DumaOS] Marking device that is marked 192.168.1.9 8 10., Tuesday, April 02, 2019 14:34:20
[DumaOS] Marking device that is marked 192.168.1.6 10 7., Tuesday, April 02, 2019 14:34:23
[DumaOS] Marking device that is marked 192.168.1.7 7 8., Tuesday, April 02, 2019 14:34:53
[DumaOS] Marking device that is marked 192.168.1.9 8 10., Tuesday, April 02, 2019 14:35:20
[DumaOS] Marking device that is marked 192.168.1.6 10 7., Tuesday, April 02, 2019 14:35:23
[DumaOS] Marking device that is marked 192.168.1.2 4 2., Tuesday, April 02, 2019 14:35:29
[DumaOS] Marking device that is marked 192.168.1.7 7 8., Tuesday, April 02, 2019 14:35:58
[DumaOS] Marking device that is marked 192.168.1.9 8 10., Tuesday, April 02, 2019 14:36:20
[DumaOS] Marking device that is marked 192.168.1.6 10 7., Tuesday, April 02, 2019 14:36:23
[DumaOS] Marking device that is marked 192.168.1.2 4 2., Tuesday, April 02, 2019 14:36:29
[DumaOS] Marking device that is marked 192.168.1.7 7 8., Tuesday, April 02, 2019 14:36:59
[DumaOS] Marking device that is marked 192.168.1.9 8 10., Tuesday, April 02, 2019 14:37:20
[DumaOS] Marking device that is marked 192.168.1.6 10 7., Tuesday, April 02, 2019 14:37:23
[admin login] from source 192.168.1.2, Tuesday, April 02, 2019 14:37:30
[admin login] from source 192.168.1.2, Tuesday, April 02, 2019 14:37:31
[admin login] from source 192.168.1.2, Tuesday, April 02, 2019 14:37:31
[admin login] from source 192.168.1.2, Tuesday, April 02, 2019 14:37:32
[admin login] from source 192.168.1.2, Tuesday, April 02, 2019 14:37:32
[admin login] from source 192.168.1.2, Tuesday, April 02, 2019 14:37:33
[admin login] from source 192.168.1.2, Tuesday, April 02, 2019 14:37:34
[admin login] from source 192.168.1.2, Tuesday, April 02, 2019 14:37:41
[admin login] from source 192.168.1.2, Tuesday, April 02, 2019 14:37:41
[admin login] from source 192.168.1.2, Tuesday, April 02, 2019 14:37:42
[admin login] from source 192.168.1.2, Tuesday, April 02, 2019 14:37:43
[DumaOS] Marking device that is marked 192.168.1.7 7 8., Tuesday, April 02, 2019 14:37:59
[admin login] from source 192.168.1.2, Tuesday, April 02, 2019 14:38:00
[admin login] from source 192.168.1.2, Tuesday, April 02, 2019 14:38:00
[admin login] from source 192.168.1.2, Tuesday, April 02, 2019 14:38:00
[DumaOS] Marking device that is marked 192.168.1.9 8 10., Tuesday, April 02, 2019 14:38:20
[DumaOS] Marking device that is marked 192.168.1.6 10 7., Tuesday, April 02, 2019 14:38:23
 

Share this post


Link to post
Share on other sites
1 hour ago, Netduma Fraser said:

Is .8 performing worse for you than .10?

Before it use to never continuously say:  [DumaOS] Marking device that is marked

which is very very odd 😕

Share this post


Link to post
Share on other sites

Just bought this router, seems a bit laggy on the GUI.   Initial setup was a nightmare on stock OS, once I updated to 1.0.1.10 I did a hard reset and started my wizard.  The wizard did not get a download speed, only an upload which I thought was weird and for having the $500 XR700 and a quad core 1.7Ghz CPU in the unit it just feels like an old Celeron for some reason and just muddy to browse the GUI. Also, and this is probably on the Netgear Dev side, The NAT when open still reports as a PAR NAT as if it were secured.  Open NATs should give us full cone.  I haven't been able to try out the GeoFiltering but I just thought I'd give my 2cents on the FW. I'll be downgrading to the .8 and hard reset to see if this helps with the mugginess of the GUI and maybe help with the speedtest?  

 

EDIT:

Just did a downgrade to .8 and the GUI seems much more fluid - although it's still a little muddy it's not like "the swamp of sorrows".  Anyway that initial setup is absolutely dreadful.  I guarantee people spending $500 on this XR700 router won't expect to wait so long for the admin IP to respond to the browser (192.168.1.1) on initial setup/startup. This is the same with the stock FW, .8 and .10 FW and is almost so uncomfortable you start to question whether the unit is faulty or not.  Even at the start of the setup wizard the hanging and blank pages are enough to make even the tech savvy wonder if it's not responding or if it's just slow.  You'd think with a 1.7Ghz quad core CPU, 1GB of DDR3, and 512MB of NAND Flash this router would respond faster to the FW/OS. I have to say the .8 FW did give me an accurate d/l and u/l speedtest on the setup wizard, NAT still reporting PAR on IPv4 and IPv6 when set to Open which again is a tell tale sign of Netgear's which the 8000, 8000P and 9000 share this issue as well. 

 

Edit #2:

Getting into some Overwatch, I'm noticing a lot of latency issues where I'll get serious spiking - Not streaming.  QoS is set to 70% on both UL and DL and Anti-BB for when there's high traffic detected.  Any thoughts?

Share this post


Link to post
Share on other sites

Hi Jeremy, welcome to the forum!

I would recommend you stay on the .8 firmware due to the slow UI issue on .10. As you're still experiencing it what browser are you using and are you accessing via HTTPS? I can't comment on how the router handles NAT as that is Netgear related but I'll pass on your concern.

What platform are you playing Overwatch on? Are you using Traffic Prioritization and are you using the Geo-Filter?

Share this post


Link to post
Share on other sites

@jeremey feen

Hey by chance did you type in your actually speeds your provider gives you once in awhile i noticed when i have reset my router both the xr500 and xr700 it thinks i have 1gb up and down and when i set my sliders to 70% it was for the 1gb and down not 300mbs down that i pay for .

Second I know what you mean the xr700 everytime i have factory reset it and set it up for the first time I thought it was broken or something the ui took forever to load it scared me but another person had me do 3 resets with the paper clip on the back and it seemed to really help the ui along after that for just the setup part .

Share this post


Link to post
Share on other sites
49 minutes ago, Danny80916 said:

@jeremey feen

Hey by chance did you type in your actually speeds your provider gives you once in awhile i noticed when i have reset my router both the xr500 and xr700 it thinks i have 1gb up and down and when i set my sliders to 70% it was for the 1gb and down not 300mbs down that i pay for .

When you do the setup wizard after a factory reset do you skip the speed test/it fails to show your correct speeds and you don't edit it? If so that explains what you see as it'll default to 1000/1000 otherwise

Share this post


Link to post
Share on other sites

So during the initial setup in the .8FW the speedtest did detect the correct speeds - did not default to 1GB.  In the ABB settings the d/l was set automatically to 333.62 and the u/l set to 31.6. So my sliders are set to 70% @ 233.5 d/l and 22.1 u/l. Overwatch is played on PC (8086K @ 5.1Ghz, 16Gb DDR3600 @ 15-15-15-35, 1080ti, 1TB 970 Evo M.2 on Asus X Code) and is hardwired. @Danny80916 I did do a hard reset both after install of the .10 and then after rollback to the .8FW.  I even did a 30-30-30 to see if that would help.  Honestly after initial setup wizard on .8 the GUI isn't terrible - but you'd think a 1.7Ghz quad core with 1GB of DDR3 and 512 of NAND would scream through an OS like FreeBSD, not saying that's what DumaOS is written on it just feels similar.  Anyway I've also written in detail the issues we're having here and what the exact settings are on the router in the Netgear Pro Gaming forums here:

https://community.netgear.com/t5/Nighthawk-Pro-Gaming-Routers/XR700-Glitching-games-during-gameplay/m-p/1732218#M9692

Share this post


Link to post
Share on other sites
22 hours ago, Jeremy Fenn said:

So during the initial setup in the .8FW the speedtest did detect the correct speeds - did not default to 1GB.  In the ABB settings the d/l was set automatically to 333.62 and the u/l set to 31.6. So my sliders are set to 70% @ 233.5 d/l and 22.1 u/l. Overwatch is played on PC (8086K @ 5.1Ghz, 16Gb DDR3600 @ 15-15-15-35, 1080ti, 1TB 970 Evo M.2 on Asus X Code) and is hardwired. @Danny80916 I did do a hard reset both after install of the .10 and then after rollback to the .8FW.  I even did a 30-30-30 to see if that would help.  Honestly after initial setup wizard on .8 the GUI isn't terrible - but you'd think a 1.7Ghz quad core with 1GB of DDR3 and 512 of NAND would scream through an OS like FreeBSD, not saying that's what DumaOS is written on it just feels similar.  Anyway I've also written in detail the issues we're having here and what the exact settings are on the router in the Netgear Pro Gaming forums here:

https://community.netgear.com/t5/Nighthawk-Pro-Gaming-Routers/XR700-Glitching-games-during-gameplay/m-p/1732218#M9692

If it detected wrong speeds and you accepted them without editing then that will carry them through, you can just edit this yourself in ABB. The PC itself doesn't have a bearing on how fast the interface responds, assuming your PC is capable of using a web browser without issues. I've responded to your Netgear post.

Share this post


Link to post
Share on other sites

Interesting enough I haven't had any of the problems others are having. This version has been very stable hasn't needed to be rebooted since the update to V1.0.1.10.

Share this post


Link to post
Share on other sites
On 4/2/2019 at 3:12 PM, Netduma Fraser said:

That's a normal entry, what issues are you seeing apart from a long log?

Well lets add this to the unresponsive error message with the Version 8, now I got to reboot this router to get rid of it because no matter how many times I click on "OK"  it certainly doesn't go away🙄🙄🙄😑😑😑👎👎👎👎

Image1.jpg

Share this post


Link to post
Share on other sites
5 hours ago, TheWraith said:

Well lets add this to the unresponsive error message with the Version 8, now I got to reboot this router to get rid of it because no matter how many times I click on "OK"  it certainly doesn't go away🙄🙄🙄😑😑😑👎👎👎👎

I haven't seen that one before. When does it occur? Is it only on that page? Was anything prior to this occurring? Does a refresh get rid of it?

Share this post


Link to post
Share on other sites
On 4/9/2019 at 12:34 PM, Netduma Fraser said:

I haven't seen that one before. When does it occur? Is it only on that page? Was anything prior to this occurring? Does a refresh get rid of it?

Yeah, after powering it off, then back on, that error message went away and never came back, so far, it happened when I would log onto the router which was odd.

Share this post


Link to post
Share on other sites

My ping assist feature doesn't work with this FW. Also how do I go about downgrading FW if need be? Thank you.

Share this post


Link to post
Share on other sites
9 hours ago, xBuTcHeRx said:

My ping assist feature doesn't work with this FW. Also how do I go about downgrading FW if need be? Thank you.

What exactly isn't working with the feature? Not getting games under your limit or getting games over your limit? You can download a previous firmware file and follow the same procedure for upgrading by uploading the file in settings.

Share this post


Link to post
Share on other sites

Long time user of Netduma OS and DumaOS, I have a Netduma R1 and I just upgraded my XR500 for a XR700. I was testing the lastest Nighthawk Pro Gaming Public Firmware v1.0.1.10 (XR700) and I already noticed few issues:

 

1) Dashboard is freezing when you play with the size of the window browser. For example, the Geo-Filter Map, Network Snapshot, Network Overview, or any R-App with an animation will freeze or will not display the animation until you refresh the browser.

 

2) The WAN Port doesn’t run my Internet Gigabit speed up to 940Mbps/50Mbps. When I performed a speedtest, the download speed reach around 500-650Mbps with or without QoS “On” and the CPU Usage is at 100% on all 4 cores with the XR700.

 

On my XR500, I was able to reach easily my Gigabit speed with or without QoS “On” and the 2 cores were never remained capped at 100% of the CPU Usage during the full speedtest.

 

So I decide to test the 10G SFP+ port on my XR700 with a SFP+ module of Netgear AGM734-10000s 1000BASE-T. I was surprised to see that I was able reach easily the 960Mbps/60Mbps and the CPU Usage is around 80% on 1 core only and not the 4 cores.

 

Why does the WAN port perform badly compare to the SFP+ port?

 

3) Factory Reset with the physical button on device will not reset correctly the initial setup but if you do the factory reset inside the DumaOS with the “Erase” button, it will load all the page for the setup without any freezing loading pages or any error messages.

 

My new purchase of a XR700 and a SFP+ module was very expensive and I’m kinda annoyed to see all those problems...

Share this post


Link to post
Share on other sites
3 hours ago, Donovan said:

1) Dashboard is freezing when you play with the size of the window browser. For example, the Geo-Filter Map, Network Snapshot, Network Overview, or any R-App with an animation will freeze or will not display the animation until you refresh the browser.

Thanks for letting us know this. I believe the developers are aware of a freezing issue but i'll check with them. I wasn't able to recreate the freezing but I did encounter another similar bug.

3 hours ago, Donovan said:

2) The WAN Port doesn’t run my Internet Gigabit speed up to 940Mbps/50Mbps. When I performed a speedtest, the download speed reach around 500-650Mbps with or without QoS “On” and the CPU Usage is at 100% on all 4 cores with the XR700.

That's really interesting. Am I right in thinking that a connection like that would not require a PPPoE login? It's really useful to know that the SFP+ port performs as expected while the WAN port doesn't, that will help us locate the problem if there is one. Might be something unusual in your network setup or it might be evidence of a larger problem. I'm glad it's working for you with the SFP+ port though!

3 hours ago, Donovan said:

3) Factory Reset with the physical button on device will not reset correctly the initial setup but if you do the factory reset inside the DumaOS with the “Erase” button, it will load all the page for the setup without any freezing loading pages or any error messages.

I tested this myself with an XR700 in the office running the latest firmware, and the button reset did work. I had to hold it for a long time though, I counted to 30 as the following guide suggests: https://kb.netgear.com/000053098/How-do-I-perform-a-factory-reset-on-my-Nighthawk-Pro-Gaming-router

Share this post


Link to post
Share on other sites

 

3 hours ago, Netduma Alex said:

That's really interesting. Am I right in thinking that a connection like that would not require a PPPoE login? It's really useful to know that the SFP+ port performs as expected while the WAN port doesn't, that will help us locate the problem if there is one. Might be something unusual in your network setup or it might be evidence of a larger problem. I'm glad it's working for you with the SFP+ port though! 

Correct, it does not require a PPPoE login.

 

3 hours ago, Netduma Alex said:

I tested this myself with an XR700 in the office running the latest firmware, and the button reset did work. I had to hold it for a long time though, I counted to 30 as the following guide suggests: https://kb.netgear.com/000053098/How-do-I-perform-a-factory-reset-on-my-Nighthawk-Pro-Gaming-router

Thank you for the link, I'm already aware to press and hold the reset button for  30 seconds because I had to do this with my XR500 before I purchase a XR700.

Share this post


Link to post
Share on other sites
20 hours ago, Donovan said:

Thank you for the link, I'm already aware to press and hold the reset button for  30 seconds because I had to do this with my XR500 before I purchase a XR700.

What exactly occurs when resetting via the button in the back? Does it wipe settings without going to the wizard or does it just seem to reboot?

Share this post


Link to post
Share on other sites

The wizard setup doesn't work properly. Sometime it will run the whole wizard setup correctly and some other time it will run a broken wizard setup. It will not load some option page to let you choose during your initial setup like WAN Port Preference between Internet Port (1Gbps) or 10G LAN SFP+Port (10 Gbps), Checking Internet Speed, or the Firmware Update. Some page will become not responsive after your press the button next, it takes forever to load or it freeze..

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

×
×
  • Create New...