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

    DHCP on WAN interface not automatically starting

    Scheduled Pinned Locked Moved DHCP and DNS
    4 Posts 3 Posters 758 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.
    • M
      mannins79
      last edited by

      Hi guys,
      I have checked the topic and it's not new; there are lots of posts but I couldn't find the ultimate solution!!

      I have a problem with my pfSense (2.1.5) box . The firewall (Soekris) worked fine for a year and only recently showed this problem. I have also tried 10 other devices (same model) but the problem still there so, it's not HW problem.

      Basically the WAN interface loses the IP address (dynamically assigned) every time I disconnect the cable from the WAN port or restart the firewall.
      I have to manually go to Status-Interfaces and restart (or renew) the DHCP on the WAN interface.

      Any help guys?
      Thanks in advance

      1 Reply Last reply Reply Quote 0
      • F
        foresthus
        last edited by

        Hi there,

        I have got the sam problem 4 now 1-2 Weeks losing the wan (dhcp) ip address. Is there anybody to solve the problem.

        I changed the SSD, changed the WAN-Port, changed the kabel, changed the routerport (has got 4 ports), but with no satisfing solution. First I thought it might be the hardware, but that can´t be.

        Hope there will be a fix soon.  :'(

        I am using the 64Bit pfsense-software.

        1 Reply Last reply Reply Quote 0
        • C
          cmb
          last edited by

          Upgrade to 2.2, if that doesn't fix it, post your system log from after the NIC regains link.

          1 Reply Last reply Reply Quote 0
          • F
            foresthus
            last edited by

            @cmb:

            Upgrade to 2.2, if that doesn't fix it, post your system log from after the NIC regains link.

            Hi,
            I upgraded to 2.2.1 and you where right. Everything is better, but now there is a problem with squid3 and squidguard for squid3. That does not function. You can´t start both services working in 2.2.1. Even going back to squid2 and squidguard for squid2 on 2.2.1 is buggy.

            Hope to see a bugfix soon.

            Therefor thnx for your help.

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