Announcement

Collapse
No announcement yet.

Why is my Z-Net Multihomed (2 IP Addresses)?

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

    Why is my Z-Net Multihomed (2 IP Addresses)?

    I just did a local area network scan using Fing and it discovered 2 IP addresses tied to the physical Ethernet interface of the Z-Net on my network. I tried to connect to both via http and both really DO come up as the Z-Net!

    I then SSHed into the device and did an ifconfig but only see the interface bound to the one static IP I gave it! I do not understand this.

    Anybody seen this? What should I do?
    ---------------------------------------------------
    Jean-Marie G. Vaneskahian
    jean@vaneskahian.com
    ---------------------------------------------------

    #2
    Is the second ip adres perhaps a reservation from the dhcp server for the lease period? Try rebooting the router.

    Comment


      #3
      I rebooted the router... and checked the DHCP clients... Nope, this is not coming from the router's DHCP server. It is VERY bizzare. Plus, I would expect to see the second address bound to the Ethernet interface on the Z-Net in the OS.

      Has anyone else gotten a Z-Net with two addresses bound to it? Has anyone scanned their network to verify?

      Here is my arp table
      --------------------------
      192.168.1.7 b8-27-eb-72-d6-09
      192.168.1.191 b8-27-eb-72-d6-09
      --------------------------

      That is the MAC address of the Z-Net.. the Static one I assigned is 192.168.1.7, there is no DHCP or even a hint of 192.168.1.191.... This is very strange!
      ---------------------------------------------------
      Jean-Marie G. Vaneskahian
      jean@vaneskahian.com
      ---------------------------------------------------

      Comment


        #4
        Why is my Z-Net Multihomed (2 IP Addresses)?

        I can't remember the details, but I vaguely remember seeing this as an issue in the rasbian OS. Google for it and you will find the fix.

        It's something related to setting a static IP and it still grabbing or holding onto the dynamic IP.

        Personally I just left mine dhcp and it's just worked.

        Comment


          #5
          Originally posted by jeanv View Post
          I rebooted the router... and checked the DHCP clients... Nope, this is not coming from the router's DHCP server. It is VERY bizzare. Plus, I would expect to see the second address bound to the Ethernet interface on the Z-Net in the OS.

          Has anyone else gotten a Z-Net with two addresses bound to it? Has anyone scanned their network to verify?

          Here is my arp table
          --------------------------
          192.168.1.7 b8-27-eb-72-d6-09
          192.168.1.191 b8-27-eb-72-d6-09
          --------------------------

          That is the MAC address of the Z-Net.. the Static one I assigned is 192.168.1.7, there is no DHCP or even a hint of 192.168.1.191.... This is very strange!
          Same here.

          This is the article Wayne was probably referring to. I just turned dhcpcd off. Note they also have dhclient running as well. No idea way.

          https://superuser.com/questions/9833...097873#1097873

          Be sure to change the default PI password as well if you haven't already.

          Z

          Comment


            #6
            That did it!!! So is this not happening to everyone?

            Thanks so much!!!

            What made no sense is why it was not showing up with an ifconfig?
            ---------------------------------------------------
            Jean-Marie G. Vaneskahian
            jean@vaneskahian.com
            ---------------------------------------------------

            Comment


              #7
              Interesting issue. Ethernet peer-to-peer comms utilize the MAC, not the IP address. Your PC ARP table had the same MAC entry for both IP's - my guess is that the rpi was answering via its MAC address and didn't necessarily know about the other IP.

              Comment


                #8
                Originally posted by jeanv View Post
                That did it!!! So is this not happening to everyone?

                Thanks so much!!!

                What made no sense is why it was not showing up with an ifconfig?
                What did it?

                Comment


                  #9
                  I disabled DHCP as per the posting. Now the Z-Net only answers to the configured static address. The odd part is that the other IP would not show up with an ifconfig.
                  ---------------------------------------------------
                  Jean-Marie G. Vaneskahian
                  jean@vaneskahian.com
                  ---------------------------------------------------

                  Comment


                    #10
                    Thnx
                    Basically this means there is a implementation flaw in the gui. Hopefully solved in next version.
                    Last edited by edwin2008; August 28, 2017, 12:13 AM.

                    Comment


                      #11
                      Here downgraded my old RPi2 (which is ZNet like) to Wheezy from Jessie lite a few months back. Noticed the same feature as described above:

                      The raspberry pi foundation chose to use neither of these and instead use dhcpcd5 for network configuration in their raspbian images. dhcpcd5 is packaged in Debian but the raspberry pi foundation raspbian images are the only Debian-based system I know of to use it by default.

                      I really didn't notice until a reboot as I had already configured the device for a static IP.

                      Relating to the Homeseer Zee-2 GUI here the static IP configuration has never been correct and I have always configured the IP via the command line.

                      This is a left over from the original Zee days.

                      [ATTACH]63014[/ATTACH]

                      The only correct piece above is the static IP. The subnet mask, gateway address are incorrect.

                      I do not touch or change this today with the Zee-2 Homeseer GUI.

                      Note too that on the original Homeseer Standard and Pro for Linux the same issue occurred relating to IP configuration (static GUI) and this was removed as today my Homeseer 3 Pro for Linux does not include a Homeseer GUI section for either DHCP or Static IP addressing.

                      There will be more changes with the RPi "Stretch" - IE: Debian 9 coming soon.

                      Wheezy (Debian 7) ==> Jessie (Debian 8) ==> Stretch (Debian 9)

                      It gets more complicated now as you have both a hotplug (wireless and/or wired) and new dhcpcd5 network configuration.
                      Last edited by Pete; August 28, 2017, 07:56 AM.
                      - Pete

                      Auto mator
                      Homeseer 3 Pro - 3.0.0.548 (Linux) - Ubuntu 18.04/W7e 64 bit Intel Haswell CPU 16Gb
                      Homeseer Zee2 (Lite) - 3.0.0.548 (Linux) - Ubuntu 18.04/W7e - CherryTrail x5-Z8350 BeeLink 4Gb BT3 Pro
                      HS4 Lite - Ubuntu 22.04 / Lenovo Tiny M900 / 32Gb Ram

                      HS4 Pro - V4.1.18.1 - Ubuntu 22.04 / Lenova Tiny M900 / 32Gb Ram
                      HSTouch on Intel tabletop tablets (Jogglers) - Asus AIO - Windows 11

                      X10, UPB, Zigbee, ZWave and Wifi MQTT automation-Tasmota-Espurna. OmniPro 2, Russound zoned audio, Alexa, Cheaper RFID, W800 and Home Assistant

                      Comment


                        #12
                        Originally posted by edwin2008 View Post
                        Thnx
                        Basically this means there is a implementation flaw in the gui. Hopefully solved in next version.
                        This isn't a homeseer problem, this is a problem with the Raspian Jessie OS, it's been fixed in the later versions of Jessie, but probably the OS version that homeseer used at the time of production had the flaw in it. You can fix the issue by updating the OS to the latest version, but you take risk that you break everything and lose support as its not a tested configuration.

                        Homeseer can resolve the issue by vetting out the latest version of Jessie and then just push out during one of their updates to have the znet update the OS.

                        Comment


                          #13
                          Originally posted by jeanv View Post
                          That did it!!! So is this not happening to everyone?

                          Thanks so much!!!

                          What made no sense is why it was not showing up with an ifconfig?
                          I would suspect most like me leave the znet dhcp and you would never see this issue because of that. I've never had a reason to make it static and its never given me issues. I just treat it as another iOT device in the house and just block its communication to the outside world.

                          Comment


                            #14
                            I really appreciate everyone's feedback! It all makes alot of sense and I understand the issue now. I have resolved mine by disabling the DHCP service that is being used. I do wonder however why others have not brought this up. I assume as was stated earlier, most use DHCP or setup DHCP reservations.

                            Thanks again everyone!!
                            ---------------------------------------------------
                            Jean-Marie G. Vaneskahian
                            jean@vaneskahian.com
                            ---------------------------------------------------

                            Comment


                              #15
                              Originally posted by jeanv View Post
                              I do wonder however why others have not brought this up. I assume as was stated earlier, most use DHCP or setup DHCP reservations.
                              I don't believe this particular flaw causes much if any operational issue. A bigger issue with Homeseer's static IP implementation is the inability to specify the DNS server(s). This has caused issues for several folks; the solution has been to revert to DHCP (and reserve an address in the router).

                              Comment

                              Working...
                              X