Is there something in the 12.2 update that could break a VPN tunnels settings? Could the settings I'm using be out of date due to the patch?
I have an IPSEC tunnel that existed between Untangle and a PFSense firewall that was working great for months then my UT box updated last night and now the tunnel will not re-establish. The far end has not changed.
I used the directions on the Wiki for Untangle to PFSense IPSEC
I uninstalled and reinstalled the VPN module and recreated the tunnel, but no dice.
I did have an issue this morning where the Web UI for the Untangle box would not come up due to an Apache server error, I called support and rebooting the box fixed that problem. The Web UI works now.
I also see one odd part in the log when I start the service up, not actually having looked at it before, I'm not sure if that unable to load plugin features message is important or not.
Feb 17 13:05:38 untangle charon: 00[LIB] unable to load 5 plugin features (5 due to unmet dependencies)
Feb 17 13:05:38 untangle charon: 00[LIB] loaded plugins: charon test-vectors ldap pkcs11 aes rc2 sha1 sha2 md5 rdrand random nonce x509 revocation constraints pubkey pkcs1 pkcs7 pkcs8 pkcs12 pgp dnskey sshkey pem openssl gcrypt af-alg fips-prf gmp agent xcbc cmac hmac ctr ccm gcm curl attr kernel-netlink resolve socket-default farp stroke updown eap-identity eap-aka eap-md5 eap-gtc eap-mschapv2 eap-radius eap-tls eap-ttls eap-tnc xauth-generic xauth-eap xauth-pam tnc-tnccs dhcp lookip error-notify certexpire led addrblock unity
- NG Firewall
- Solutions by Industry
- Solutions by Issue