Forum Discussion

Segovia123's avatar
Segovia123
Tuning in
3 months ago

DHCP Does Not Look Right- Multiple IP's for Single MAC Address

Multiple IP's for Single MAC Address, this can't be right, anyone else the same

  • Tudor's avatar
    Tudor
    Very Insightful Person

    I’m reading that 192.168.0.116 is the only device assigned a MAC address, the others are available. I presume the output is from the VM app, I don’t/can’t use it as I run in modem mode.

  • Adduxi's avatar
    Adduxi
    Very Insightful Person

    That whole DHCP table looks odd to me, as the last octets are repeated in places.  Maybe a pinhole reset would do the Hub the world of good .....  

    The only other thing I can think of is the Pod is getting one IP, and the rest are devices attached to the Pod?  Who knows, I don't use Pods and I certainly wouldn't use the Hub as a Router. 

  • The actual IP is 115, question is, where do the Self Assigned come from ?

    • Adduxi's avatar
      Adduxi
      Very Insightful Person

      That's a TP-Link MAC address for the Smart socket.  So assuming it's grabbed a DHCP lease and the Hub is reporting it as "Self Assigned".  

      • Segovia123's avatar
        Segovia123
        Tuning in

        It's not the only one, most of my devices have multiple IP's assigned according to the router , as this example

  • Client62's avatar
    Client62
    Alessandro Volta

    In the original post there is a table of IPs, the display format looks quite different to what we see from our VM Hub's Connected items web page.

    Exactly what are we looking at ? I.E. What make / model of device displayed that table of information ?

  • I have done a pin reset, and It's cleared up a bit, I only have two devices with multiple IP's, but I am still getting Self Assigned and DHCP, surely they must be one or another 

     

    • Segovia123's avatar
      Segovia123
      Tuning in

      The devices with multiple IP's are not my Mac devices, they are mainly smart sockets

  • Client62's avatar
    Client62
    Alessandro Volta

    The suggestion is any device may self allocate an IP if the DHCP response is incomplete / not received,
    which could be a DHCP server fault or a network cable fault.

    When a Window computers fail to get a DHCP response they self allocate in the 169.254.0.0/16 range
    which is very obvious as it fails to work on a domestic internet connection.

    There are so many smart devices I am assuming there is a network switch involved,
    if a smart plug was connected direct to the VM Hub does that work differently ?