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

    Simple DHCP Relay configuration?

    Scheduled Pinned Locked Moved DHCP and DNS
    1 Posts 1 Posters 2.4k 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.
    • S
      SSzretter
      last edited by

      I am trying to figure out how I can have a machine on the "LAN" nic of pfSense get a DHCP address from a DHCP server on the "WAN" nic of pfSense (happens to be a Windows Server 2003 machine if that matters).

      I tried turning off the pfSense DHCP and turning on the "Enable DHCP relay on lan interface" and using either the 'proxy requests to dhcp server on wan subnet' or typing in the ip address of the dhcp server (172.16.1.3). The client machines just time out trying to reach a dhcp server (tried on win xp and win 7).

      I thought maybe the issue is the ip subnet, so I tried changing the LAN ip address to a 172.16.1.19 address, but then for some reason it does not work at all - I can not access the pfSense web admin when setting my machine to a static 172.16.1.4 for example. I checked that .19 and .4 are not being used on the WAN or LAN.

      Details:

      I have a simple install of pfSense, two nic cards. All the settings are default from the install and I did not block anything, meaning my firewall settings screen shows no filters. No VLANs, no routes, etc.

      My "WAN" nic is set to use dhcp to get it's address (172.16.1.20). My "LAN" nic is set to a static "192.168.1.1" address.

      If I have DHCP turned on for the LAN interface and plug a machine in to the LAN side, it works great - I get a 192.168.1.x address on the machine and I can communicate through to the WAN.

      I can not figure out how to have pfSense pass the dhcp request through to the WAN port and get an ip address that way (within the 172.16.1.x range)?

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