Netgate Discussion Forum
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Search
    • Register
    • Login

    Device has an assigned ip address but it does not appear on DHCP Leases

    DHCP and DNS
    2
    3
    636
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • I
      ikonomn
      last edited by ikonomn

      My firewall is 2.7.2-RELEASE (amd64) on a HP thin client.
      I have a Hikvision ip video intercom kit ds-kis604-s. The indoor station(monitor) and the door station both take an ip address for DHCP server. The indoor station appears only on ARP Table. The outdoor station does not appears on both DHCP Leases and ARP Table.
      Both devices appear using fping command.What is causing this problem.
      Regards

      GertjanG 1 Reply Last reply Reply Quote 0
      • GertjanG
        Gertjan @ikonomn
        last edited by

        @ikonomn said in Device has an assigned ip address but it does not appear on DHCP Leases:

        What is causing this problem

        Observe again the ARP table :

        3547c299-e969-4d33-a3d0-112b5ef20a1d-image.png

        this time, i marked in green the important thing : my arp table contains a line where it lists the relation between be:7f:ae:d4:1a:c1 and 192.168.1.115.
        After 405 seconds, if the entry isn't updated, it will be gone.

        If pfSense needs to talk to "192.168.1.115" again, it will execute a ARP broadcast" who has 192.168.1.115 and be:7f:ae:d4:1a:c1 will answer : me !!" and this reply will get cached for some time.

        This : the green flesh :

        37a3412b-e6de-4baa-b472-8ca1e7a6b14b-image.png

        means : its 'up' because it exists in the ARP cache.
        This doesn't mean that when its marked down (we are now 405 seconds later - see my arp cache image ) :

        cf2bc8b4-5d87-46ce-85ce-d73e73329f6a-image.png

        that the device is disconnected, or that the lease is gone.

        So, you get it now, pretty not useful ^^

        When I ping this 192.168.1.115, it will be green again.
        Not because it "replied to my ping".
        Much more is going on : because I executes a ping to an IP, and pfSense didn't know anymore to what MAC to talk to, so an arp broadcast was executed first, and the answer was cached, etc etc etc

        All this works in parallel with "DHCP" and can work without DHCP, as the device can also have static IP settings.

        If a device doesn't ask for a DHCP lease and you can still 'talk' to it using an IP then that is because you've set up a static IP (and DNS, and gateway and network details (mask) etc).

        As long as pfSense doesn't have to connect to the device, your indoor station,

        No "help me" PM's please. Use the forum, the community will thank you.
        Edit : and where are the logs ??

        I 1 Reply Last reply Reply Quote 1
        • I
          ikonomn @Gertjan
          last edited by

          @Gertjan Thanks a lot for the help.

          1 Reply Last reply Reply Quote 0
          • First post
            Last post
          Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.