Hi, I've tried this morning. (built on Thu Nov 13 22:13:57 CST 2014 ) It works (for me) like a charm. Thank you very  much Regards

@Kofl: @falumas: This is another thing I found in the logs which most likely didn't cause my problem, but it seems like the Hyper-V components need a boost. A storage device in 'pfsense2.2' loaded but has a different version from the server.  Server version 6.0  Client version 2.0 (Virtual machine ID 6D28DD84-xxxx-xxxxx-B799-AECCE8AF44E6). The device will work, but this is an unsupported configuration. This means that technical support will not be provided until this problem is resolved. To fix this problem, upgrade the integration services. To upgrade, connect to the virtual machine and select Insert Integration Services Setup Disk from the Action menu. That message can be ignored: http://support.microsoft.com/kb/2737297 (its not only valid for Windows but also for *inux, *BSD) Are you shure about this? The MS kb article talks about the client having a higher version of the intergration services than the server. In the logs it's posted the other way around, so that would indicate there is room for inprovement !!

Can you please test if it works correctly with new snapshots? The cahnge has been merged.

Self inflicted wound. Set a flag to daemonize dnscrypt-proxy and it spanked something else. WAS:  'dnscrypt_proxy_flags="-a 127.0.0.1:40"' CHANGED TO:  'dnscrypt_proxy_flags="-a 127.0.0.1:40 -d"' SORRY!!!!!

Also works for me. Thank you

There seems to be some general issue in package reinstallation post-upgrade, it's one on my list to look at this week when time permits.

Thanks, pretty sure Ermal fixed that one earlier today.

confirmed, ticket open https://redmine.pfsense.org/issues/4001

@cmb: I don't see anything obvious that'd cause a boot delay along those lines. Something took a long time in the linkup of the NIC, and it's not clear what from that. Is it only reboots post-upgrade? With the Sunday snapshot I was able to replicate the same delay multiple times with no changes made before reboot. It seems to be a lot better with the current snapshot with sub 2 minute reboot time for the last 2 times I've tested.

most things don't parse netstat in that way anymore, but that circumstance is an issue. https://redmine.pfsense.org/issues/4000

Yeah it's just cosmetic, that's where it's trying to fill a v4 gateway, which doesn't exist on that interface. I have a couple systems showing that, will check into it when time permits. It doesn't hurt anything.

Think it does. Will need to check myself again. Been switching speed so much that I can't remember.

Yeah. https://redmine.pfsense.org/issues/3999

Yeah sounds like you've pretty much narrowed it down to a bad NIC in the Apple TV. Probably the only other thing you could try is a completely different switch. It's very rare these days, but it's possible the Apple TV and that switch just don't play nicely together for some reason. Unlikely that's the case though.

Sorry, I can't reproduce it anymore. Did many tests with all related packages, also did a snapshot upgrade between it, nothing went wrong.

"The colors for informational messages should be different." I know everyone is trying to get 2.2 out the door and it's been like this for a long time but I completely agree with this  - good UI says error and informational messages should definitely be different.

duh,  I just realized that my LAN and WAN ports are vlans on the same physical 1g port and that is not ideal when your WAN link is 1gbps.  I'll update when I move the lan port to it's own interface.

Didn't get to it last night, so I am on it right now. It's booting again, hence I can type this :-) I did make a screenshot, because it looks like it is set to console anyway? (Dont mind the #####'s. I was unsure what to press to make it stop booting…) [image: Capture.PNG] [image: Capture.PNG_thumb]

I just saw this today, first time I updated snapshots after installing OpenVPN.  Bare hardware, not stretched at all (Atom D2550).  Client connection to Private Internet Access was shown as down, yet it was up & running.  Kill by hand, restart by GUI, and things are fine.

Should be merged in now. Must have got the return mixed up with strpos when I wrote that test. Someday PHP needs to make such things more standardized. Or perhaps we'll have rewritten everything in another language by the time that happens. :p