On Mar 7, 4:19 am, Mike Christie <[email protected]> wrote: > On 03/05/2012 10:31 PM, [email protected] wrote: > > > Hi, > > > The RFC4171 says that iSNS unicast messages SHOULD NOT include the > > authentication block but rather should rely on IPsec security > > mechanisms. > > > Why the open iSNS code sends authentication block (with Security > > enabled) along with all unicast messages like registration, query > > etc ? > > I do not know why the original author decided to do that. The rfc does > not say MUST NOT, so maybe the original author decided they preferred to > do it for some reason. There does not seem to be any clues in the code > or commit logs. > > Is this causing a issue/bug with some other servers/clients?
Problem is that if I enable security at the server, then all targets/ initiators should also send authentication block in every PDU. The targets/initiators that I am using do not support authentication, so they fail to communicate with open iSNS server. -- You received this message because you are subscribed to the Google Groups "open-iscsi" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/open-iscsi?hl=en.
