StarPort CHAP Incompatibility with 3rd Party iSCSI Target

Initiator (iSCSI, FCoE, AoE, iSER and NVMe over Fabrics), iSCSI accelerator and RAM disk

Moderators: anton (staff), art (staff), Max (staff), Anatoly (staff)

Post Reply
dutch55
Posts: 3
Joined: Thu Nov 04, 2004 7:56 pm

Thu Nov 04, 2004 8:03 pm

I tried the StarPort initiator against an iSCSI target from RASilient Systems. CHAP failed. Here is what one of their developers said when I reported it to them. They think it is your problem:


"The StarPort initiator has some problem with the CHAP state machine. It tries to negotiate AUTH_METHOD at the last step instead of the very first step."

Dear Anton:

If you want to establish a dialog to resolve with them, pls send me a private message.
User avatar
anton (staff)
Site Admin
Posts: 4008
Joined: Fri Jun 18, 2004 12:03 am
Location: British Virgin Islands
Contact:

Thu Nov 04, 2004 8:15 pm

Very interesting :-( OK, we're checking what's wrongs with our code. Thank you for bug report. And sure! I'll be happy to talk to you in private. Just please drop me a message to support@starwind.com. Thank you!
Regards,
Anton Kolomyeytsev

Chief Technology Officer & Chief Architect, StarWind Software

Image
Val (staff)
Posts: 496
Joined: Tue Jun 29, 2004 8:38 pm

Fri Nov 05, 2004 3:53 pm

Dutch55,

We've already fixed the issue and it will be included into the next StarPort build.


Please download the recent StarPort version from our site (v2.4.2 build 20041104)


The issue with incorrect CHAP responses is fixed in the version.

Thank you for the feedback once more.
Best regards,
Valeriy
Post Reply