It would be best to split off issues into their own threads rather than piling on the announcement thread. Locking this for now. If you posted an issue here that hasn't already been solved, feel free to start a fresh thread here on the 2.2 board.
That package does not appear to be affected by the problem for which this thread is intended. If it is broken in some other way on 2.2, post a new thread on the 2.2 board and someone may be able to look at the package if there enough detail on how to reproduce the issue.
IKE: AES 256 encryption with SHA1 auth, 7800 SA lifetime, IKE DH group : Group 5, MODP 1536
IPSEC: AES 256 encryption with SHA1 auth, 3600 SA lifetime, IPsec PFS group: Group 5, MODP 1536
Line is very stable (DSL 30Mbit) and has not changed since the upgrade from pfsense 2.1.x to latest 2.2-RC.
Everything remained quite stable the last 2-3 days, with only an issue this afternoon, which disappeared as usual after a complete stop + start of the ipsec service.
Diagnostics->Backup/Restore, there should be a Clear Package Lock button. Press that to get rid of the "Packages are currently being reinstalled in the background".
Then go looking in logs to try and see what died that prevented a clean package install and unlock.
Note to other readers: Do not clear the package lock until it has been stuck "a long time" ™ - it might just be taking a while to download, unpack and install stuff (e.g. on nanoBSD with a slow CF card, on a slow link...)
Thx - worked out. This Tinc package just wont install. Is there any other ipsec/vpn which can greate full mesh vpn automatically?
You're not having the same issue. This thread was about a long-ago fixed issue with SSH host key generation in some circumstances. There are no known issues along these lines since, and any that do exist wouldn't be relevant to this thread. Please start a new thread with specifics of what you're seeing, as it's definitely completely unrelated to this thread.
Upgraded XenServer to 6.5 yesterday. PfSense doesn't route packets at more than 64kB/s …
I had to roll back an Hypervisor to use it again Now it works at 3~4Gb/s . I've tried with and without all the offload mecanisms. With or without to tools (which may be not fully optimized for 6.5)
