NTT's 2nd
IPSEC Interoperability Test Results
(Automatic Key Sequencing)

The results which are listed below are not necessarily supported by other parties. Also, there were no specified requirements which had to be met to allow the interoperable testing as long as the devices could communicate properly. Finally, these test results are not to be a used as a basis for setting up networks built around them either. Thus any networks which are built around the interoperable system results posted below must be the sole responsibility of the network installer. Also, please note that at the time of testing, there were numerous modifications and additions being added at a very quick pace and thus, when reviewing the results, ensure that you compare the "Current Version at Time of Testing" information with the latest shipping version as later versions may offer different results.

Interoperability Result Matrix
(Click on the Product Link for details)

Rcv Snd	Raptor Firewall	Gauntlet	VPNet VSU1010	Firewall-1	PERMIT	Sidewinder	Secured A2DIS	RAVLIN	SafeNet	YAMAHA RT140e	cIPro
Raptor Firewall		m	A	A	A	m	m	A	A	X	A
Gauntlet	m		m	m	X	m	m	X	X	m	X
VSU1010	X	m		A	A	m	-	A	X	m	X
Firewall-1	A	m	A		A	X	-	X	A	X	A
PERMIT	A	X	A	X		A	-	A	A	X	X
Sidewinder	m	m	m	X	A		m	A	X	X	X
A2DIS	m	m	-	-	-	m		-	-	-	-
RAVLIN	A	X	A	X	A	A	-		X	X	X
SafeNet	A	X	X	A	A	X	-	A		-	A
RT140e	X	m	m	X	X	X	-	X	-		-
cIPro	A	X	X	A	A	X	-	A	A	-

[Reading the Matrix]

Depending on the direction of communications, the automatic key exchange sequence didn't execute properly for some machines, so we've divided the matrix into "Initiator" [Snd] and "Responder" [Rcv] to be able to tell which direction worked and which didn't.
To view the "Initiator" [Snd] results, refer to the rows.
To view the "Responder" [Rcv] results, refer to the columns.

To view Version and Revison differences, please see the List of Products Tested for details.

[LEGEND: Marks used in the Table are as follows:]

A: Automatic Key Sequence Exchange is possible.
m: Only Manual Key Exchange is possible.
X: Key Exchanges were not possible.
-: Not tested.

Products Not Tested

[Background]

Products not tested are listed as follows.

ShivaVPN Gateway The VPN redundancy feature built into their product did not allow for compatibility with other vendor's products. The current version, as it is, does not have an interoperable match.
This benefits of this feature are such that if 1 of your VPN buses goes bad, it automatically uses the backup VPN bus.

3Com NetBuilder 3Com's proprietary IPsec feature "PPTP" does not allow it to communicate with other vendors' products.
This "PPTP" feature allows for non-IP protocols to be used as well, or basically a multi-protocol solution.
At the moment, this product only supports manual key exchange, but the next version will support automatic key exchange.

FortKnox The FortKnox's IKE header has a minor version difference in that it is set to use [1] where as all other products to be tested use the IKE header set to [0] . Due to this difference, an error [Invalid Minor Version] was given off and thus key exchanges were not possible.
At present, All-in-one type (WWWAFTPAMailAFirewallABandwidth control) products are IPsec compliant. They also have client software as well. All settings are done through a Web browser.

Return

ShivaVPN Gateway	The VPN redundancy feature built into their product did not allow for compatibility with other vendor's products. The current version, as it is, does not have an interoperable match. This benefits of this feature are such that if 1 of your VPN buses goes bad, it automatically uses the backup VPN bus.
3Com NetBuilder	3Com's proprietary IPsec feature "PPTP" does not allow it to communicate with other vendors' products. This "PPTP" feature allows for non-IP protocols to be used as well, or basically a multi-protocol solution. At the moment, this product only supports manual key exchange, but the next version will support automatic key exchange.
FortKnox	The FortKnox's IKE header has a minor version difference in that it is set to use [1] where as all other products to be tested use the IKE header set to [0] . Due to this difference, an error [Invalid Minor Version] was given off and thus key exchanges were not possible. At present, All-in-one type (WWWAFTPAMailAFirewallABandwidth control) products are IPsec compliant. They also have client software as well. All settings are done through a Web browser.

NTT's 2nd IPSEC Interoperability Test Results (Automatic Key Sequencing)

NTT's 2nd
IPSEC Interoperability Test Results
(Automatic Key Sequencing)