Why does the A6200 continually appear in router log?

[IrvSp]

WIfe's PC, running on W10, latest Fall creator update (V1803), Pro Version, using F/W 1.0.0.35 (Beta), connected to a Nighthawk R8000 using Smart Connect for the 2 5Ghz bands.

I see this sort of logging repeatedly every day in the log:

---------------------

[DHCP IP: (192.168.1.40)] to MAC address 08:BD:43:A5:8C:AA, Saturday, Aug 18,2018 18:47:44
[DHCP IP: (192.168.1.40)] to MAC address 08:BD:43:A5:8C:AA, Saturday, Aug 18,2018 18:32:58
[DHCP IP: (192.168.1.30)] to MAC address F8:B1:56:DD:6A:5B, Saturday, Aug 18,2018 18:29:57
[DHCP IP: (192.168.1.40)] to MAC address 08:BD:43:A5:8C:AA, Saturday, Aug 18,2018 17:43:43
[DHCP IP: (192.168.1.40)] to MAC address 08:BD:43:A5:8C:AA, Saturday, Aug 18,2018 17:42:54
[Time synchronized with NTP server] Saturday, Aug 18,2018 17:42:34
[Internet connected] IP address: 67.8.88.79, Saturday, Aug 18,2018 17:42:33
[DHCP IP: (192.168.1.2)] to MAC address AC:63:BE:8E:E3:E2, Saturday, Aug 18,2018 17:41:53
[DHCP IP: (192.168.1.40)] to MAC address 08:BD:43:A5:8C:AA, Saturday, Aug 18,2018 17:41:19
[DHCP IP: (192.168.1.40)] to MAC address 08:BD:43:A5:8C:AA, Saturday, Aug 18,2018 17:39:50
[DHCP IP: (192.168.1.40)] to MAC address 08:BD:43:A5:8C:AA, Saturday, Aug 18,2018 17:37:00
[DHCP IP: (192.168.1.40)] to MAC address 08:BD:43:A5:8C:AA, Saturday, Aug 18,2018 17:29:19
[DHCP IP: (192.168.1.40)] to MAC address 08:BD:43:A5:8C:AA, Saturday, Aug 18,2018 17:28:01
[DHCP IP: (192.168.1.40)] to MAC address 08:BD:43:A5:8C:AA, Saturday, Aug 18,2018 17:26:23
[DHCP IP: (192.168.1.40)] to MAC address 08:BD:43:A5:8C:AA, Saturday, Aug 18,2018 17:09:19
[DHCP IP: (192.168.1.40)] to MAC address 08:BD:43:A5:8C:AA, Saturday, Aug 18,2018 16:57:03
[DHCP IP: (192.168.1.40)] to MAC address 08:BD:43:A5:8C:AA, Saturday, Aug 18,2018 16:53:27
[DHCP IP: (192.168.1.40)] to MAC address 08:BD:43:A5:8C:AA, Saturday, Aug 18,2018 16:53:10
[DHCP IP: (192.168.1.40)] to MAC address 08:BD:43:A5:8C:AA, Saturday, Aug 18,2018 16:41:46
[Time synchronized with NTP server] Saturday, Aug 18,2018 16:16:16
[Internet connected] IP address: 67.8.88.79, Saturday, Aug 18,2018 16:16:15
[DHCP IP: (192.168.1.40)] to MAC address 08:BD:43:A5:8C:AA, Saturday, Aug 18,2018 16:01:07
[DHCP IP: (192.168.1.40)] to MAC address 08:BD:43:A5:8C:AA, Saturday, Aug 18,2018 15:24:06
[DHCP IP: (192.168.1.40)] to MAC address 08:BD:43:A5:8C:AA, Saturday, Aug 18,2018 15:22:44
[DHCP IP: (192.168.1.40)] to MAC address 08:BD:43:A5:8C:AA, Saturday, Aug 18,2018 15:21:58
[DHCP IP: (192.168.1.40)] to MAC address 08:BD:43:A5:8C:AA, Saturday, Aug 18,2018 15:17:04
[DHCP IP: (192.168.1.40)] to MAC address 08:BD:43:A5:8C:AA, Saturday, Aug 18,2018 15:09:37
[DHCP IP: (192.168.1.40)] to MAC address 08:BD:43:A5:8C:AA, Saturday, Aug 18,2018 15:07:32
[DHCP IP: (192.168.1.40)] to MAC address 08:BD:43:A5:8C:AA, Saturday, Aug 18,2018 15:06:50
[DHCP IP: (192.168.1.40)] to MAC address 08:BD:43:A5:8C:AA, Saturday, Aug 18,2018 15:06:14
[DHCP IP: (192.168.1.40)] to MAC address 08:BD:43:A5:8C:AA, Saturday, Aug 18,2018 15:02:37
[DHCP IP: (192.168.1.40)] to MAC address 08:BD:43:A5:8C:AA, Saturday, Aug 18,2018 15:02:26
[DHCP IP: (192.168.1.40)] to MAC address 08:BD:43:A5:8C:AA, Saturday, Aug 18,2018 14:59:52
[DHCP IP: (192.168.1.40)] to MAC address 08:BD:43:A5:8C:AA, Saturday, Aug 18,2018 14:59:31
[Time synchronized with NTP server] Saturday, Aug 18,2018 14:49:56
[Internet connected] IP address: 67.8.88.79, Saturday, Aug 18,2018 14:49:55
[DHCP IP: (192.168.1.6)] to MAC address 0C:89:10:84:61:9C, Saturday, Aug 18,2018 13:26:16
[Time synchronized with NTP server] Saturday, Aug 18,2018 13:23:35
[Internet connected] IP address: 67.8.88.79, Saturday, Aug 18,2018 13:23:35
[DHCP IP: (192.168.1.40)] to MAC address 08:BD:43:A5:8C:AA, Saturday, Aug 18,2018 13:08:46
[DHCP IP: (192.168.1.40)] to MAC address 08:BD:43:A5:8C:AA, Saturday, Aug 18,2018 12:22:45
[DHCP IP: (192.168.1.40)] to MAC address 08:BD:43:A5:8C:AA, Saturday, Aug 18,2018 12:22:27
[DHCP IP: (192.168.1.40)] to MAC address 08:BD:43:A5:8C:AA, Saturday, Aug 18,2018 12:22:17
[DHCP IP: (192.168.1.40)] to MAC address 08:BD:43:A5:8C:AA, Saturday, Aug 18,2018 12:22:04
[DHCP IP: (192.168.1.40)] to MAC address 08:BD:43:A5:8C:AA, Saturday, Aug 18,2018 12:21:44
[DHCP IP: (192.168.1.40)] to MAC address 08:BD:43:A5:8C:AA, Saturday, Aug 18,2018 12:21:33
[DHCP IP: (192.168.1.40)] to MAC address 08:BD:43:A5:8C:AA, Saturday, Aug 18,2018 12:21:03
[DHCP IP: (192.168.1.40)] to MAC address 08:BD:43:A5:8C:AA, Saturday, Aug 18,2018 12:18:06
[DHCP IP: (192.168.1.40)] to MAC address 08:BD:43:A5:8C:AA, Saturday, Aug 18,2018 12:16:53
[Time synchronized with NTP server] Saturday, Aug 18,2018 11:57:15
[Internet connected] IP address: 67.8.88.79, Saturday, Aug 18,2018 11:57:14
[DHCP IP: (192.168.1.40)] to MAC address 08:BD:43:A5:8C:AA, Saturday, Aug 18,2018 11:25:48
[DHCP IP: (192.168.1.40)] to MAC address 08:BD:43:A5:8C:AA, Saturday, Aug 18,2018 11:10:59
[DHCP IP: (192.168.1.40)] to MAC address 08:BD:43:A5:8C:AA, Saturday, Aug 18,2018 11:00:53
[DHCP IP: (192.168.1.40)] to MAC address 08:BD:43:A5:8C:AA, Saturday, Aug 18,2018 10:47:05

