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

    DHCP server fail with error in config

    Scheduled Pinned Locked Moved 2.0-RC Snapshot Feedback and Problems - RETIRED
    7 Posts 2 Posters 4.0k 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.
    • G
      GoldServe
      last edited by

      I am using a 6/4 snapshot and everything was going fine (configured two WANs, 1 LAN, 1 WLAN) until I rebooted. I could not get any dhcp address and I found the following:

      When I log into the console, the WLAN interface address does not show:

      *** Welcome to pfSense 2.0-BETA2-pfSense (i386) on lanner_pfsense ***
      
        WAN (wan)                 -> em3        -> 192.168.2.197 (DHCP)
        LAN (lan)                 -> em2        -> 192.168.10.1
        WAN2 (opt1)               -> em4        -> NONE (DHCP)
        WLAN (opt2)               -> ath0_wlan0 -> NONE
      
      

      I set my ip address manually on my machine and I am still able to get to 192.168.10.1. Checking the system logs, I get the following message:

      php: /system_gateways_edit.php: The command '/usr/local/sbin/dhcpd -user dhcpd -group _dhcp -chroot /var/dhcpd -cf /var/dhcpd/etc/dhcpd.conf em2 ath0_wlan0' returned exit code '1', the output was 'Internet Systems Consortium DHCP Server V3.0.7 Copyright 2004-2008 Internet Systems Consortium. All rights reserved. For info, please visit http://www.isc.org/sw/dhcp/ /var/dhcpd/etc/dhcpd.conf line 23: expecting numeric value. subnet netmask ^ Configuration file errors encountered -- exiting'
      

      Inspecting the dhcpd.conf file, I see the problem:

      option domain-name "home";
      option ldap-server code 95 = text;
      option domain-search-list code 119 = text;
      
      default-lease-time 7200;
      max-lease-time 86400;
      log-facility local7;
      ddns-update-style none;
      one-lease-per-client true;
      deny duplicates;
      ping-check true;
      authoritative;
      authoritative;
      subnet 192.168.10.0 netmask 255.255.255.0 {
      	pool {
      		range 192.168.10.100 192.168.10.199;
      	}
      	option routers 192.168.10.1;
      	option domain-name-servers 192.168.10.1;
      
      }
      subnet  netmask 0.0.0.0 {
      	pool {
      		range 192.168.20.100 192.168.20.199;
      	}
      	option routers ;
      	option domain-name-servers ;
      
      }
      ```[config-lanner_pfsense.home-20100608092430.txt](/public/_imported_attachments_/1/config-lanner_pfsense.home-20100608092430.txt)
      1 Reply Last reply Reply Quote 0
      • jimpJ
        jimp Rebel Alliance Developer Netgate
        last edited by

        Do you see any errors on the console at boot-time about missing functions?

        Remember: Upvote with the 👍 button for any user/post you find to be helpful, informative, or deserving of recognition!

        Need help fast? Netgate Global Support!

        Do not Chat/PM for help!

        1 Reply Last reply Reply Quote 0
        • G
          GoldServe
          last edited by

          No, I didn't see any missing function error messages…

          1 Reply Last reply Reply Quote 0
          • jimpJ
            jimp Rebel Alliance Developer Netgate
            last edited by

            It might be because you have DHCP enabled on your wireless interface, but it has no IP address. Not sure how that might have happened.

            I see it in the config, but it is not on the console output.

            Remember: Upvote with the 👍 button for any user/post you find to be helpful, informative, or deserving of recognition!

            Need help fast? Netgate Global Support!

            Do not Chat/PM for help!

            1 Reply Last reply Reply Quote 0
            • G
              GoldServe
              last edited by

              Yeah, that's what I noticed as well but in interface statistics screen, all the information about the interface is correct.

              Status  	 up
              MAC address 	00:0b:6b:09:xx:xx
              IP address 	192.168.20.1  
              Subnet mask 	255.255.255.0 
              
              
              1 Reply Last reply Reply Quote 0
              • jimpJ
                jimp Rebel Alliance Developer Netgate
                last edited by

                It appears to be correct in some areas but not in others, which may indicate that certain areas aren't getting the right interface information. This is known to happen if you don't have a proper pfSense.so PHP module, hence my questioning the boot errors.

                You may just need to upgrade to a new snapshot (from today or last night) and see if it's any better.

                Remember: Upvote with the 👍 button for any user/post you find to be helpful, informative, or deserving of recognition!

                Need help fast? Netgate Global Support!

                Do not Chat/PM for help!

                1 Reply Last reply Reply Quote 0
                • G
                  GoldServe
                  last edited by

                  I think the problem is with timing or the order of which the ip address is assigned to OPT2, wireless interface. On a fresh boot, i see the following error message.

                  Jun 8 18:43:22 	miniupnpd[63897]: HTTP listening on port 2189
                  Jun 8 18:43:22 	php: miniupnpd: Starting service on interface: lan
                  Jun 8 18:43:22 	php: miniupnpd: Interface opt2 has no ip address, ignoring
                  Jun 8 18:43:22 	php: : The command '/usr/local/sbin/dhcpd -user dhcpd -group _dhcp -chroot /var/dhcpd -cf /var/dhcpd/etc/dhcpd.conf em2 ath0_wlan0' returned exit code '1', the output was 'Internet Systems Consortium DHCP Server V3.0.7 Copyright 2004-2008 Internet Systems Consortium. All rights reserved. For info, please visit http://www.isc.org/sw/dhcp/ /var/dhcpd/etc/dhcpd.conf line 23: expecting numeric value. subnet netmask ^ Configuration file errors encountered -- exiting'
                  
                  

                  Notice miniupnpd also thinks there is no ip address for opt2 but later on, it gets an address.

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