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

    My config info to help ID the reason for DHCP not working

    Scheduled Pinned Locked Moved L2/Switching/VLANs
    4 Posts 2 Posters 402 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.
    • C
      ccgc
      last edited by

      Re: Netgate to Netgear config - VLANs cannot get DHCP or connect to the internet
      Pls see images to follow

      Netgate config
      interfaces-vlan.jpg
      interfaces-vlan.jpg
      interfaces video.png
      video dhcp.png
      video dhcp.png
      firewall rules.png

      Port 48 is the uplink from netgear to netgate
      netgear vlan20.png
      netgear vlan1 membership.png
      netgear vlan20 membership.png
      netgear pvid config.png

      Port 48 VLAN Tag is 1,20

      G 1 Reply Last reply Reply Quote 0
      • G
        Gblenn @ccgc
        last edited by

        @ccgc Here's where I think you got it wrong. If port 48 is attached to pfsense, then that port needs to have any and all VLAN ports as Tagged, not Untagged.

        9dd103ce-ad8c-4e9c-9ec3-42589deee440-image.png

        C 1 Reply Last reply Reply Quote 1
        • C
          ccgc @Gblenn
          last edited by

          @Gblenn
          Thanks for your reply. I tried changing that but it still is not handing out DHCPs. Any other thoughts?
          Thanks again,
          Leon

          G 1 Reply Last reply Reply Quote 0
          • G
            Gblenn @ccgc
            last edited by Gblenn

            @ccgc I also notice now that on this view, you have all the ports 1-8 Tagged instead of Untagged?

            3c37ad16-951e-4fda-a3c6-77b63306ab1f-image.png

            Did you follow this guide?

            https://kb.netgear.com/31026/How-to-configure-a-VLAN-on-a-NETGEAR-managed-switch

            And you really don't have to do anything with VLAN 1, except remove it from the ports you want to have as access ports for VLAN 20 (VIDEO).

            And of course, VIDEO has to have a different subnet range than LAN. So if VIDEO has 192.168.0.1/24 you have to use something other than 192.168.0.

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