From nobody Fri Oct 15 16:04:48 2021 X-Original-To: bugs@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id C86A21801FCF for ; Fri, 15 Oct 2021 16:04:48 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.nyi.freebsd.org (mxrelay.nyi.freebsd.org [IPv6:2610:1c1:1:606c::19:3]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "mxrelay.nyi.freebsd.org", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4HWB1D5BcTz3t6s for ; Fri, 15 Oct 2021 16:04:48 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2610:1c1:1:606c::50:1d]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mxrelay.nyi.freebsd.org (Postfix) with ESMTPS id 93EE61602 for ; Fri, 15 Oct 2021 16:04:48 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.5]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id 19FG4mmv023698 for ; Fri, 15 Oct 2021 16:04:48 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id 19FG4mlf023697 for bugs@FreeBSD.org; Fri, 15 Oct 2021 16:04:48 GMT (envelope-from bugzilla-noreply@freebsd.org) X-Authentication-Warning: kenobi.freebsd.org: www set sender to bugzilla-noreply@freebsd.org using -f From: bugzilla-noreply@freebsd.org To: bugs@FreeBSD.org Subject: [Bug 259152] [iscsi] ExpDataSN mismatch in SCSI Response (unable to connect or authenticate to OCI oracle iscsi block devices) Date: Fri, 15 Oct 2021 16:04:48 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: CURRENT X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: jhb@FreeBSD.org X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: bugs@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: cc Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated List-Id: Bug reports List-Archive: https://lists.freebsd.org/archives/freebsd-bugs List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-bugs@freebsd.org MIME-Version: 1.0 X-ThisMailContainsUnwantedMimeParts: N https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D259152 John Baldwin changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jhb@FreeBSD.org, | |mav@FreeBSD.org, | |trasz@FreeBSD.org --- Comment #5 from John Baldwin --- Please redo the packet capture with '-s 0'. The SCSI response PDUs are in = the same packet as the Data-In but can't be seen in WireShark since the captured packets are truncated. Given the small number of packets involved, using '= -s 0' should be ok without risk of dropping packets. Note that since there is a Data-In, the ExpDataSN field should be 1 in the = SCSI Response. It is a count of the Data-In PDUs sent in the reply to the origi= nal request prior to the SCSI Response PDU that closes it: https://datatracker.ietf.org/doc/html/rfc7143#section-11.4.8 The error messages in comment #4 suggest a completely garbled connection, e= .g. if there are extra bytes in the stream that cause the client to read PDU headers at the wrong offset. 'PDU 0x0' means that it thinks the opcode of = the PDU is 0 (NOP-Out). However, NOP-out PDUs are only sent by the initiator (client), not the target. I wonder if OCI is using AHS (which isn't generally supported in FreeBSD's iSCSI stack)? A full pcap might help. Oh, also, the LoginRespone shows 'iSCSIProtocolLevel=3DNot Understood" in t= he reply. That may be ok though as that just means we can't use features from= RFC 7144 I think (reading in RFC 7144 which defines version 2 where as 7143 is version 1). --=20 You are receiving this mail because: You are the assignee for the bug.=