On Tue, Feb 15, 2022 at 1:42 PM Peter Westlake <peter.westlake@pobox.com> wrote:
On Tue, 15 Feb 2022, at 17:49, Adi Roiban wrote:
> Hi
>
> On Tue, 15 Feb 2022 at 15:47, Peter Westlake <peter.westlake@pobox.com> wrote:
>>
>> I'm using twisted.conch.telnet to send commands to a switch, and the output is coming back with newlines added after the 80th character. It doesn't do that if I log in to the switch interactively. Is there some configuration setting in the telnet protocol that I haven't found, to stop it doing this?
>>
>
> I am not sure what "log in to the switch interactively" really means :)

"telnet switchname" at the Linux command line, instead of running my Twisted program.

> Since this is telnet, I guess that you can capture the communication
> between and you and  the switch and see what are the differences.

I'll try. But even if I find it, it will be Twisted sending the different messages, and I'll still need to know how to stop it wrapping.

In general, Telnet has a lot of negotiable features.  It's not too likely that Twisted's telnet implementation and telnet(1) negotiate exactly the same features right out of the box.  If you figure out what telnet(1) and this switch are negotiating then it will probably be fairly straightforward to convince your Twisted code to behave the same way (application-controllable feature negotiation is one of the main features of twisted.conch.telnet).
 

Peter.
_______________________________________________
Twisted mailing list -- twisted@python.org
To unsubscribe send an email to twisted-leave@python.org
https://mail.python.org/mailman3/lists/twisted.python.org/
Message archived at https://mail.python.org/archives/list/twisted@python.org/message/P4YLAR6GXSEMD3C2HPEVMNI6OXMXNDSY/
Code of Conduct: https://twisted.org/conduct