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

    Hyper-V WAN down issue

    Scheduled Pinned Locked Moved Virtualization
    7 Posts 4 Posters 2.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.
    • N
      nh5
      last edited by

      Hi,

      I've been having an issue for a long time now with Hyper-V 2012R2 and pfSense, the WAN randomly dies in the middle of the night what's interesting is it has happened at exactly 2:16am 2x this past week. Usually, I either reboot it or I've learned a simple ifconfig hn0 down    ifconfig hn0 up usually gets it going again.

      I've been playing with the settings here: https://doc.pfsense.org/index.php/Tuning_and_Troubleshooting_Network_Cards to no avail as of yet. I set the kern.ipc.nmbclusters to 1000000 two nights back as a test after reading up about mbuf issues. During the condition a ping from the shell returns "no buffer space available" (or something close to that phrase)

      But at the same time I'm not 100% sure if what I'm touching plays a role here. I've also been playing with disabling certain integration tools including the time synchronization and it hasn't changed the condition.

      I've been unable to find anything useful in the logs. I first had this happen back on 2.2.1 a few months back and it has become increasingly more frequent as in every day/other day at this point. Where can I begin?

      Background info

      pfsense 2.2.4
      3 interfaces attached
      7 VLAN interfaces attached to one of those virtual interfaces
      Using Synthetic network adapters (aka non-legacy adapters)
      Provided 2x cores of cpu
      2048MB of ram

      Where to begin?

      1 Reply Last reply Reply Quote 0
      • cwagzC
        cwagz
        last edited by

        I think I had a similar problem.  The setting change suggested here fixed it for me.

        https://forum.pfsense.org/index.php?topic=96602.msg537663#msg537663

        Netgate 6100 MAX

        1 Reply Last reply Reply Quote 0
        • N
          nh5
          last edited by

          Saw that thread, I'm not dealing with DHCP on the WAN so it rules that out. However, I also tried disabling and enabling time sync on the VM with no change in condition. At this time it happens about every 36-48 hours. I've pretty much come to the conclusion that nothing is getting logged regarding the cause of the issue. Looking into running pfSense on bare metal again soon.

          1 Reply Last reply Reply Quote 0
          • 7
            753951
            last edited by

            I have similar issue when OpenVPN server is enabled. When I disable it, everything runs fine for weeks on. Didn't have time to trace it yet, but just like in your case, nothing in logs looks suspicious.

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

              So let me ask you are you running windows server 2012R2 with nothing in front of the box to protect it?

              
              (WWW)
                   |
                    -----------[WIN2012-NIC]-------{VM-PFSENSE}--------[VSWITCH]------[WIN2012-NIC]------[OTHER NETWORK]
                                                                        |
                                                                        |
                                                                          ------------------{OTHER-VMS}
              
              

              or well something like that? …. I ask do to I was thing about running something like this but I was thinking that wins firewall sucks but lol and it would not work out so well.

              IF need be not to hijack you post or anything shoot me a PM

              We all start same where

              1 Reply Last reply Reply Quote 0
              • 7
                753951
                last edited by

                Yes and no. NIC that's connected to WWW is directly passed through (SR-IOV) to pfsense VM. Windows OS does not see that NIC itself. When pfsense is shut down, host OS does not have access to WWW.

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

                  Sweet and yeah I was thinking it would work like that but never tested it like that, however I will be setting up a test box today and ill see if I get the same issue.

                  Btw thanks for the info and a momentary of hijacking your thread

                  We all start same where

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