Latest PFsense for hyper-V?

rustydusty1717

Hi Rusty

My setup of the pfSense 2.2 64bit snapshot works fine so far.
See details in my previous post.

Cheers,
Thomas

Which revision? Any weird bugs or stability issues so far? Are you using legacy network drivers?

Thanks!

tisler

2.2-ALPHA (amd64)
built on Wed Aug 06 14:28:19 CDT 2014

No issues besides the clock going backwards in the first few minutes after reboot. Not experiencing any side effect of this so far.
I'm using the standard network adapters.

Cheers,
Thomas

rustydusty1717

What kind of throughput are you seeing on network side? I've got 50Mb X 5Mb and can saturate most of the 50Mb download with my current 2.0.3 but having some weird bugs with it and not consistent. I will switch everything to the 2.2 tonight and see how things progress.

rustydusty1717

Flipped everything over, power cycled modem, WAN side won't come up.

Will try turning the interfaces down and up like on older versions to see if that fixes it. Might have to try legacy network drivers as well. :-\

rustydusty1717

Apologies for all the posts.

Ended up still using legacy drivers as regular didn't work. Got it up and running and so far so good.

I would imagine the drivers didn't work due to my system. I posted the wrong specs of the host, but this is what it is:

Custom Desktop:
Motherboard: ASUS M5A99X EVO R2.0
CPU: AMD FX-8350
Memory: 24GB G.skill ripjaws
PSU: Seasonic 1000W

To get the host to connect I need to manually install the network drivers. Most likely reason why I still have to use legacy drivers.

lordstag

@rustydusty1717:

Apologies for all the posts.

Ended up still using legacy drivers as regular didn't work. Got it up and running and so far so good.

I would imagine the drivers didn't work due to my system. I posted the wrong specs of the host, but this is what it is:

Custom Desktop:
Motherboard: ASUS M5A99X EVO R2.0
CPU: AMD FX-8350
Memory: 24GB G.skill ripjaws
PSU: Seasonic 1000W

To get the host to connect I need to manually install the network drivers. Most likely reason why I still have to use legacy drivers.

I may be wrong here, but it's the Virtual Adapter driver that is in pfSense/FreeBSD. It should have almost nothing to do with the model of the physical adapter. That is up to Hyper-V to take care of.

As for 2.2 Hyper-V WAN performance I have a 100/10 line:

rustydusty1717

I tried with regular drivers, then rebuilt and used legacy and connected up instantly. Also tried the ifconfig up and down without luck.

tisler

You're Motherboard has a Realtek 8111F, 1 x Gigabit LAN Controller.
There are several posts that pfSense (actually its freeBSD) works best with Intel NICs. Thats why I ordered a Intel board.
The Realtek might be the cause for the network problem.

Cheers,
Thomas

rustydusty1717

I do have a seperate Dual Gigabit that I was going to add. It is however a rosewill network card if that helps at all.

reklaw

Hi guys and Tisler,

I was wondering how / where you download the 2.2 Alpha build (the one that Tisler mentioned previously)
I have Intel NIC's and wanted to try it out on my 2012 R2 Hyper-V.

Also does anyone know if Squid module will work with 2.2 currently?

Thanks guys,

Bruce

rustydusty1717

http://snapshots.pfsense.org/

tisler

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.

breakaway

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 up

To make it work. What's up with this?

tisler

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…

rustydusty1717

Turning the interfaces on and off didn't work for me. I had to continue to use legacy drivers

rustydusty1717

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)

breakaway

@tisler:

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.

reklaw

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.

rustydusty1717

So 2.1.5 is released?

Wonder about 2.2 more than anything, as is everyone I think.

Guest

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.