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

    Pfsense meltdown

    Scheduled Pinned Locked Moved General pfSense Questions
    4 Posts 3 Posters 1.2k 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.
    • P
      Phatsta
      last edited by

      I installed a virtual pfsense on ESXi 4.1 on monday at a school. I have 3 VLAN's, and DHCP server activated on all of them. Other than adding allow rules for accessing internet, and a NAT rule to allow remote control by RDP, all is default. Everything worked fine for a day. On tuesday I lost the remote control. The firewall just would not let the traffic through, uh-uh.

      Today I lost the DHCP server on all networks. It looks fine, enabled and all, but it doesn't hand out IP's. Except once every ten tries, when it gives out an IP from the physical LAN (!!!!) no matter what VLAN I connect to.

      What the **** is happening?

      1 Reply Last reply Reply Quote 0
      • stephenw10S
        stephenw10 Netgate Administrator
        last edited by

        Check the system logs.
        These failures happened without any changes from yourself?

        Where are you handling the vlan traffic, in EXSi or directly in pfSense?

        Steve

        1 Reply Last reply Reply Quote 0
        • H
          heper
          last edited by

          what do the logs say ?
          are the vlans configured correctly ? dhcp leases from a different vlan sounds like a problem in the switch config

          also consider upgrading the esxi to 5.5 … it has improved support for freebsd 8.3 (see attached screenshot)

          exi_compatibility_freebsd.png
          exi_compatibility_freebsd.png_thumb

          1 Reply Last reply Reply Quote 0
          • P
            Phatsta
            last edited by

            Thanks for your quick replies guys!

            I actually found the problem. I couldn't see it at first, not until I logged in to one of the VM's and got the "shutdown alert log" or whatever it's called. In Windows when you boot up after dirty shutdown. This told me I've had a power failure, and looking a bit further I saw that the vlan settings on the vswitch in vmware was pretty much fu*ked up. I set it right and did a controlled reboot, and shalom.

            I'd say you were correct heper :)

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