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

    PfSense VM freeze

    Scheduled Pinned Locked Moved
    Virtualization
    6
    11
    6.3k
    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.
    • B
      biggsy
      last edited by

      Switch: The 8 network cables of the 2 Dell server (each have 4 NIC port) share one physical switch.
      No VLAN setup for the switch. Network cables connected the same physical switch with 2 routers for WAN connection.

      ???

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

        @biggsy:

        Switch: The 8 network cables of the 2 Dell server (each have 4 NIC port) share one physical switch.
        No VLAN setup for the switch. Network cables connected the same physical switch with 2 routers for WAN connection.

        ???

        There is no VLAN in entire network setup.

        1 Reply Last reply Reply Quote 0
        • M
          Mike-Bracknell
          last edited by

          I think what he's trying to point out is that with 1 switch and no VLAN you're negating the effect of the router in terms of security.

          Anyway, as regards the freeze issue this sounds like similar issues to my thread (albeit in different measures) and I traced those to me running 32bit pfSense in a 64bit FreeBSD container.  I would suggest downloading the 32bit pfSense version and trying to stick it in a 32bit FreeBSD container and see how the freeze goes (the backups are cross-portable).

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

            Well the proper way to say it is the entire network is in single VLAN.
            Have not setup multiple VLAN in this test stage. Light me out if the single VLAN setup is the culprit of the pfSense freeze.

            Currently checking on whether the current setup is causing a network loop though.
            Will try the 32bit later on, and see it still freeze or not.

            I am wondering is there anyone using version amd64 on ESXi 5.1 successfully and already in production?
            Any hint on solving this freezing issue is welcome  :)

            1 Reply Last reply Reply Quote 0
            • johnpozJ
              johnpoz LAYER 8 Global Moderator
              last edited by

              What would be the point of running amd64 version in a vm?

              I just don't see what it gets you?

              Im running 32bit on esxi 5.1 that was upgraded from 5.0, which was updated to u1 and have not had any issues with pfsense as vm at all.  Not one.  Runs and Runs and Runs -  I am running 2.1 for the record.  Even update pfsense to version 9 vm once upgraded to 5.1 without any issues at all.

              An intelligent man is sometimes forced to be drunk to spend time with his fools
              If you get confused: Listen to the Music Play
              Please don't Chat/PM me for help, unless mod related
              SG-4860 24.03 | Lab VMs 2.7.2, 24.03

              1 Reply Last reply Reply Quote 0
              • M
                matguy
                last edited by

                @johnpoz:

                What would be the point of running amd64 version in a vm?

                I just don't see what it gets you?

                Im running 32bit on esxi 5.1 that was upgraded from 5.0, which was updated to u1 and have not had any issues with pfsense as vm at all.  Not one.  Runs and Runs and Runs -  I am running 2.1 for the record.  Even update pfsense to version 9 vm once upgraded to 5.1 without any issues at all.

                True, in this case, he's only giving his VM 2GB of ram.  Unless you have an expectation that your pfSense would actually use more than 4GB of ram, (as far as I know) there's zero reason to use 64 bit pfSense.  32 bit is more mature and usually better supported.

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

                  Connect the WAN interfaces' NIC ports directly to the routers seem to solved the freeze issue. :)
                  Now the server been running 23 hours without issue.

                  Will increase RAM for the VM in future for packages thus opt for AMD64.

                  Been running a few 32bit pfSense on PIII bare metal in production though. :)

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

                    Server been running a month without issue.
                    For those who face pfSense freeze issue may want to check for any network loop or network traffic related issue as i found out most pfSense freeze issue was related to overloading network traffic or faulty/incorrectly setup NIC.

                    1 Reply Last reply Reply Quote 0
                    • S
                      Supermule Banned
                      last edited by

                      Maybe because you had both WAN and LAN in the same physical network on the switch??

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

                        @Supermule:

                        Maybe because you had both WAN and LAN in the same physical network on the switch??

                        yup, with heavy network traffic, it would took few hours to freeze the pfsense box.

                        1 Reply Last reply Reply Quote 0
                        • First post
                          Last post