>Number: 166508 >Category: kern >Synopsis: AES 256 encryption does not work with glxsb driver >Confidential: no >Severity: non-critical >Priority: low >Responsible: freebsd-bugs >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Fri Mar 30 03:00:26 UTC 2012 >Closed-Date: >Last-Modified: >Originator: Todd Blum >Release: 8.1 (pfSense 2.0.1) >Organization: >Environment: FreeBSD mbsnet-pf1.mbspchost.com 8.1-RELEASE-p6 FreeBSD 8.1-RELEASE-p6 #0: Mon Dec 12 18:59:41 EST 2011 root@FreeBSD_8.0_pfSense_2.0-snaps.pfsense.org:/usr/obj./usr/pfSensesrc/src/sys/pfSense_wrap.8.i386 i386
>Description: Enabling the glxsb driver on an Alix board (Netgate m1n1wall 2D13) running pfSense 2.0.1 (FreeBSD 8.1) prevents AES256 IPSec Phase2 connections from establishing: Mar 27 16:31:44 racoon: ERROR: pfkey ADD failed: Invalid argument Mar 27 16:31:44 racoon: ERROR: pfkey UPDATE failed: Invalid argument Mar 27 16:31:44 racoon: WARNING: attribute has been modified. Mar 27 16:31:44 racoon: [Name of Tunnel]: INFO: initiate new phase 2 negotiation: my.ip.add.ress500<=>rem.ote.ip.adr500 AES128 IPSec connections still work OK. I believe the remote side is Cisco IOS or ASA. I am running 2.0.1-RELEASE (i386). Other users have reported similar behavior: http://forum.pfsense.org/index.php?topic=47701.new Per pfSense dev team, the problem is upstream in the FreeBSD kernel: https://redmine.pfsense.org/issues/2324#change-8509 >How-To-Repeat: Load glxsb driver, then try to establish an AES256 IPSec tunnel. >Fix: >Release-Note: >Audit-Trail: >Unformatted: _______________________________________________ freebsd-bugs@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
