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

    DHCP not working as expected!?

    Scheduled Pinned Locked Moved DHCP and DNS
    7 Posts 4 Posters 512 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.
    • F
      FSC830
      last edited by

      Hi,
      at first: all of the following is in an virtual environment, pfSense as well as the Windows hosts.
      It is setup as a sandbox for playing and testing prior doing changes at my NetGate appliance.

      The virtual pfSense is version 2.6.0, the setup is as follows:

      Interfaces:
      WAN: 172.16.0.0/16
      LAN: 192.168.64.0/24
      Opt1: 192.168.20.0/24
      Opt2: 192.168.30.0/24
      Wireguard (not in use in sandbox)

      In each of the Opt networks a host exists with a static IP 192.168.20.10/192.168.30.10.
      Each host can ping the other and into the (virtual) WAN, the pfSense address is in every network x.x.x.111

      All runs fine, as long as the hosts are configured with static IPs.
      But after configuring DHCP weird things happened:

      1. the host IP is out of DHCP range!?
      2. the gateway/DNS IP is not the IP from the pfSense interface!?
      3. access to other networks is not possible any longer!?
      4. DHCP leases are not seen!?

      #2 can explain #3, but why is IP not matching the interface IP and why is host IP out of DHCP scope?

      Any ideas?
      BTW: in my appliance all works as expected, may be the 2.6.0 software, which is buggy?

      Screenshots from pfSense:
      09765bb1-da4f-49ec-83a8-8ba29ebce14a-grafik.png

      3bd3371a-841c-4e8d-b766-2b3596ace073-grafik.png

      d6b639f7-60fd-4789-b6df-1af36d4b575a-grafik.png

      Screenshots from host:

      Sorry for German GUI, but IP and commands are clearly seen and need no translation.

      6eaea85c-aae1-4742-bd1f-ceab1758fb4e-grafik.png

      Ping when DHCP was enabled:

      933fae90-b78e-40fd-9701-dda070cee309-grafik.png

      Ping when static IP was set (lower command):

      2c1bf2ba-8c16-496b-a8f9-efaa0078f43f-grafik.png

      V J 2 Replies Last reply Reply Quote 0
      • V
        viragomann @FSC830
        last edited by

        @fsc830
        e2ff925e-2263-406c-80bf-0cdb1250e1d9-grafik.png

        This should give you an answer, I think.

        1 Reply Last reply Reply Quote 0
        • J
          Jarhead @FSC830
          last edited by

          @fsc830 You don't say what IP's you used as gateways but I would try to find out what the .254 that's handing out IP addresses is first.

          1 Reply Last reply Reply Quote 0
          • F
            FSC830
            last edited by FSC830

            Thanks, I actually did not see this, but... there is no server with this IP in this network!?
            Same in other network:
            Currently host in 192.168.30.x uses static IP, host in 192.168.20.x is still using DHCP.
            So where does this IP is coming from??

            d9179778-4355-48be-bf8b-62ba13f9de0f-grafik.png

            Regards

            Edit: the gateways are always 192.168.x.111, but as seen, 192.168.x.1 as DNS and gateway is empty.

            V 1 Reply Last reply Reply Quote 0
            • V
              viragomann @FSC830
              last edited by

              @fsc830
              It's probably your virtualization environment, which has DHCP server enabled on the virtual networks.

              1 Reply Last reply Reply Quote 1
              • F
                FSC830
                last edited by

                😵 😵

                Hero of the day. I disabled the VM DHCP, but after modifying a setting it seems, that is was enabled again.
                Now everything is as configured.

                head -> desk, again and again... thanks, was focused at the pfSense.

                Regards

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

                  @fsc830 said in DHCP not working as expected!?:

                  was focused at the pfSense.

                  What is more likely - you have a rouge dhcp, or pfsense handing out info you didn't set it - and not logging that it handed anything out ;)

                  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

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