Odd DHCP / Static IP intermittent problem



  • Hi all,

    I've have a VM box running pfsense, configured with static IPs on both the internal and external interfaces.  After a reboot, and also at some random times the internal interface resets itself to a DHCP IP and I have to go into the shell and reset it back to it's static IP.  The web interface shows the internal interface as being set to static.

    Any ideas where I can look to modify this behavior?

    Many thanks,
    Matt



  • The pfsense reverted back to a DHCP IP address last night about 3am of it's own accord.

    I may have solved this temporarily by adding a reservation to my DHCP server for the pfsense box.  Just rebooted and it got the right address.  Not quite sure why it's trying to DHCP an address when it's all set to static…



  • @mkent:

    The pfsense reverted back to a DHCP IP address last night about 3am of it's own accord.

    The behaviour you describe is seriously unusual. :o  In your place my assumption would be that hardware is failing or that pfSense was corrupted during the original installation. If I was in your position and had a firewall behaving that way I would check the drive for problems, format the drive and reload it from scratch using install media that I'd verified the checksum on beforehand.

    If the problem persists after a full reinstall, I'd suspect either a driver incompatibility or a hardware issue which I would then start looking for in the runtime and boot logs for inconsistencies or errors.

    Here are the possible hardware causes that come to mind in troubleshooting order based on my personal experiences:
        a. Cabling and/or switch (use a different port and cable)
        b. LAN NIC (To verify, try swapping the LAN and WAN assignments using the console menu item #1 and see if the WAN then exhibits the same issue.)
        c. Hard disk (check the logs for errors, use Diagnostics: SMART Status: Perform Self-tests, badblocks*)
        d. RAM (replacing is the often the surest way to confirm)
        e. BIOS bug/corruption (reinstall/upgrade bios)
        f. Motherboard


Log in to reply