pfSense Support Subscription

Author Topic: 2.2 now Release Candidate  (Read 12934 times)

0 Members and 1 Guest are viewing this topic.

Offline hmh

  • Newbie
  • *
  • Posts: 24
  • Karma: +4/-0
    • View Profile
Re: 2.2 now Release Candidate
« Reply #15 on: December 12, 2014, 01:51:02 am »

Offline seqteq

  • Newbie
  • *
  • Posts: 11
  • Karma: +0/-0
    • View Profile
Re: 2.2 now Release Candidate
« Reply #16 on: December 14, 2014, 07:40:53 am »
Great work guys, looking good.

Gotta little problem with Open-VM-Tools package though,

pfSense 2.2-RC / Open-VM-Tools version 1280544_9, fresh installs on ESXi 5.1 and VMWare Workstation 11

Shutdown/restart does not work from VMWare esxi 5.1
Restart and Power on script does not work from VMWare Workstation 11

I searched and didn't find anything on my issue.

Also I didn't have this problem in the beta

The message from ESXi restart looks like this:
Call "VirtualMachine.RebootGuest" for object "pfSense 2.2 x64" on ESXi "x.x.x.x" failed.
-----------------------------------
The message from ESXi shutdown looks like:

Initiate guest OS shutdown:The request to Power off this virtual machine failed because the corresponding VMware Tools script did not run successfully. If you have configured a custom power-off script in this virtual machine, make sure that it contains no errors. Attempting the operation again will ignore the script failure. You can also submit a support request to report this issue.

See the error stack for details on the cause of this problem.
Time: 12/14/2014 6:59:01 AM
Target: pfSense 2.2 x64
ESXi: x.x.x.x
Error Stack
The request to Power off this virtual machine failed because the corresponding VMware Tools script did not run successfully. If you have configured a custom power-off script in this virtual machine, make sure that it contains no errors. Attempting the operation again will ignore the script failure. You can also submit a support request to report this issue.

additional dialogue:
Call "VirtualMachine.ShutdownGuest" for object "pfSense 2.2 x64" on ESXi "x.x.x.x" failed.
-----------------------------------
The message from VMWare Workstation 11 for power on looks like:
The VMware Tools power-on script did not run successfully in this virtual machine. If you have configured a custom power-on script in this virtual machine, make sure that it contains no errors. You can also submit a support request to report this issue.
-----------------------------------
The message from VMWare Workstation 11 for restart looks like:

The request to Reset this virtual machine failed because the corresponding VMware Tools script did not run successfully. If you have configured a custom reset script in this virtual machine, make sure that it contains no errors. Attempting the operation again will ignore the script failure. You can also submit a support request to report this issue.
« Last Edit: December 14, 2014, 07:48:33 am by seqteq »

Offline jzsjr

  • Jr. Member
  • **
  • Posts: 91
  • Karma: +0/-0
    • View Profile
Re: 2.2 now Release Candidate
« Reply #17 on: December 14, 2014, 01:39:09 pm »
Upgraded my APU with no issues.  Everything seems to be working fine except for my IPsec vpn connection.  I'm not sure what the issues other than it does not like the new IPsec.  I was hoping someone could look over the logs.  Thanks, Jim

