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

    Multiple VLANs using DHCP on each interface

    Scheduled Pinned Locked Moved DHCP and DNS
    11 Posts 4 Posters 2.6k 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.
    • M Offline
      mtist_alby
      last edited by

      No help on this one? DHCP works fine on the internal interface for our LAN, just not the OPT1 or OPT2 interfaces. Please help.

      1 Reply Last reply Reply Quote 0
      • empbillyE Offline
        empbilly
        last edited by

        The VLANs 101 and 150 are connected to a switch or router? Make a small diagram of your infra.

        https://eliasmoraispereira.wordpress.com/

        1 Reply Last reply Reply Quote 0
        • M Offline
          mtist_alby
          last edited by

          The VLANs are 101 through 150 or 50 of them. All virtual interfaces on the OPT1 interface, connected to a switch on the inside network, trunked and passing all VLANs. When we set an address manually on clients connectivity to everywhere works. I have connected a PC directly to the interface and it will not get an address. With Wireshark running, I capture the ARP request, reply and DNS request no reply. I pasted the log from pfsense in the forum post. On the back end these are VMs using separate VLANs so they cannot connect. Thank you for helping me out.  :)

          1 Reply Last reply Reply Quote 0
          • A Offline
            a_null
            last edited by

            I have to ask - is your pass rule allowing UDP? And does each subnet have their own pool of addresses?

            \x0

            1 Reply Last reply Reply Quote 0
            • M Offline
              mtist_alby
              last edited by

              I attached a snippet of the actual rule. You will see it is on VLAN101 Interface. Our setup is interfaces VLAN101, VLAN102, VLAN103…..VLAN150. All set up with this rule. Our subnetting scheme is also as the interface configuration. 192.168.101.0/24, 192.168.102.0/24, 192.168.103.0/24........192.168.150.0/24. We are setting up a virtualized pool of servers behind all this. One pool for each student consisting of a couple windows servers and clients to do some active directory training among other things. When we configure them with static addresses it all works well. DHCP is our only problem. As I pointed out earlier, we attached a laptop to the OPT2 interface. The current VLANs are all created on OPT1. From OPT2 DHCP is also not talking. Client sends a request, no answer, as observed with Wireshark. ARP works fine.

              Got to be blocked somehow in these rules. Each interface only needs 1 rule passing any any, correct? Just like in the attachment. Thank you for helping out.

              VLAN101_rule.PNG
              VLAN101_rule.PNG_thumb

              1 Reply Last reply Reply Quote 0
              • jahonixJ Offline
                jahonix
                last edited by

                Rules are not your problem.

                dhcpd      Can't bind to dhcp address: Address already in use
                is your problem.
                Do you have another DHCP server somewhere or is your managed switch not passing DHCP?

                You did the obvious and enabled DHCP on each interface and defined a reasonable client range as well?

                1 Reply Last reply Reply Quote 0
                • M Offline
                  mtist_alby
                  last edited by

                  Only DHCP on the network with pfsense is pfsense. It is handing out addresses just fine on the LAN interface. That subnet is 192.168.1.0/24.

                  VLAN101 = 192.168.101.0/24
                  VLAN102 = 192.168.102.0/24
                  VLAN103 = 192.168.103.0/24
                  VLAN104 = 192.168.104.0/24
                  VLAN105 = 192.168.105.0/24
                  VLAN106 = 192.168.106.0/24
                                    .
                                    .
                                    .
                                    .
                  VLAN150 = 192.168.150.0/24

                  Thank you, jahonix. I got the joke but a couple of my students did not. I need to work on them a bit.

                  1 Reply Last reply Reply Quote 0
                  • M Offline
                    mtist_alby
                    last edited by

                    I attached a snippet of one of the DHCP services for VLAN101.

                    VLAN101_DHCP.PNG
                    VLAN101_DHCP.PNG_thumb

                    1 Reply Last reply Reply Quote 0
                    • jahonixJ Offline
                      jahonix
                      last edited by

                      Try a reboot.

                      1 Reply Last reply Reply Quote 0
                      • M Offline
                        mtist_alby
                        last edited by

                        I am at a loss for words. Glad and upset with myself at the same time. Can't believe I did not try that. It absolutely worked. DHCP is up and running on all the VLANs. Thank you

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