Date: Tue, 03 Jan 2017 12:16:52 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-standards@FreeBSD.org Subject: [Bug 215727] [iscsi] target sends invalid NOP-out and drops connection if initiator doesn't reply Message-ID: <bug-215727-15@https.bugs.freebsd.org/bugzilla/>
next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D215727 Bug ID: 215727 Summary: [iscsi] target sends invalid NOP-out and drops connection if initiator doesn't reply Product: Base System Version: 11.0-RELEASE Hardware: Any OS: Any Status: New Severity: Affects Many People Priority: --- Component: standards Assignee: freebsd-standards@FreeBSD.org Reporter: nareg.sinenian@gmail.com Created attachment 178470 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=3D178470&action= =3Dedit Sample NOP-In sent by the FreeBSD target The target sends NOPs to the initiator and expects a reply. When it doesn't receive a reply, it drops the connection. The problem, however, is that standards-compliant initiator will not respond to the NOP sent by the target because it contains an invalid target transfer tag. See RFC7143 Sec. 10.19.1: If the target is sending a NOP-In as a ping (intending to receive a corresponding NOP-Out), this field is set to a valid value (not the reserved value 0xffffffff). The FreeBSD target sends a NOP-In expecting a reply, but the field is NOT s= et to a valid value. It is instead set to the reserved value of 0xffffffff. I have verified this by examining target traffic. A sample log is attached.= In this case, the target dropped the connection due to a "ping timeout" as observed on the console:=20 WARNING: 10.10.6.5 (iqn.2015-01.com.localhost): connection error; dropping connection WARNING: 10.10.6.5 (iqn.2015-01.com.localhost): no ping reply (NOP-Out) aft= er 5 seconds; dropping connection --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-215727-15>