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

DHCP totally not working right

DHCP and DNS
2
2
494
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.
  • V
    vitronix
    last edited by Feb 14, 2015, 7:51 PM

    Hello,

    I am a newbie to pfSense and Linux, I used to run a SmoothWall firewall but I'm attracted by the many features pfSense offers.
    My system is a Intel pentium 64-bit dual-core with 3 Realtek NIC's build in and one present on the mainboard.
    I used the psSense 64-bit, 2.2 release.
    To get started I kept things simple, the build in NIC is connected to my NetGear router so this is the WAN card re0, IP v4 address 192.168.1.x
    The LAN card rl0 has an IP address of 192.168.10.1 /24
    I wanted a DHCP pool of 192.168.10.200 to 192.168.10.250. I set the DHCP server using the console as well a the web-based gui.
    No matter what I do my clients sometimes get an IP adress of 10.0.100.x of course now I'm writing this post everything works as intended.

    Has anyone got similar problems with the setup of the DHCP server?

    I also should mension that I started with a more complex set up, including a NIC for my WAP and one for a DMZ.
    I realized that I should go for a simple configuration to get used to the web-interface and the many features of pfSense.
    So I reinstalled the hole thing using the console.
    Could it be that there are some configuration settings kept from the first install ? (I don't think so since the HDD is formatted and overwritten).

    Sorry for the poor English (I'm Dutch)
    Thanks in advace,

    vitronix

    1 Reply Last reply Reply Quote 0
    • D
      Derelict LAYER 8 Netgate
      last edited by Feb 14, 2015, 8:04 PM

      You are getting DHCP from somewhere else, not pfSense.  Make sure there are no other DHCP servers on your network.  The client might tell you what it thinks its DHCP server is (ipconfig /all in windows, for instance)

      Chattanooga, Tennessee, USA
      A comprehensive network diagram is worth 10,000 words and 15 conference calls.
      DO NOT set a source address/port in a port forward or firewall rule unless you KNOW you need it!
      Do Not Chat For Help! NO_WAN_EGRESS(TM)

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