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

    Hyper-V integration installed with pfSense 2.0.1

    Scheduled Pinned Locked Moved Virtualization
    168 Posts 59 Posters 171.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.
    • A
      ArthurZz1
      last edited by

      Hello there,

      I'm also stuck with CARP on "INIT" with 2 pfsense vm (2.1 BETA) on Windows Server 2012. Activated mac spoofing for vNIC but not luck.

      I'll be following this thread in case you have any update on this problem.

      1 Reply Last reply Reply Quote 0
      • E
        elementalwindx
        last edited by

        Per installing  pfSense-LiveCD-2.1-DEVELOPMENT-amd64-20130516-0018.iso from Polly on my 2008R2 Hyper-V setup, I cannot get a DHCP ip for my WAN adapter at all.

        I've tried going into the Hyper-V Network settings and using external (with/without checkbox), internal, and private setup. and full stopped the vm between each change.

        I've shelled and did ifconfig de0 down etc. but it will not try to get an ip address.

        What am I doing wrong? How should the Hyper-V network settings be?

        I imagine it should be as such:

        Hyper-V Network settings:

        WAN - External not shared
        LAN - External shared/not shared doesnt matter since I have 4 adapters on this server

        Inside the VM settings area:
        2 Legacy adapters using the created hyper-v network adapter (Properly labeled Internet, and LAN)

        Now I tried using non-legacy adapters and pfsense detected and installed those with the same results as the legacy.

        Any help on what I am doing wrong? Thanks.

        edit

        I can connect the setup via this method: cable modem -> netgear router -> switch -> WAN port on server w/ pfsense in hyper-v

        and I can get a DHCP address on the WAN port.

        but if I connect it like such: cable modem -> WAN port on server w/ pfsense in hyper-v then I get the problem described above and get no DHCP address.

        The cable modem gives a straight public ip. Not an internal 192.* number.

        edit 2

        I think it has something to do with the way cable modems operate in the manner that the first thing they see is the first thing they try to hand out an address to. IE they see the physical nic mac address and give it the ip, then the virtual mac address comes along asking for the IP and the cable modem gives it the middle finger.

        Wonder how I can fix that. Perhaps clone the mac address of the physical adapter?

        edit 3

        Ok cloned the mac addresses, but make sure you check the box for "spoof address" under the vm settings, otherwise it won't work. :) Problem solved.

        I'll run this setup in a production environment over the weekend to see if it crashes and let you guys know.

        Thanks for the awesome iso!

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

          Hi all.
          My last updated ISO with a Hyper-V kernel

          http://goo.gl/evcFRk :: pfSense-LiveCD-2.1-DEVELOPMENT-amd64-HV-kernel-20130812-2157.iso

          1 Reply Last reply Reply Quote 0
          • E
            elementalwindx
            last edited by

            @PollyPy:

            Hi all.
            My last updated ISO with a Hyper-V kernel

            http://goo.gl/evcFRk :: pfSense-LiveCD-2.1-DEVELOPMENT-amd64-HV-kernel-20130812-2157.iso

            just in time. I was going to reinstall your iso tomorrow on a 2012 server :)) ill let you know how it goes. Is it possible to get pfsense to realize a wireless card is available?

            1 Reply Last reply Reply Quote 0
            • L
              Liceo
              last edited by

              Dear all

              After struggling with Performance problems on Hyper-V using the official builds, i tested this one and in rocks!

              Thanks to all involved!

              Liceo

              1 Reply Last reply Reply Quote 0
              • G
                gemmiu
                last edited by

                Do i still have to restart the WAN-Adapter after every reboot to receive a dhcp ip address or is this issue solved in the last version?

                1 Reply Last reply Reply Quote 0
                • L
                  Liceo
                  last edited by

                  @gemmiu:

                  Do i still have to restart the WAN-Adapter after every reboot to receive a dhcp ip address or is this issue solved in the last version?

                  I solved this problem after setting all the NIC to 100/full.

                  1 Reply Last reply Reply Quote 0
                  • E
                    elementalwindx
                    last edited by

                    @gemmiu:

                    Do i still have to restart the WAN-Adapter after every reboot to receive a dhcp ip address or is this issue solved in the last version?

                    The previous 2 builds I have not had that issue you are describing.

                    1 Reply Last reply Reply Quote 0
                    • G
                      Geralt
                      last edited by

                      Is there any way how to get Vlans on Guest(pfsense) working?

                      Thanks.

                      PS : nice job ;)

                      1 Reply Last reply Reply Quote 0
                      • T
                        TRIUMF
                        last edited by

                        You should add network adapters and configure vlans using Hyper-V, not pfsense itself.

                        1 Reply Last reply Reply Quote 0
                        • G
                          gemmiu
                          last edited by

                          I'm very new in freedsd and pfsense.

                          About the WAN problem, is there a way to check in a startup script, if the wan adapter has a dhcp ip address assigned? And if no, the wan adapter will be restartet and the dhclient will be run again?

                          Sorry for my bad english.

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

                            What exactly do you mean with "WAN problem"?
                            As i know, you shouln't need any start script since the integration driver….

                            What language do you speek usually?
                            You can send me a pm if its german  ;D

                            1 Reply Last reply Reply Quote 0
                            • L
                              Liceo
                              last edited by

                              @TRIUMF:

                              You should add network adapters and configure vlans using Hyper-V, not pfsense itself.

                              Sure, but then you are limited to the max of vNICs you can add.

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

                                @Liceo:

                                Sure, but then you are limited to the max of vNICs you can add.

                                You need more than 8 vNICs?

                                1 Reply Last reply Reply Quote 0
                                • L
                                  Liceo
                                  last edited by

                                  @hege:

                                  @Liceo:

                                  Sure, but then you are limited to the max of vNICs you can add.

                                  You need more than 8 vNICs?

                                  Consider using it in a productive environment, that can happen. It's not really an issue, if i would need more i may would deploy a 2nd pfsense.

                                  1 Reply Last reply Reply Quote 0
                                  • T
                                    TRIUMF
                                    last edited by

                                    @Liceo:

                                    @TRIUMF:

                                    You should add network adapters and configure vlans using Hyper-V, not pfsense itself.

                                    Sure, but then you are limited to the max of vNICs you can add.

                                    Sorry, never needed that many NICs so never had this issue :)

                                    Is there a chance we will see pfsense officially supported on Hyper-v in near future?

                                    1 Reply Last reply Reply Quote 0
                                    • L
                                      Liceo
                                      last edited by

                                      @PollyPy:

                                      Hi all.
                                      My last updated ISO with a Hyper-V kernel

                                      http://goo.gl/evcFRk :: pfSense-LiveCD-2.1-DEVELOPMENT-amd64-HV-kernel-20130812-2157.iso

                                      Hi PollyPy

                                      Which procedure you use to create your pfsense-Hyper-V builds? Do you have a step-by-step manual which is understandable for a Linux dummie like me?

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

                                        Hi PollyPy

                                        Which procedure you use to create your pfsense-Hyper-V builds? Do you have a step-by-step manual which is understandable for a Linux dummie like me?

                                        http://forum.pfsense.org/index.php/topic,56565.msg308223.html#msg308223

                                        1 Reply Last reply Reply Quote 0
                                        • D
                                          diegoriera
                                          last edited by

                                          Hi,

                                          Have you 2.1-RC1-HV.ISO?

                                          Thanks

                                          1 Reply Last reply Reply Quote 0
                                          • D
                                            diegoriera
                                            last edited by

                                            If I try to Update system or install Packages the system crash during download.

                                            Panic String: sleeping thread
                                              Dump Parity: 2933982801
                                              Bounds: 0
                                              Dump Status: good

                                            If I include kern.timecounter.hardware=TSC the clock was wrong

                                            I tested any versions with hyper-v patches.

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