NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.

Forum Discussion

rsdavis1's avatar
rsdavis1
Aspirant
May 21, 2020
Solved

R6250 WiFi Clients are not identified

I have both wired and wireless clients served by this R6250 router.  Wireless security is WPA2-PSK [AES].  All seem to be functioning normally.  However, the list of wireless clients always includes ...
  • antinode's avatar
    antinode
    Jun 12, 2020

    > [...] Any ideas?

     

       I can offer some clues.

     

       Names which begin with "HP", like "HPA08CFD6E31EC" ("6") and
    "HPFA0C87" ("9") suggest Hewlett Packard.  The last six characters of
    those names match the low six (hexadecimal) digits of the MAC address,
    which is typical for such automatically generated names.

     

       On "9", the OUI ("64:51:06") is registered to HP.  See, for example,
    a Web site like: https://aruljohn.com/mac.pl

     

       My quick Web search suggested that "02:0F:B5" ("6") is a virtual OUI,
    typically used by devices like wireless extenders.

     

       In "10", the OUI ("20:EE:28") is registered to Apple, which is, at
    least, suggestive.

     

       "7" and "8" remains mysteries.


       In general, if a device didn't get an IP address, then calling it a
    "connection" might be over-stating things.  Without an IP address, I'd
    say that there's a limit to how much trouble it can cause.  Those could
    be wireless devices which tried to connect using bad credentials, for
    example.

     

       If a device did get an IP address (like, say, "8"), then I might try
    pointing a web browser at that address, to see if it's willing to talk
    that way.  (Many types of devices do that these days.)

     

       You might run an experiment or two, too.  For example, introduce a
    novel wireless device, intentionally specify a bad passphrase, and
    observe the (changed?) results.  Or, power down your whole dwelling,
    then bring back the router, and then add other devices or power circuits
    and watch the changes.

     

       Beyond that, tools exist to monitor/trace network traffic, but I
    don't use them enough to make any recommendations.