Latest PFsense for hyper-V?
-
I have squirt and snort and lightsquirt installed.
The custom options in squirt do not work though. At least its not showing my custom html page.
Lightsquirt is not working at all. No reports. -
Is anyone else having a problem where the network interfaces don't come up automatically after a boot? I am having such an issue – the WAN side (static IP to my internet provider) is working great -- but the LAN side (DHCP) doesn't come back automatically after a reboot. I have to either ssh in or connect via web, and initiate an
ifconfig de1 down ifconfig de1 upTo make it work. What's up with this?
-
If you recycle your LAN adapter is pfSense then fully working/can your browse the Internet)?
Without knowing more details about your installation its hard to give and advice… -
Turning the interfaces on and off didn't work for me. I had to continue to use legacy drivers
-
Almost 6 day uptime, no issues whatsoever besides having to use legacy.
Although this is my personal instance of pfsense and is not used for much other than port forwarding and such, I may just leave it even after 2.2 is offically released. This personal instance does nothing other than serve as a firewall, no dhcp/dns as that is done by the DC.
I am able to achieve full speeds of my biz cable connection with legacy nic (50Mb down X 5Mb upload)
-
If you recycle your LAN adapter is pfSense then fully working/can your browse the Internet)?
Without knowing more details about your installation its hard to give and advice…It's a very simple setup… The WAN side is a static IP interface with my ISP -- this works without requring reboot. But the LAN side runs DHCP and hands out addresses to my LAN hosts. After reboot, no LAN hosts can get an IP. I can log into the WAN interface from the internet, then I do the ifconfig up-down dance and kablam, everything works.
Perhaps like some issue with interfaces that have DHCP running?
Once it's up and running its fine though. Have had 100+ days of uptime with zero issue.
-
Thanks for the link rustydustry1717, will have a play on the weekend with 2.2 and see how it goes with the non-legacy adapters.
-
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