Dec 14 19:32:04   ipsec_starter[47482]: 'con1' routed
Dec 14 19:32:04   ipsec_starter[47482]:
Dec 14 19:32:13   charon: 08[NET] received packet: from 216.235.xxx.194[500] to 71.204.15.119[500] (404 bytes)
Dec 14 19:32:13   charon: 08[ENC] parsed AGGRESSIVE request 0 [ SA KE No ID V V V V V V V V V ]
Dec 14 19:32:13   charon: 08[ENC] received unknown vendor ID: 40:4b:f4:39:52:2c:a3:f6
Dec 14 19:32:13   charon: 08[ENC] received unknown vendor ID: 5b:36:2b:c8:20:f6:00:07
Dec 14 19:32:13   charon: 08[IKE] <25> received NAT-T (RFC 3947) vendor ID
Dec 14 19:32:13   charon: 08[IKE] received NAT-T (RFC 3947) vendor ID
Dec 14 19:32:13   charon: 08[IKE] <25> received draft-ietf-ipsec-nat-t-ike-03 vendor ID
Dec 14 19:32:13   charon: 08[IKE] received draft-ietf-ipsec-nat-t-ike-03 vendor ID
Dec 14 19:32:13   charon: 08[IKE] <25> received draft-ietf-ipsec-nat-t-ike-02\n vendor ID
Dec 14 19:32:13   charon: 08[IKE] received draft-ietf-ipsec-nat-t-ike-02\n vendor ID
Dec 14 19:32:13   charon: 08[IKE] <25> received draft-ietf-ipsec-nat-t-ike-00 vendor ID
Dec 14 19:32:13   charon: 08[IKE] received draft-ietf-ipsec-nat-t-ike-00 vendor ID
Dec 14 19:32:13   charon: 08[ENC] received unknown vendor ID: da:8e:93:78:80:01:00:00
Dec 14 19:32:13   charon: 08[IKE] <25> received DPD vendor ID
Dec 14 19:32:13   charon: 08[IKE] received DPD vendor ID
Dec 14 19:32:13   charon: 08[IKE] <25> received XAuth vendor ID
Dec 14 19:32:13   charon: 08[IKE] received XAuth vendor ID
Dec 14 19:32:13   charon: 08[IKE] <25> 216.235.148.194 is initiating a Aggressive Mode IKE_SA
Dec 14 19:32:13   charon: 08[IKE] 216.235.148.194 is initiating a Aggressive Mode IKE_SA
Dec 14 19:32:13   charon: 08[CFG] looking for pre-shared key peer configs matching 71.204.15.119...216.235.148.194[0006B10ECFF0]
Dec 14 19:32:13   charon: 08[IKE] <25> no peer config found
Dec 14 19:32:13   charon: 08[IKE] no peer config found
Dec 14 19:32:13   charon: 08[ENC] generating INFORMATIONAL_V1 request 2478717834 [ N(AUTH_FAILED) ]
Dec 14 19:32:13   charon: 08[NET] sending packet: from 71.204.15.119[500] to 216.235.xxx.194[500] (56 bytes)
Dec 14 19:32:19   charon: 08[NET] received packet: from 216.235.xxx.194[500] to 71.204.15.119[500] (404 bytes)
Dec 14 19:32:19   charon: 08[ENC] parsed AGGRESSIVE request 0 [ SA KE No ID V V V V V V V V V ]
Dec 14 19:32:19   charon: 08[ENC] received unknown vendor ID: 40:4b:f4:39:52:2c:a3:f6
Dec 14 19:32:19   charon: 08[ENC] received unknown vendor ID: 5b:36:2b:c8:20:f6:00:07
Dec 14 19:32:19   charon: 08[IKE] <26> received NAT-T (RFC 3947) vendor ID
Dec 14 19:32:19   charon: 08[IKE] received NAT-T (RFC 3947) vendor ID
Dec 14 19:32:19   charon: 08[IKE] <26> received draft-ietf-ipsec-nat-t-ike-03 vendor ID
Dec 14 19:32:19   charon: 08[IKE] received draft-ietf-ipsec-nat-t-ike-03 vendor ID
Dec 14 19:32:19   charon: 08[IKE] <26> received draft-ietf-ipsec-nat-t-ike-02\n vendor ID
Dec 14 19:32:19   charon: 08[IKE] received draft-ietf-ipsec-nat-t-ike-02\n vendor ID
Dec 14 19:32:19   charon: 08[IKE] <26> received draft-ietf-ipsec-nat-t-ike-00 vendor ID
Dec 14 19:32:19   charon: 08[IKE] received draft-ietf-ipsec-nat-t-ike-00 vendor ID
Dec 14 19:32:19   charon: 08[ENC] received unknown vendor ID: da:8e:93:78:80:01:00:00
Dec 14 19:32:19   charon: 08[IKE] <26> received DPD vendor ID
Dec 14 19:32:19   charon: 08[IKE] received DPD vendor ID
Dec 14 19:32:19   charon: 08[IKE] <26> received XAuth vendor ID
Dec 14 19:32:19   charon: 08[IKE] received XAuth vendor ID
Dec 14 19:32:19   charon: 08[IKE] <26> 216.235.148.194 is initiating a Aggressive Mode IKE_SA
Dec 14 19:32:19   charon: 08[IKE] 216.235.xxx.194 is initiating a Aggressive Mode IKE_SA
Dec 14 19:32:19   charon: 08[CFG] looking for pre-shared key peer configs matching 71.204.15.119...216.235.xxx.194[0006B10ECFF0]
Dec 14 19:32:19   charon: 08[IKE] <26> no peer config found
Dec 14 19:32:19   charon: 08[IKE] no peer config found
Dec 14 19:32:19   charon: 08[ENC] generating INFORMATIONAL_V1 request 2450645352 [ N(AUTH_FAILED) ]
Dec 14 19:32:19   charon: 08[NET] sending packet: from 71.204.15.119[500] to 216.235.xxx.194[500] (56 bytes)

Offline rexki

  • Newbie
  • *
  • Posts: 20
  • Karma: +2/-0
  • Independent Consultant
    • View Profile
Re: 2.2 now Release Candidate
« Reply #18 on: December 14, 2014, 03:51:58 pm »
Coming from 2.1.5 x64  - SSH access URL update - 2.2 rc x64 full update x64 busted the following:

1.  Squid 3.4.9_1 pkg 0.1 - transparent not working , without Trans not working  - getting the libmd5.so.o not found - uninstalled squid after a reboot verification that status did not change any of these findings.
2.  the update Completely uninstalled squidGuard - left menus, services and watchdog. it was not me
3.  Service Watch dog is a mess - changes to un-activate watching line items don't work, only deleting the line items that were watched.
4.  Firewall log is empty and not reporting after turning a diagnostic external DNS server logging those on the general tab.
5.  ipGuard service will not start.

Not ready for prime time yet unless you want to be hours on site at a client with no filters in place s required by law at my school clients.  Ouch!!
pfSense 2.3.4-Release(amd64) - 31 watts Min d-power mode - 843-853 mbps across LANs -  i5-2400 3xGigE - Asus P8H61-M -All slotted Intel single NICS EM drivers -  shooting for 6 watts - to save $27/year in electricity.  In Hawaii $50 per year savings over 20 watt delta!!

Offline jimp

  • Administrator
  • Hero Member
  • *****
  • Posts: 21378
  • Karma: +1431/-26
    • View Profile
Re: 2.2 now Release Candidate
« Reply #19 on: December 15, 2014, 12:55:13 pm »
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.
Need help fast? Commercial Support!

Co-Author of pfSense: The Definitive Guide. - Check the Doc Wiki for FAQs.

Do not PM for help!