---------------------------

192.168.1.40 is her PC and the address is RESERVED outside of the DHCP address range.

Now this is NOT a new USB Network Adapter, and we've had this 'forever' with the same 'problem'. I've tried every trick I know? All possible USB and POWER settings are set to NOT turn it off. Every single f/w has been tried MANY times, and all sorts of ways... clean, over older ones, every possible way for years... and this problem started from day 1 no less on I think W8.0.

Yes, I've lived with it forever. Why? My wife has NEVER complained she wasn't connected! A few time though I did get "the network seems slow" though. It seems more of those 'complaints' recently, so I am re-visiting this.

Then there are log entries that show it can go for a log time with only one entry:

===================

[DHCP IP: (192.168.1.9)] to MAC address 48:60:5F:85:5B:17, Saturday, Aug 18,2018 10:44:58
[Time synchronized with NTP server] Saturday, Aug 18,2018 10:30:55
[Internet connected] IP address: 67.8.88.79, Saturday, Aug 18,2018 10:30:55
[DHCP IP: (192.168.1.40)] to MAC address 08:BD:43:A5:8C:AA, Saturday, Aug 18,2018 09:45:17
[Time synchronized with NTP server] Saturday, Aug 18,2018 09:04:35
[Internet connected] IP address: 67.8.88.79, Saturday, Aug 18,2018 09:04:34
[DHCP IP: (192.168.1.40)] to MAC address 08:BD:43:A5:8C:AA, Saturday, Aug 18,2018 08:42:29
[DHCP IP: (192.168.1.3)] to MAC address 84:89:AD:71:97:B2, Saturday, Aug 18,2018 08:15:42
[DHCP IP: (192.168.1.30)] to MAC address F8:B1:56:DD:6A:5B, Saturday, Aug 18,2018 07:51:09
[Time synchronized with NTP server] Saturday, Aug 18,2018 07:38:15
[Internet connected] IP address: 67.8.88.79, Saturday, Aug 18,2018 07:38:14

