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

    Can't get DHCP from ISP

    Scheduled Pinned Locked Moved Virtualization
    3 Posts 3 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.
    • R
      rbadal
      last edited by

      Dear users,

      I have a problem with my pfSense box. I am using this release; pfSense-LiveCD-2.2.4-RELEASE-amd64-20150725-1957.
      My setup is as follow; ISP Modem –> Hypervisor (ProxMox) --> VM with pfsense (NIC's are bridged and im using pfsense transparant)
      Every time when i setup my WAN interace in pfsense to DHCP i cannot get an IP from my ISP. If i configure my hypervisor to DHCP i can get an IP. Every other device works OK with the DHCP from my ISP, only pfSense is giving me troubles. If have setup the firewall to allow DHCP. When i check the logging i get this:

      Oct 24 18:57:22 dhclient[81286]: exiting.
      Oct 24 18:57:22 dhclient[81286]: connection closed
      Oct 24 18:57:20 dhclient: FAIL
      Oct 24 18:57:20 dhclient[79663]: No working leases in persistent database - sleeping.
      Oct 24 18:57:20 dhclient[79663]: No DHCPOFFERS received.
      Oct 24 18:57:16 dhclient[79663]: DHCPDISCOVER on em0 to 255.255.255.255 port 67 interval 4
      Oct 24 18:57:02 dhclient[79663]: DHCPDISCOVER on em0 to 255.255.255.255 port 67 interval 14
      Oct 24 18:56:45 dhclient[79663]: DHCPDISCOVER on em0 to 255.255.255.255 port 67 interval 17
      Oct 24 18:56:32 dhclient[79663]: DHCPDISCOVER on em0 to 255.255.255.255 port 67 interval 13
      Oct 24 18:56:27 dhclient[79663]: DHCPDISCOVER on em0 to 255.255.255.255 port 67 interval 5
      Oct 24 18:56:23 dhclient[79663]: accepting packet with data after udp payload.
      Oct 24 18:56:23 dhclient[79663]: ip length 328 disagrees with bytes received 348.
      Oct 24 18:56:22 dhclient[79663]: DHCPDISCOVER on em0 to 255.255.255.255 port 67 interval 4
      Oct 24 18:56:20 dhclient[79663]: accepting packet with data after udp payload.
      Oct 24 18:56:20 dhclient[79663]: ip length 328 disagrees with bytes received 348.
      Oct 24 18:56:20 dhclient[79663]: DHCPDISCOVER on em0 to 255.255.255.255 port 67 interval 2
      Oct 24 18:56:19 dhclient[79663]: DHCPDISCOVER on em0 to 255.255.255.255 port 67 interval 1
      Oct 24 18:56:19 dhclient: PREINIT
      Oct 24 18:56:17 dhclient[74269]: exiting.
      Oct 24 18:56:17 dhclient[74269]: connection closed
      Oct 24 18:56:17 dhclient[72430]: em0 link state up -> down
      Oct 24 18:56:16 dhclient[72430]: DHCPDISCOVER on em0 to 255.255.255.255 port 67 interval 5
      Oct 24 18:56:14 dhclient[72430]: DHCPDISCOVER on em0 to 255.255.255.255 port 67 interval 2
      Oct 24 18:56:14 dhclient[72430]: DHCPDISCOVER on em0 to 255.255.255.255 port 67 interval 1
      Oct 24 18:56:14 dhclient: PREINIT
      Oct 24 18:56:09 dhclient[54255]: exiting.

      On my hypervisor i have not configured internet because i would like pfsense to request an IP from my ISP, not my hypervisor. Also, if i try to use the same IP configuration from my ISP as static on my WAN in pfsense, i still dont have access to internet. I hope you guys can help me!

      Thnx in advance!

      EDIT:
      This soms not to be an pfSense issue. If i try a Linux Live CD i still can't get an IP adres. Maybe an hypervisor problem? Will try Hyper-V to check if it's working on WIndows.

      1 Reply Last reply Reply Quote 0
      • A
        adamsuail
        last edited by

        i was able to get an ip from my isp after giving the VMs WAN interface the MAC address of the physical interface. i think they have some sort of mechanism to identify VMs MAC address and deny access.
        there is also an option in the VMs NIC card configuration that i think helped  "Replicate physical network connection state"

        1 Reply Last reply Reply Quote 0
        • K
          kferrero
          last edited by

          I had this issue with Comcrap. When I switched from a hardware firewall to my pfsense box on esxi I had to reboot my cable modem 2-3 times and spam the "dhcp renew" button in pfsense for it to grab an IP. I can't speak for other ISPs but it has something to do with Comcrap using sticky IPs that are tied to the MAC address of the device requesting a DHCP IP.

          I noticed that if I switch back to the hardware firewall, I revert back to an old "dynamic" IP, and if I switch back to pfsense I get the same new "dynamic" IP. I put dynamic in quotes because even though it's not considered static, I always get the same IP based on the firewall I'm using aka sticky IP

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