On 01/06/2016 10:06 AM, james harvey wrote:
After more digging, I found out this out of no where hex string is
referred to as "initiator_ext", and is being sent since srp_daemon.sh
give srp_daemon the "-n" flag. Since there's no user-set
initiator_ext, srp_daemon grabs it from somewhere.
If I want to continue using the "-n" flag, how can I find out what my
initiator is going to send as initiator_ext, so the target can be set
up to work with it?
Or, can I set my own initiator_ext, it looks by appending it to
/etc/srp_daemon.conf ?
Why doesn't ibsrpdm give the initiator_ext value?
Hello James,
What makes you think that ibsrpdm doesn't give you the initiator_ext
value ? Installing and activating the srptools package with default
options should be sufficient to make an SRP initiator log in to an SRP
target system. That will make ibsrpdm and srp_daemon query the login
parameters from the target system, including initiator_ext, and use
these parameters to log in to the target system. BTW, the latest version
of srptools is available from
http://downloads.openfabrics.org/downloads/srptools/.
Bart.