Latest PFsense for hyper-V?
-
So 2.1.5 is released?
Wonder about 2.2 more than anything, as is everyone I think.
-
I, for one, am hoping to get 2.2 to BETA soon. Honestly, the only major things that are currently broken are captive portal and AES-GCM IPsec (which is new).
2.2 is the strategy for Hyper-V support.
-
Not to drag up on a old topic but:
we got PFsense 100% working on Xen and Hyper-v
with all hyper-v drivers, fully working Carp, multi-subnetting, etc.We notified Jim this week and awaiting his reply on arrangements to publish this as a PFSense build.
Regards,
Marco -
Not to drag up on a old topic but:
we got PFsense 100% working on Xen and Hyper-v
with all hyper-v drivers, fully working Carp, multi-subnetting, etc.We notified Jim this week and awaiting his reply on arrangements to publish this as a PFSense build.
Regards,
MarcoHere's what you didn't do.
You didn't send any code.
You didn't offer to send any code.You just said you had it working, and want to publish it.
Only ESF distributes pfSense.
-
Just wanted to post an update. On sunday I rebuilt my firewall again with the latest snapshot as of sunday. Didn't use legacy again to start and this time it worked perfectly.
Also, I'm noticing a huge decrease in CPU load over the legacy drivers, as well as full speed of my connection (biz cable 50x5)
-
Hi
I have a 2.2 (latest) installation on Hyper-V 2012 R2 and all works fine, but I still see the synthetic network adaptors as Degraded (integration services upgrade required).
I thought Integration Services were included in FreeBSD 10, do I need to install them separately or have I done something wrong?Many thanks
Bill
-
You shouldn't require to use legacy drivers which was my problem. After switching from legacy I saw huge CPU usage drop increased performance
-
This matches my (brief) experience.
-
Which part does?
-
not using the "Legacy" drivers.
-
Have issues getting it to run without the legacy drivers?
I had to do the install of the snapshots 3 times to get it to work. Haven't bothered updating to the latest snapshot in the worry it won't work anymore.
Running for weeks without a hiccup.
-
FWIW I've had 2.2 running on Hyper-V 2012 R2 for the past week and a half at home with nary a hiccup. Works beautifully. No perceptible CPU usage even under full load at night with everyone watching Netflix or gaming. Mix of Realtek and Intel NICs. Granted host is a 3770k, but still, I don't think I've seen CPU usage > 10%.
-
FWIW I've had 2.2 running on Hyper-V 2012 R2 for the past week and a half at home with nary a hiccup. Works beautifully. No perceptible CPU usage even under full load at night with everyone watching Netflix or gaming. Mix of Realtek and Intel NICs. Granted host is a 3770k, but still, I don't think I've seen CPU usage > 10%.
I concur with all of this. Huge decrease in CPU usage since switching from the legacy drivers. Performance gains are significant
-
Just to add another me too post, I just upgraded from the 2.1 based install, my host is still 2008 R2 and was running leagcy adapters (obviously). Having just got 100Mb fibre installed I was finding the VM could only actually do about 90Mb because of the legacy adapters and their "limit" of 100Mb.
Switched over to 2.2 by doing a clean install and importing the config and then just disconnected the old VM and connected the new and away everything went. I now get a solid 100Mb down :)
-
I concur with all of this. Huge decrease in CPU usage since switching from the legacy drivers. Performance gains are significant
An update - I ditched the realtek NICs and threw in a couple Intels, now the CPU usage is nothing - literally. Rock solid wireline performance and I never see a load on it even with two VPN tunnels and kids hammering Netflix :).
Hypervisor is Hyper-V 2012R2 on Server 2012 R2. I'm not necessarily a fan of the Hypervisor but pfSense is rock solid on it. I've got nothing but praise at this point for the setup.
-
Horray for compatibility in hyper-v!
-
Same as here. Works good.
-
I've been using pfSense in hyper-v 2012 r2 for over 6 months.
The 'degraded' status can be more or less ignored, it just means it isn't reading the data about it from the OS, doesn't mean performance is actually degraded.
Performance is awesome overall, I'm going to be setting it up as my primary router for Google Fiber once I get that installed. I'll be trying to see if I can set it up with CARP as well.
The only real issue I run into occasionally is with traffic actually flowing through the WAN after a reboot\update. I often need to power off the VM entirely and then power it back on for my interfaces to work again.
-
I'll be trying to see if I can set it up with CARP as well.
edit: scratch that, CARP now works with Hyper-V, see my later post in this thread.
The only real issue I run into occasionally is with traffic actually flowing through the WAN after a reboot\update. I often need to power off the VM entirely and then power it back on for my interfaces to work again.
I'm guessing that's due to a timing issue we've seen on some reboots on our own systems and some others'. The clock runs backwards and/or is otherwise messed up in that circumstance but only during boot and maybe a couple minutes after. I haven't had a chance to dig too far into that one, on our systems it doesn't seem to have any negative impact beyond log noise from the "runtime went backwards". I've heard from at least one other person who needs to do the same power off/on at times after that timing issue occurs. I'll be looking at that further post-2.2 release as well.
-
I've heard from at least one other person who needs to do the same power off/on at times after that timing issue occurs. I'll be looking at that further post-2.2 release as well.
Ah, yes I do regularly get the runtime \ clock went backwards message. I figure it's due to the way that cpu cycles are handed out to each VM and how the VM itself keeps time or possibly also due to the VM Host overriding the VM time. I don't usually see issues associated with it, though.
To be honest I haven't fully validated that I'm still getting the interface issue in the latest releases. I got into the habit of doing a full shutdown & startup after each update, so I'll have to try it again normally next time I update to see if the issue recurs.