==================

Since this has been happening 'forever' and on different OS's, it most likely isn't the PC nor the Power settings.

I've used both DHCP addressing and Reserved IP Address, makes no difference?

My PC (192.168.1.30) hardly ever makes a log entry (hard wired Reserved Address)? Also will not turn-off via power or device setting. I'm tending to think those entries are for coming out of sleep, at least on my PC. Both PC's according to IPCONFIG have a 24 hour lease on the IP Address and normally after 12 hours the PC will try to see if it has the same lease or not by renewing it.

Just bothers me and was wondering if anyone else sees this or knows the reason why this happens?

Again, as far as I can tell, the is no drop of the connection... not on the Genie icon on the Systray or Windows/Browser notification of no internet connection...

[IrvSp]

I partially figured this out...

The PC is basically in sleep mode... the same as my PC though.

I noticed when I woke here PC up the Systray Wireless Network Connectoid had a RED dot on it, then went away. Ran IPCONFIG /ALL and sure enough, the lease was just obtained. So sleeping shuts down the USB Network Device it seems. My PC, with the same power setting but wired doesn't do that.

I looked into today's log:

============

[DHCP IP: (192.168.1.40)] to MAC address 08:BD:43:A5:8C:AA, Sunday, Aug 19,2018 09:13:25
[Admin login] from source 192.168.1.30, Sunday, Aug 19,2018 09:12:27
[DHCP IP: (192.168.1.30)] to MAC address F8:B1:56:DD:6A:5B, Sunday, Aug 19,2018 09:11:53
[DHCP IP: (192.168.1.3)] to MAC address 84:89:AD:71:97:B2, Sunday, Aug 19,2018 08:17:56
[DHCP IP: (192.168.1.9)] to MAC address 48:60:5F:85:5B:17, Sunday, Aug 19,2018 08:15:17
[Time synchronized with NTP server] Sunday, Aug 19,2018 08:05:55
[Internet connected] IP address: 67.8.88.79, Sunday, Aug 19,2018 08:05:55
[DHCP IP: (192.168.1.40)] to MAC address 08:BD:43:A5:8C:AA, Sunday, Aug 19,2018 07:31:09
[Admin login] from source 192.168.1.30, Sunday, Aug 19,2018 07:07:15
[email sent to: ixxx] Sunday, Aug 19,2018 07:01:02
========

At 7:07AM was when I looked at the log for the initial check and there were no entries but that the email was sent.

My PC was on before the log was sent to my ID and cleared to start over.  At 7:31AM her PC was powered on. I checked the lease and it was for 24 hours. At 9:12AM I checked the log and no new entries were from her PC. So I woke it up (and saw the red dot on the connectoid). Checked the log, there was the IP Request at 9:13AM.

So, 1/2 of the 'problem' is solved. Going to sleep is different on my wired PC connection that it is on the USB Network adapter when the computer goes to sleep. Probably PC hardware differences I'd assume... and tied to the USB drivers. Setting for saving power by letting the PC turn off the device doesn't seem to hold when the PC actually sleeps?

Still, unsolved is the repeated attempts within seconds, which doesn't always happen.

[IrvSp]

I think I figured out the problem... and it is in the NG driver...

See the screen captures to the right from Device Manager please.

What you see are the Power Settings for 2 different wireless adapters on the PC. The Dell supplied N Speed Intel adapter and the USB NG A6200. Note the differences... specifically the WAKEUP box... ALWAYS grayed out on the A6200 and missing the box below it. Now look at the disabled Intel one. If you do allow the PC to turn it off, if the box underneath is selected to allow it to wake up the computer and is ONLY available if the first box is selected. The A6200 NEVER allows that box to be one. Driver error?

It hit me that her PC has both a wireless mouse and keyboard, both controlled by a USB port, both USB 3.0, the port for the USB dongle is right next to the port the A6200 is plugged into, so it can't be powered off...

@ChristineT, @DarrenM, can you take a look at this? Been bothering for a long time.

[DarrenM]

Hello IrvSp

I will escalate this up to the engineers and see if they may have a awnser or fix for this issue.

DarrenM

[IrvSp]

Thanks @DarrenM, I've had this problem on every release of the firmware and I do know the adapter is old.

If I'm going to decide to replace it, assuming support will not do anything, do you know if the A6210 or A7000 have this same feature missing?

[DarrenM]

I have checked and the A6200 is not able to do this but the A7000 will wake the computer.

DarrenM

[IrvSp]

@DarrenM, thanks... that is all I needed to know. Considering my options... this is more of an annoyance than a problem. May just live with it as I now know why.

Thank you again.