Ok, I have had a look at this capture file with WireShark. The connection does not get very far before the initiator pulls the plug... It's not even completing the target discovery.
Because of the use of 'continuation' packets by both hosts, it's difficult to decode. Here is a summary of what I'm seeing: Packet#10, Initiator->Target, Login Request (0x03) InitiatorName=iqn.1996-04.de.suse:01.f55caa69a4db InitiatorAlias=thing1 SessionType=Discovery HeaderDigest=None DataDigest=None DefaultTime2Wait=0 DefaultTime2Retain=0 IFMarker=No OFMarker=No ErrorRecoveryLevel=0 MaxRecvDataSegmentLength=8192 Packet#14, Target->Initiator, Login Response (0x23) HeaderDigest=None DataDigest=None DefaultTime2Wait=0 DefaultTime2Retain=0 IFMarker=No OFMarker=No ErrorRecoveryLevel=0 MaxRecvDataSegmentLength=8192 Packet#20, Initiator->Target, Text Request (0x04) SendTargets=All Packet#23, Target->Initiator, Text Response (0x24) TargetName=iqn.1986-03.com.sun:02:b0f5eaa2-28d5-4960-9210-b212a505a9f1 TargetAddress=192.168.0.3,1 TargetAddress=13.62.136.195,1 TargetAddress=0.0.0.0,1 TargetAddress=0.0.0.0,1 TargetAddress=13.62.136.195,1 Packet#26, Initiator->Target, TCP FIN,ACK I've never had a problem at the target discovery stage, so I cannot comment on what is going wrong. Latter today, I will compare the above to the behaviour of the Microsoft iScsi initiator. Thanks Nigel Smith This message posted from opensolaris.org _______________________________________________ storage-discuss mailing list [EMAIL PROTECTED] http://mail.opensolaris.org/mailman/listinfo/storage-discuss
