Hyper-V Synthetic Network Drivers ($600)



  • We wish to get the Hyper-V Linux Integration Services 2.1 synthetic network drivers to work correctly under Pfsense 2.0+ (FreeBSD).  To claim the bounty, you must get the drivers working and either get them into the SVN for Pfsense 2.0+ official builds, or provide a quick and easy method of installing them ourselves into future versions of Pfsense 2.

    I should also note that we will not award this bounty until we load and stability test the system to watch for any crashes and/or load issues due to the hacked driver.  We expect about 1-4 weeks of testing before we actually award the bounty after bounty fulfillment.



  • Linux is vastly different from FreeBSD and I don't believe MS provides anything there for FreeBSD, at least not that I've been able to find. If they did, that would be an achievable bounty. Porting something for Linux to FreeBSD is vastly more involved, possibly to the extent of nearly rewriting it all from scratch. That could easily be a few hundred hours of work.



  • @cmb:

    Linux is vastly different from FreeBSD and I don't believe MS provides anything there for FreeBSD, at least not that I've been able to find. If they did, that would be an achievable bounty. Porting something for Linux to FreeBSD is vastly more involved, possibly to the extent of nearly rewriting it all from scratch. That could easily be a few hundred hours of work.

    Possibly… although someone might come up with a really cool trick in how to make it work.  Alternatively if someone did slave away at it for a really long time to get it to work and got paid peanuts for it, it would still enhance the community at large as we would want to make the results publicly available.  Either way I'm sure that if someone is motivated it can get done.  I would also be willing to negotiate the price a bit.

    Either way, you are correct to say that it isn’t an easy thing one way or another.  Otherwise I would have taken care of it myself.  If it can be done though, not only would it make my life easier, but it would enhance Pfsense considerably.



  • Sure, I agree, just explaining it's extremely unlikely anyone would be willing to take you up on it because of what's involved.



  • Well, here's hoping!

    I did get a PM from someone.  I wish him luck.



  • @deltaend:

    Well, here's hoping!

    I did get a PM from someone.  I wish him luck.

    Yeah, me too!



  • Hello guys,

    Do you have any update with this topic ?
    Anyone with interest or working on this ?



  • I got contacted by one person who offered to do it, but they wanted to play some (not so funny) bidding game where they say the words "convince me" and I'm supposed to indefinetely increase the bounty until I get scammed out of a massive amount of money.

    In the realm of those people who take this seriously and understand that I'm not here to hire a team of professional developers for what this would probably normally cost, but rather help to make those who are already interested do some development by paying for pizza monies, no I haven't talked to anyone yet.

    I will post an update for the bounty though.  It is now $600.  If you can finish development before January 1st 2012, than the bounty is $1,000 for the first person to submit a working and stable driver.  As before, we will award this after 4 weeks of stability tests to ensure it works correctly.



  • Thank you for the quick reply.
    I will ask my company to help increase the bounty.



  • A quick question.  And this may be a dumb one, but I have to ask.

    On your Hyper-V VM are you using the regular NIC or Legacy NIC?

    Legacy NIC works with pfsense.



  • @jaredadams:

    A quick question.  And this may be a dumb one, but I have to ask.

    On your Hyper-V VM are you using the regular NIC or Legacy NIC?

    Legacy NIC works with pfsense.

    The legacy NIC is limited to 100Mbps.  That is the major reason why we wouldn't want to use it.



  • Im increasing the bounty with $900.

    Were having some issues even with the legacy one - they dont see any arp of the hosts sometimes.

    /M



  • If it goes up to 3000$ i would give this a shot.



  • Well, we are half there.  $600 + $900 = $1500.



  • I with I could contribute to the bounty, but alas, I'm only acting as a hobbyist right now and can't afford to contribute funds at this time.

    As to why it would be nice to have this

    • The synthetic network driver provides better performance overall (both bandwidth and turnaround and lower CPU usage)
    • Features like VMQ (VMDq) are exclusive to synthetic adapters (and legacy adapters can't connect to the same network, effectively requiring to have separate network cards for legacy and synthetic VMs - meaning that for simple networks, pfSense might be the sole non-Windows VM requiring 2 dedicated network cards, while everything else runs off a single team).
    • Simpler Hyper-V setup (ie, being able to team and use vlans with a simple Hyper-V switch setup).

    And some notes that might help someone more familiar with pfSense and FreeBSD get started:



  • Please dont lower the bounty - I raised it with 900 to 1500.



  • Dont lower the bounty on the thread - its 1500



  • @mikhug:

    Dont lower the bounty on the thread - its 1500

    I didn't, no one did.  Relax. ;)



  • deltaend,

    I hope you won't find this as intruding, but if you haven't found someone that can program the Hyper-V Synthetic NIC. I would be willing to match your offering for whomever able to build it.

    We are having some strange problems with the Legacy NIC using FreeBSD on our Hyper-V nodes and would like to be able to use the Synthetic NIC.



  • Sounds great!

    Bounty is now $2100



  • Mikhug, please sound off so I can confirm that you are still interested in adding $900 to our total.  We have a programmer who might be interested in the project.



  • Deltaend & Mikehug

    Can you please shoot me an email to timt at sharktech.net so we can co-ordinate our efforts? I've had someone reach out to me as well probably the same individual but would be better if we all handle this together so we can set the standards of what we are looking for.



  • this would be so awesome.  i hope it gets made.



  • In an effort to organize this so that it is more official, I applied to kickstarter for a project on this.  Hopefully by the end of this week it gets approved and everyone can contribute.  I will post the link here when it gets approved.

    Hopefully we can raise more money than we need so we can pay for additional support for Hyper-V such as i386 support, TimeSync, Storage drivers, etc…





  • Per the link you specified, it will initially support FreeBSD 8.2 and 8.3 sometime early summer.

    Per http://doc.pfsense.org/index.php/PfSense_and_FreeBSD_Versions, 2.0.1 is based on 8.1. So this would initially only help the upcoming pfSense 2.1 (with IPv6 support), which is based on 8.3, and assuming that these drivers make it into the 2.1 release (the bounty could be put towards motivating programmers to include the necessary support along with 2.1 or shortly after or as an installable package).



  • Well, if this is the case, no need for my KickStarter project… also no need to move ahead with getting something coded until we find out if the drivers will be fully compatible or not.  For the moment, I think we could consider this bounty suspended until such a time as we can evaluate pfSense with the new driver pack.



  • Definitely glad to see Microsoft, NetApp and Citrix stepping up on this. Once they make that available, we'll need to look at incorporating it and keeping hyper-v a first class citizen. We'll need the funding at that point to get a server to run hyper-v long term (if someone would like to contribute something, donations welcome), and to put developer time towards integrating the patches, testing, etc. Virtually all development comes from people on our payroll and we have to have some way to meet that payroll. Once we get to that point, I'll follow up on this thread to see what we can put together.


Locked