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 2-4 connections that are not identified by device name and sometimes not even by IP address.  All are identified by MAC address but they are unknown to me.  I've changed the password and this seems to have no effect on the mystery connections.  Should I be concerned? Are these "phantom" connections somehow related to the laptops, printers, TIVO or XBox 360 that are connected to the wireless network?  Any thoughts would be welcomed. 

  • > [...] 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.

7 Replies

  • I am having the same issue on my router.  Except it shows up as a WIRED connection.  I have no wired connections.  I blocked it as I fear it is spyware,  I have reloaded the frmware, but it still can get rid of it.  This just started occuring.  I've been sing this router for well over a year with no issues.

    • > I am having the same issue on my router. Except it shows up as a
      > WIRED connection. [...]

       

         So, exactly the same, except for the different hardware, the
      different firmware, and the different behavior?  Might be a good reason
      to start a new, different thread.

       

         I may be easily mystified, but I can't understand why anyone would
      report a problem like "I'm seeing strange/unexpected stuff, but I won't
      actually show you any of it."  Copy+paste is your friend.

       

      > [...] I have no wired connections. [...]

       

         If nothing is connected to any of the LAN Ethernet ports on the
      router, then I see no good excuse for the firmware saying that there is
      one.

       

      > [...] I blocked it as I fear it is spyware, [...]

       

      At least one of us seems to have no idea what "spyware" means.

      • sgc1's avatar
        sgc1
        Aspirant

        All very helpful responses.  thank you.   If you do some research on the web, there are infections that are happeing across various models and brands of wireless routers  This appears to be one of the signs of an infected router.   I had a linksys a few years ago, and after a while, the same thing happened.  That was the reason I decided to try NETGEAR, but apparently the issue goes across brands.