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

    No IP given/accepted

    Scheduled Pinned Locked Moved DHCP and DNS
    4 Posts 2 Posters 565 Views
    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.
    • QinnQ
      Qinn
      last edited by

      Since a few hours I have an endless

      DHCPOFFER on 172.16.20.23 to 7c:dd:90:85:c4:ea via igb1.1007
      DHCPDISCOVER from 7c:dd:90:85:c4:ea via igb1.1007

      In the DHCP log op PFS, normaly I would expect DHCPREQUEST followed by a DHCPACK on. This is one mobile device, that's logged in on a Access Point (from the logging of the AP, I can see they are connected), but this one isn't getting an IP?

      Can anyone shine some light on it,

      Cheers Qinn

      Hardeware: Intel(R) Celeron(R) J4125 CPU @ 2.00GHz 102 GB mSATA SSD (ZFS)
      Firmware: Latest-stable-pfSense CE (amd64)
      Packages: pfBlockerNG devel-beta (beta tester) - Avahi - Notes - Ntopng - PIMD/udpbroadcastrelay - Service Watchdog - System Patches

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

        Hi,

        In case of doubt, fireshark the DHCP dialog.

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

        1 Reply Last reply Reply Quote 0
        • QinnQ
          Qinn
          last edited by

          @Gertjan:

          Hi,

          In case of doubt, fireshark the DHCP dialog.

          Thanks, I did that, but didn't see nothing that could explain it. For now it seems the power from the AP was too low and the distance to this client was too far so RSSI was -83 and connection could not be made. I raised the power to 23dBm and instantly connection was made.
          Although I am not fond of raising the power from one direction, as the connection is made from both side AP to client and client to AP, it did work?

          Hardeware: Intel(R) Celeron(R) J4125 CPU @ 2.00GHz 102 GB mSATA SSD (ZFS)
          Firmware: Latest-stable-pfSense CE (amd64)
          Packages: pfBlockerNG devel-beta (beta tester) - Avahi - Notes - Ntopng - PIMD/udpbroadcastrelay - Service Watchdog - System Patches

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

            Nice touch !

            The DHCPDISCOVER means that an initial UDP packet came through, because logged and answered as such on pfSEnse.
            One tends to say that the "data path" = the connection works.

            The DHCPOFFER uses the same path back and probably never made it.

            (or : worse : the mobile device didn't understand the "DHCPOFFER"  from pfSense, and then you're out of business right away, mobile device are hard to debug  ;)).

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

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