It seems that the issue is not with the driver, since same errors appear when using an emulated E1000 NIC.

@ermal: Which screen is this? Firewall > Rules > Lan > add new rule This is simple, all description area doing that problem.

I guess, I have a related issue. I have installed one of the 2.2 snapshots a couple of days ago. Now I wanted to update it to the latest one using the .tgz file. However, I got an error stating that "The uploaded image file is not for this platform.". Both the installed system and the update are amd64, so that shouldn't be the actual cause for error.

This is separate issue. Please give more details in another thread.

That's great Thanks.

It appears to be using this Intel 802.11AC (and Bluetooth) chipset: http://ark.intel.com/products/75439/intel-dual-band-wireless-ac-7260 I would say almost certainly won't work. Steve

Might be related to this: https://forum.pfsense.org/index.php?topic=74505.0

I can't see why there should be any issues at all, but I was going to migrate from using a dedicated computer into using Hyper-V on my Windows Server 2012 R2 installation anyways so I will just do a config backup and configure a new installation using Hyper-V and see how that goes.

The next time the builder wakes up to do a fresh run it should work. If not I'll check it out again later.

There was tracker code put into filter.inc that broke the rules. Seems that it is not supported by pf or the rule is malformed. These are the default rules. After removing the code, mine started working.

Open a bug report on redmine.pfsense.org and mention that, it should be fairly easy to fix on our side, those modules may just not be getting built/included in the images.

packages are still getting a lot of attention. what jimp said.

@maverick_slo: Hmmm I used i386 build. U used Gen1 or Gen2? I suppose Gen1. So far only used Hyper-V 2, not tried on Hyper-V 3 yet. That is the next test when things work a bit more….. Peter

Its a builder issue i fixed. The tracker is used to match properly log entries with expected rule. And yes its a pfSense only feature.