On Wed, 2013-11-20 at 02:48 -0700, Kumar, Ranjan RK wrote: > Hi nab, > > Thanks for the help. > > I have back ported the patch provided, and was able to make it to > work. But still facing some issues. > > What I need is to authenticate the target using the chap, and still > provide access to any iSCSI initiator trying to connect (ie, with out > using initiator mask). > Yes, this is exactly what commit c3e514427 was added to support. > In demo mode I observed that chap also wont be working. Is there any > solution available for this issue. > Care to be more specific..? > I have set demo_mode_write_protect=0 generate_node_acls=1 > cache_dynamic_acls=1 and i didn't have any initiators being masked to > my target. > FYI, that commit c3e514427 requires that authentication credentials be set from within TPG context in targetcli, eg: /iscsi> cd iqn.2003-01.org.linux-iscsi.devstack.x8664:sn.66fedee52d5d/tpg1/ /iscsi/iqn.20...dee52d5d/tpg1> set auth userid=nab Parameter userid is now 'nab'. /iscsi/iqn.20...dee52d5d/tpg1> set auth password=test12345 Parameter password is now 'test12345'. /iscsi/iqn.20...dee52d5d/tpg1> set auth userid_mutual=ban Parameter userid_mutual is now 'ban'. /iscsi/iqn.20...dee52d5d/tpg1> set auth password_mutual=54321tset Parameter password_mutual is now '54321tset'. I assume these values are not set..? --nab -- To unsubscribe from this list: send the line "unsubscribe target-devel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
