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

    Cannot get DHCP functioning on 2nd Interface

    Scheduled Pinned Locked Moved DHCP and DNS
    20 Posts 5 Posters 2.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
      Jedi2155
      last edited by

      After 3 weeks of trying to solve this issue, I'm about to return my hardware appliance and get a UniFi if I can't figure this out, its my last week before my return window trying to get PFsense working....

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

        @Jedi2155

        Wait ...

        You are having troubles with the 'second' network.
        What happens when you make LAN this second network, and the second network LAN ?
        If the issues follows the NIC, you might have a NIC that can receive but not send ?!

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

        J 2 Replies Last reply Reply Quote 0
        • J
          Jedi2155 @Gertjan
          last edited by Jedi2155

          @Gertjan

          I tried that a few weeks ago and it actually worked (DHCP and all). It has to be a configuration issue and I cannot figure it out for the life of me. As I said, the LAN connection works if I:

          1 - Manually assign a static IP
          2 - When I had a VLAN setup to this LAN and the end device, DHCP works perfectly!
          3 - When I configure it as a simple LAN interface and I also tried bridging it, I cannot get it to work.

          Primary LAN is a i226LM, secondary is a i226V

          I've also double checked the BIOS settings (it's a Minisforum MS-01.
          Last thing I'm going to try to backup my config, wipe everything and try to reconfigure it from scratch.

          I presently only have PFsense installed (directly, no proxmod or virtualization yet) and I'm using this as a HomeLab eventually. Was dipping my hand into PFSense trying to do more control before return to a commercial solution.

          1 Reply Last reply Reply Quote 0
          • J
            Jedi2155 @Gertjan
            last edited by

            @Gertjan

            So I wiped the disk, and reinstalled from scratch, and before I did anything else, I configured the second LAN, and it worked.....I then reloaded my saved config I backed up prior to the wipe, and it was still working....

            So something broke that wasn't related to my configuration and I have no idea what. So at this stage ( I had tried several attempts to reboot/reroot and lots of things, but something in the install broke basically).

            D 1 Reply Last reply Reply Quote 1
            • the otherT the other referenced this topic on
            • D
              Danyo @Jedi2155
              last edited by

              @Jedi2155 This is probably a bit late, but it might still help others out in the future:

              If you have this issue, with the MS-01, it isn't your fault. It has to do the with I226-lm. It has intel Vpro on it, which for some reason messes with the DHCP leases. It's a known issue that's been around for a year or 2.

              I was struggling with the same issue for a week or so until I stumbled upon an article that explained this in more detail.

              On other systems you can turn off intel Vpro properly, but on the ms-01 it doesn't fix it for some reason.

              J 1 Reply Last reply Reply Quote 0
              • J
                Jedi2155 @Danyo
                last edited by Jedi2155

                @Danyo Thank you! I got it working now generally but it doesn't work in all cases and it depends on the end device. For example the i226-LM DHCP works with my Desktop which has an Intel NIC but it doesn't work if I plug it into my laptop (which doesn't have an Intel NIC), or my LG TV. This only applies to the i226-LM as you suggested but not the i226-V.

                I'm wondering what within your research suggested issues with Vpro (which when I googled) is an umbrella term for dozens of features including several VM ones which are toggleable on the MS-01 BIOS. I have moved pfsense into a proxmox container so VM features are pretty useful even I don't know what they all do (yet).

                D 1 Reply Last reply Reply Quote 0
                • D
                  Danyo @Jedi2155
                  last edited by Danyo

                  @Jedi2155 I found several topics about it, but the main reason for it is this:

                  https://www.asrockind.com/en-gb/index.php?route=newsblog/faq&faq_id=91

                  On asrock boards they have the option to fully turn the function off, which allows DHCP leases to work once again.

                  edit.: it's interesting that it does work with intel devices on the other end, I have only tried my laptop and TV, and neither work, I might give my desktop a try later see if that works. Or just cave in and use that connection for the WAN side.

                  T 1 Reply Last reply Reply Quote 0
                  • T
                    thewho @Danyo
                    last edited by

                    @Danyo Where did you read about the Intel devices works? i have searching about everywhere to find more info about this problem.

                    1 Reply Last reply Reply Quote 0
                    • D
                      DrSKiZZ
                      last edited by

                      Its a firmware bug on that Intel port with remote management. Minisforum is aware as I have been complaining about for over a year now. You'll have to use one of the SFP+ ports. I've heard turning on KEA DHCP may fix it.

                      J 1 Reply Last reply Reply Quote 0
                      • J
                        Jedi2155 @DrSKiZZ
                        last edited by

                        @DrSKiZZ

                        I was able to fix it by wiping and re-installing PFsense strangely. I also might've turned off some of those remote management features in the BIOS during the wipe that was turned on before the wipe.

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