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

    DHCP sometimes doesn't assign IP address

    Scheduled Pinned Locked Moved DHCP and DNS
    19 Posts 3 Posters 1.1k 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.
    • J
      Jarhead @Jarhead
      last edited by

      Wireless access point maybe?

      G 1 Reply Last reply Reply Quote 0
      • bingo600B
        bingo600 @galt007
        last edited by

        @galt007
        Do you have your "Old router" or a "Wifi Box" connected ?
        Those are the usual suspects, when having a rouge dhcp server.

        You might not catch the offender by doing a pfSense packet trace, if the rouge unit is on the same L2 net as your devices getting a 192.168.2.x DHCP IP.
        Well technically you should be able to see the broadcasts UDP 67/68.

        But i would make a "Mirror port" on your switch.
        On the Netgear make a "Free port" a mirror of your "TV port", connect your linux Box to the mirror port , and "Fire up Wireshark as root".

        In wireshark select your Cabled interface that is connected to the mirror port, and start "sniffing".

        To display filter wireshark to just show the captured DHCP packages, write : bootp - In the top line.

        8ab80c0b-bdeb-4a16-ad47-ac989b708765-image.png
        In the

        Now just sit back and wait for some dhcp packages to be shown.

        Locate the ones that hands out a DHCP Offer contaning a 192.168.2.x" IP address to the TV. And note the MAC Address of the device sending.

        Now to find the offender you have 2 choices (using the mac):

        1: Use your switch to track down the mac , to a specific port.

        2: Use a mac address lookup tool , to try to identify the vendor it was assigned to. Wireshark might already show the vendor in the packet trace.

        Lookup url's:
        https://www.wireshark.org/tools/oui-lookup.html
        http://www.coffer.com/mac_find/

        Happy hunting

        /Bingo

        If you find my answer useful - Please give the post a šŸ‘ - "thumbs up"

        pfSense+ 23.05.1 (ZFS)

        QOTOM-Q355G4 Quad Lan.
        CPUĀ  : Core i5 5250U, Ram : 8GB Kingston DDR3LV 1600
        LANĀ  : 4 x Intel 211, DiskĀ  : 240G SAMSUNG MZ7L3240HCHQ SSD

        G 1 Reply Last reply Reply Quote 1
        • G
          galt007 @Jarhead
          last edited by galt007

          @jarhead Geeting these on a packet capture of 192.168.2.0/24

          ARP, Request who-has 192.168.2.1 tell 192.168.2.110, length 46
          ARP, Request who-has 192.168.2.1 tell 192.168.2.110, length 46
          IP 192.168.2.110.38973 > 192.168.2.255.15600: UDP, length 35
          ARP, Request who-has 192.168.2.1 tell 192.168.2.110, length 46
          ARP, Request who-has 192.168.2.1 tell 192.168.2.110, length 46

          the 110 address is the DHCP assinged TV address

          AP's are setup in bridge mode without LAN ip addresses. WAN side of AP is DHCP but statically assigned by pfsense

          bingo600B 1 Reply Last reply Reply Quote 0
          • G
            galt007 @bingo600
            last edited by

            @bingo600 Thanks for the recipe. I did find a device 192.168.2.187 connected to my wifie network. Im going to reboot that AP and see if it connects again

            1 Reply Last reply Reply Quote 0
            • bingo600B
              bingo600 @galt007
              last edited by

              @galt007 said in DHCP sometimes doesn't assign IP address:

              ARP, Request who-has 192.168.2.1 tell 192.168.2.110, length 46

              You are probably looking for a device that uses : 192.168.2.1 as the ip address.
              That ARP request above , smell a lot of a Client (192.168.2.110) , arp'ing for it's default gateway (192.168.2.1). Most often the default gateway ip is the same as the DHCP server ip on SOHO devices..

              /Bingo

              If you find my answer useful - Please give the post a šŸ‘ - "thumbs up"

              pfSense+ 23.05.1 (ZFS)

              QOTOM-Q355G4 Quad Lan.
              CPUĀ  : Core i5 5250U, Ram : 8GB Kingston DDR3LV 1600
              LANĀ  : 4 x Intel 211, DiskĀ  : 240G SAMSUNG MZ7L3240HCHQ SSD

              G 1 Reply Last reply Reply Quote 1
              • G
                galt007 @bingo600
                last edited by

                @bingo600 @Jarhead Found the offending device. Actiontec ECB6000 Moca 2.0 network adapter.

                Found it the old school way. TV direct to main switch, started pulling ports until the TV was assigned a proper address from PfSense.

                Thanks for the help folks!

                bingo600B 1 Reply Last reply Reply Quote 0
                • bingo600B
                  bingo600 @galt007
                  last edited by

                  @galt007
                  Well done.

                  But from the manual : https://www.actiontec.com/wp-content/uploads/2017/02/ECB6000_UserManual.pdf

                  It doesn't seem like that device has a DHCP server built in. So i suppose the "Rouge Server" is at "The other end" of the Coax ...

                  What is it used for ??

                  If you find my answer useful - Please give the post a šŸ‘ - "thumbs up"

                  pfSense+ 23.05.1 (ZFS)

                  QOTOM-Q355G4 Quad Lan.
                  CPUĀ  : Core i5 5250U, Ram : 8GB Kingston DDR3LV 1600
                  LANĀ  : 4 x Intel 211, DiskĀ  : 240G SAMSUNG MZ7L3240HCHQ SSD

                  J G 2 Replies Last reply Reply Quote 0
                  • J
                    Jarhead @bingo600
                    last edited by

                    @bingo600 Had no idea what a rouge server was until the second time you posted it... rogue. 😊

                    bingo600B 1 Reply Last reply Reply Quote 0
                    • bingo600B
                      bingo600 @Jarhead
                      last edited by

                      @jarhead
                      Ah ... English isn't my native language (sorry)

                      If you find my answer useful - Please give the post a šŸ‘ - "thumbs up"

                      pfSense+ 23.05.1 (ZFS)

                      QOTOM-Q355G4 Quad Lan.
                      CPUĀ  : Core i5 5250U, Ram : 8GB Kingston DDR3LV 1600
                      LANĀ  : 4 x Intel 211, DiskĀ  : 240G SAMSUNG MZ7L3240HCHQ SSD

                      1 Reply Last reply Reply Quote 0
                      • G
                        galt007 @bingo600
                        last edited by

                        @bingo600 that's a good question. Think it came with my tivo which might explain why my tivo was trying to talk to 192.168.2.x.

                        Might have been how my tivo communicated with my tivo mini.

                        Main tivo works fine without it as it networked properly now.

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