On Wed, 2010-02-17 at 14:13 +0900, FUJITA Tomonori wrote: > Seems that stgt@xxxxxxxxxxxxxxx dropped this mail due to attachment. > > On Tue, 16 Feb 2010 10:47:11 -0800 > Chandra Seetharaman <sekharan@xxxxxxxxxx> wrote: > > > On Tue, 2010-02-16 at 10:38 +0900, FUJITA Tomonori wrote: > > > Hey, > > > > > > On Mon, 15 Feb 2010 11:46:51 -0800 > > > Chandra Seetharaman <sekharan@xxxxxxxxxx> wrote: > > > > > > > I just started testing some of the features of stgt. > > > > > > > > While trying stgt, realized that stgt provides the option of "CHAP" or > > > > "None" to the initiator. open-iscsi SW initiator chooses the lower > > > > "None", thereby it ends up not using the CHAP that I specified for the > > > > target in stgt. > > > > > > > > How do I tell stgt to _not_ provide "None" as an option ? IOW, makes > > > > sure CHAP _is_ used by the initiator ? > > > > > > Are you taking about a discovery or normal session? > > > > Discovery session. > > Ah, stgt doesn't support Discovery session authentication (like IET). Oh I see... But, when I disabled discovery authentication in open-iscsi and try to connect to my stgt targets, it connect, but I do not see any CHAP protocol exchanges (in the log of open-iscsi), that I see with Netapp target. OTOH, when I change the password (at the open-scsi end) to be different (than what was defined at tgtd target) it fails. Which makes me think that the password verification does happen. My question is why am I not seeing CHAP_A, CHAP_A/CHAP_/I/CHAP_C, ... exchange in case of stgt target ? Any ideas ? > > Do you need this feature? If so, I can implement it (some time this > month probably). That will be great. Thanks. -- To unsubscribe from this list: send the line "unsubscribe stgt" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
