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

    Odd DHCP lease entry

    Scheduled Pinned Locked Moved DHCP and DNS
    19 Posts 4 Posters 1.3k 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.
    • provelsP
      provels @johnpoz
      last edited by provels

      @johnpoz
      It's an old Buffalo (2008) 54Mb with DD-WRT, WPA-2, AES (PSK n/a) used for phones and laptop. Anything else is static. OK, will just delete it and see what happens. Thanks for the help. If it suddenly pops up again, I think I'll just go static addressing. Will post if anything changes. Thanks again, have a great holiday!

      Peder

      MAIN - pfSense+ 24.11-RELEASE - Adlink MXE-5401, i7, 16 GB RAM, 64 GB SSD. 500 GB HDD for SyslogNG
      BACKUP - pfSense+ 23.01-RELEASE - Hyper-V Virtual Machine, Gen 1, 2 v-CPUs, 3 GB RAM, 8GB VHDX (Dynamic)

      johnpozJ 1 Reply Last reply Reply Quote 0
      • johnpozJ
        johnpoz LAYER 8 Global Moderator @provels
        last edited by

        It could be something glitched as well - Have seen reports of say TVs wifi mac addresses going all funky etc..

        I would make sure you delete the lease.. Yeah change your psk, and then see if any of your devices loose their connection..

        But again unless your using something like wep or open.. And you actually have a secure WPA2 psk setup - its unlikely the kid next door hacked your wifi ;)

        An intelligent man is sometimes forced to be drunk to spend time with his fools
        If you get confused: Listen to the Music Play
        Please don't Chat/PM me for help, unless mod related
        SG-4860 24.11 | Lab VMs 2.8, 24.11

        provelsP 1 Reply Last reply Reply Quote 1
        • provelsP
          provels @johnpoz
          last edited by

          @johnpoz said in Odd DHCP lease entry:

          WPA2 psk

          Is AES OK?

          Peder

          MAIN - pfSense+ 24.11-RELEASE - Adlink MXE-5401, i7, 16 GB RAM, 64 GB SSD. 500 GB HDD for SyslogNG
          BACKUP - pfSense+ 23.01-RELEASE - Hyper-V Virtual Machine, Gen 1, 2 v-CPUs, 3 GB RAM, 8GB VHDX (Dynamic)

          johnpozJ 1 Reply Last reply Reply Quote 0
          • johnpozJ
            johnpoz LAYER 8 Global Moderator @provels
            last edited by

            Yea wpa2 psk should default to AES/CCMP only.. vs possible depreciated tkip..

            An intelligent man is sometimes forced to be drunk to spend time with his fools
            If you get confused: Listen to the Music Play
            Please don't Chat/PM me for help, unless mod related
            SG-4860 24.11 | Lab VMs 2.8, 24.11

            provelsP 1 Reply Last reply Reply Quote 1
            • provelsP
              provels @johnpoz
              last edited by

              @johnpoz
              Thanks, that's what I have.

              Peder

              MAIN - pfSense+ 24.11-RELEASE - Adlink MXE-5401, i7, 16 GB RAM, 64 GB SSD. 500 GB HDD for SyslogNG
              BACKUP - pfSense+ 23.01-RELEASE - Hyper-V Virtual Machine, Gen 1, 2 v-CPUs, 3 GB RAM, 8GB VHDX (Dynamic)

              johnpozJ 1 Reply Last reply Reply Quote 0
              • johnpozJ
                johnpoz LAYER 8 Global Moderator @provels
                last edited by johnpoz

                Is your actual psk secure.. Something closer to 33S^vHwFGMce6FStGOXk vs P@55w0rd! ;)

                @johnpoz
                It's an old Buffalo (2008) 54Mb with DD-WRT

                So your only running G for wireless? ugggh ;)

                An intelligent man is sometimes forced to be drunk to spend time with his fools
                If you get confused: Listen to the Music Play
                Please don't Chat/PM me for help, unless mod related
                SG-4860 24.11 | Lab VMs 2.8, 24.11

                provelsP 1 Reply Last reply Reply Quote 0
                • provelsP
                  provels @johnpoz
                  last edited by provels

                  @johnpoz
                  It's a 26 character phrase (and not ABCD...Z!)

                  Do I really need gig throughput to read my mail? :)

                  One man show. I mostly RDP to my basement network which is gig. The Buffalo switch is 10/100 so my main floor hardwired has 100. If interested I can give an inventory of my antiques...

                  On another topic, if you would care to look at this post, I'd appreciate any input. I'm all kinds of trouble today! :)
                  https://forum.netgate.com/topic/159371/traffic-shaping-not-honored
                  Thanks again for your help.

                  Peder

                  MAIN - pfSense+ 24.11-RELEASE - Adlink MXE-5401, i7, 16 GB RAM, 64 GB SSD. 500 GB HDD for SyslogNG
                  BACKUP - pfSense+ 23.01-RELEASE - Hyper-V Virtual Machine, Gen 1, 2 v-CPUs, 3 GB RAM, 8GB VHDX (Dynamic)

                  1 Reply Last reply Reply Quote 0
                  • R
                    Rod-It
                    last edited by

                    Any IOS14 devices using private mac?

                    Disable it if so and see if the issue goes away.

                    provelsP 1 Reply Last reply Reply Quote 0
                    • provelsP
                      provels @Rod-It
                      last edited by

                      @rod-it
                      Thanks for the reply, but no. I had plugged in a new streamer device on 12/23 that had a mfg date of 11/13, but the lease was 12/13. ¯_ (ツ)_/¯ I have deleted and will observe. Thanks again.

                      Peder

                      MAIN - pfSense+ 24.11-RELEASE - Adlink MXE-5401, i7, 16 GB RAM, 64 GB SSD. 500 GB HDD for SyslogNG
                      BACKUP - pfSense+ 23.01-RELEASE - Hyper-V Virtual Machine, Gen 1, 2 v-CPUs, 3 GB RAM, 8GB VHDX (Dynamic)

                      1 Reply Last reply Reply Quote 0
                      • R
                        Rod-It
                        last edited by

                        Does ping -a 192.168.0.103 give you anything, perhaps a name or brand was cached that might help you?

                        Whatever it is, you're not alone, it's been posted many times over the years, and on multiple forums.

                        https://forum.netgate.com/topic/43720/mac-address-00-ab-00-00-00-00/

                        A few people suggest this is some type of IoT based device with cheap network kit where the mac is spoofed to whatever they want it to be, other people say it's bootp.

                        Are you running your ISPs modem in bridged mode, could it be this?

                        provelsP 1 Reply Last reply Reply Quote 0
                        • provelsP
                          provels @Rod-It
                          last edited by provels

                          @rod-it
                          No, no reply. I have my own modem, so I don't think so. Thanks for the link. Maybe it's my TV or a laptop I rebuilt for a friend. ¯\_ (ツ)_/¯

                          Peder

                          MAIN - pfSense+ 24.11-RELEASE - Adlink MXE-5401, i7, 16 GB RAM, 64 GB SSD. 500 GB HDD for SyslogNG
                          BACKUP - pfSense+ 23.01-RELEASE - Hyper-V Virtual Machine, Gen 1, 2 v-CPUs, 3 GB RAM, 8GB VHDX (Dynamic)

                          1 Reply Last reply Reply Quote 0
                          • R
                            Rod-It
                            last edited by

                            I'd probably do as suggested on that other thread, set it to a DHCP reservation for that mac, then create a firewall block rule for the IP. Keep an eye on the states for that rule, look in to it if anything is shown and that may give you a clue - or when you realise something is no longer working.

                            I hope you find the culprit though

                            provelsP 1 Reply Last reply Reply Quote 1
                            • provelsP
                              provels @Rod-It
                              last edited by

                              @rod-it
                              Appreciate the support. Thanks!

                              Peder

                              MAIN - pfSense+ 24.11-RELEASE - Adlink MXE-5401, i7, 16 GB RAM, 64 GB SSD. 500 GB HDD for SyslogNG
                              BACKUP - pfSense+ 23.01-RELEASE - Hyper-V Virtual Machine, Gen 1, 2 v-CPUs, 3 GB RAM, 8GB VHDX (Dynamic)

                              1 Reply Last reply Reply Quote 0
                              • JKnottJ
                                JKnott @johnpoz
                                last edited by

                                @johnpoz said in Odd DHCP lease entry:

                                Anything that is not all zeros would really be viable mac address I would think.

                                You might want to avoid mulitcast MAC addresses. Those are any with the least significant bit of the first octet. That would also include the broadcast MAC of all 1s.

                                PfSense running on Qotom mini PC
                                i5 CPU, 4 GB memory, 32 GB SSD & 4 Intel Gb Ethernet ports.
                                UniFi AC-Lite access point

                                I haven't lost my mind. It's around here...somewhere...

                                provelsP 1 Reply Last reply Reply Quote 0
                                • provelsP
                                  provels @JKnott
                                  last edited by

                                  @johnpoz @Rod-It
                                  Just thinking this over again. A while back I tried to mount a USB wireless NIC to my pfSense VM. I tried using both Windows Internet Connection Sharing and bridging in both Windows and pfSense, trying to create an wireless access point. The exercise failed, but maybe bridging is the the cause.

                                  Peder

                                  MAIN - pfSense+ 24.11-RELEASE - Adlink MXE-5401, i7, 16 GB RAM, 64 GB SSD. 500 GB HDD for SyslogNG
                                  BACKUP - pfSense+ 23.01-RELEASE - Hyper-V Virtual Machine, Gen 1, 2 v-CPUs, 3 GB RAM, 8GB VHDX (Dynamic)

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