negotiationMandatory behavior does not match documentation.

[douglampe]

Per the documentation:

negotiationMandatory: Disable telnet negotiations if needed. Can be used with 'send' when telnet specification is not needed. Telnet client will then basically act like a simple TCP client. Defaults to true.

It appears negotiationMandatory has no impact on send. Since send is basically a passthrough to write, the only checks after sending are for waitFor and sendTimeout. The desired effect of negotiationMandatory: false seems to be achieved by sendTimeout: undefined. However, since sendTimeout defaults to 2000, this is not an obvious option since undefined must be explicitly set.

I believe a better check would be to check for if (this.opts.sendTimeout && negotiationMandatory) unless I am misunderstanding the intent of negotiationMandatory.

[antfurn]

Hi, I've just hit this same issue. I'm guessing this is a recent(ish) change as I've not had this problem with older version.

Thanks, Antony

[mkozjak]

@antfurn able to pinpoint on what version it worked last?

[antfurn]

Pretty sure I was not seeing this issue with v2.0.9
The other version I was using before that was v2.0.4