Menu

Pasting long pieces of text

2018-12-17
2019-01-21
1 2 > >> (Page 1 of 2)
  • Francisco Jorge

    Francisco Jorge - 2018-12-17

    Hello,

    I am having trouble pasting many lines of text to a console. If I have many lines in the clipboard, only the first three or four of them are pasted to the console, depending on the length of the lines.

    Is there anything I can do to be able to paste all the text in the clipboard, or at least to increase the amount of text that gets pasted?

    Thanks
    Fran

     
  • Noodle

    Noodle - 2018-12-19

    I will look into this later at the weekend.

     
  • Noodle

    Noodle - 2018-12-20

    I can't reproduce the issue. I can paste all the text with 10000 lines myself. If it is ok, could you please attach the content in a txt file?

     
  • Francisco Jorge

    Francisco Jorge - 2018-12-22

    Hi. Maybe it depends on the behavior of the host where I am pasting the text, because I have tried pasting the same text on an ssh session to vim on a 'normal' host and there it is working fine. So I do not think the problem lies on the text.

    I am having trouble pasting the text on a Juniper router running on a virtual machine (EVE-NG). Perhaps the CLI of that virtualized router is too slow. That CLI also offers a TAB completion facility, which might be interfering during the pasting of the text. I don't know.

    The thing is that I have tried pasting the same amount of text onto the same router with MobaXterm and that way it works fine.

    Regards.

     
  • Noodle

    Noodle - 2018-12-24

    Would you please check the env command(env |grep TERM) with the putty-nd and the MobaXterm?
    I guess the TERM env is not wrong with putty-nd.

     
  • Francisco Jorge

    Francisco Jorge - 2019-01-02

    I both cases the TERM variable is vt100:

    putty-nd:

    root@HL4:~ # env | grep TERM
    TERM=vt100

    MobaXterm:

    root@HL4:~ # env | grep TERM
    TERM=vt100

     
  • Noodle

    Noodle - 2019-01-05

    Thanks, man.
    So it is not the TERM issue.
    The last but painful way is to turn on the packets logs to check if it sends the buffer out.
    The configuration items can be found via [Session -> Loggings]

     
  • Francisco Jorge

    Francisco Jorge - 2019-01-10

    Hi,

    I have taken some lines from notepad++ and pasted to the putty-nd session.

    These are the lines copied and pasted:

    ip route 5.52.34.76 255.255.255.252 5.5.50.1 tag 50 name AUX-AFUS1
    ip route 5.52.34.76 255.255.255.252 5.5.50.2 tag 50 name AUX-AFUS1
    ip route 5.56.142.252 255.255.255.252 5.5.50.1 tag 50 name AUX-AFUS1
    ip route 5.56.142.252 255.255.255.252 5.5.50.2 tag 50 name AUX-AFUS1
    ip route 5.56.142.204 255.255.255.252 5.5.50.33 tag 50 name AUX-AFUS2
    ip route 5.56.142.204 255.255.255.252 5.5.50.34 tag 50 name AUX-AFUS2
    ip route 5.52.43.228 255.255.255.252 5.5.53.33 tag 50 name AUX-CZFUS1
    ip route 5.52.43.228 255.255.255.252 5.5.53.34 tag 50 name AUX-CZFUS1
    ip route 5.52.34.64 255.255.255.248 5.5.50.1 tag 50 name AUX-AFUS1
    ip route 5.52.34.64 255.255.255.248 5.5.50.2 tag 50 name AUX-AFUS1
    ip route 5.56.142.224 255.255.255.252 5.5.50.33 tag 50 name AUX-AFUS2
    ip route 5.56.142.224 255.255.255.252 5.5.50.34 tag 50 name AUX-AFUS2
    ip route 5.56.142.228 255.255.255.252 5.5.50.1 tag 50 name AUX-AFUS1
    ip route 5.56.142.228 255.255.255.252 5.5.50.2 tag 50 name AUX-AFUS1
    ip route 5.52.34.128 255.255.255.240 5.5.50.33 tag 50 name AUX-AFUS2
    ip route 5.52.34.128 255.255.255.240 5.5.50.34 tag 50 name AUX-AFUS2
    ip route 5.52.35.216 255.255.255.248 5.5.50.33 tag 50 name AUX-AFUS2
    ip route 5.52.35.216 255.255.255.248 5.5.50.34 tag 50 name AUX-AFUS2
    ip route 5.52.24.52 255.255.255.252 5.5.5.193 tag 50 name AUX-BFUS8
    ip route 5.52.24.52 255.255.255.252 5.5.5.194 tag 50 name AUX-BFUS8
    ip route 5.52.127.0 255.255.255.252 5.5.52.225 tag 50 name AUX-BJFUS1
    ip route 5.52.127.0 255.255.255.252 5.5.52.226 tag 50 name AUX-BJFUS1
    ip route 5.52.127.92 255.255.255.252 5.5.52.225 tag 50 name AUX-BJFUS1
    ip route 5.52.127.92 255.255.255.252 5.5.52.226 tag 50 name AUX-BJFUS1
    ip route 5.52.127.4 255.255.255.252 5.5.52.225 tag 50 name AUX-BJFUS1
    ip route 5.52.127.4 255.255.255.252 5.5.52.226 tag 50 name AUX-BJFUS1
    ip route 5.52.85.120 255.255.255.252 5.5.57.162 tag 50 name AUX-BLFUS1
    ip route 5.52.85.120 255.255.255.252 5.5.57.161 tag 50 name AUX-BLFUS1
    ip route 5.52.85.124 255.255.255.252 5.5.57.162 tag 50 name AUX-BLFUS1
    ip route 5.52.85.124 255.255.255.252 5.5.57.161 tag 50 name AUX-BLFUS1
    ip route 5.52.85.136 255.255.255.252 5.5.57.162 tag 50 name AUX-BLFUS1
    ip route 5.52.85.136 255.255.255.252 5.5.57.161 tag 50 name AUX-BLFUS1
    ip route 5.52.85.140 255.255.255.252 5.5.57.162 tag 50 name AUX-BLFUS1
    ip route 5.52.85.140 255.255.255.252 5.5.57.161 tag 50 name AUX-BLFUS1
    ip route 5.52.85.168 255.255.255.252 5.5.57.162 tag 50 name AUX-BLFUS1
    ip route 5.52.85.168 255.255.255.252 5.5.57.161 tag 50 name AUX-BLFUS1

    I have only been able to paste 28 lines of the above and part of the 29th.

    The logs show many strange characters that do not appear on the terminal. Notepad++ interprets those characters as BackSpaces (BS). You can find the logs in the attached file.

    Hope this helps
    Fran

     
  • Noodle

    Noodle - 2019-01-11

    Cool, I see.
    So it is what putty-nd received from the server. I still want to know what putty-nd sends.
    Would you please log with the "SSH packets" level again?
    Thanks!
    BR//LuDong

     
  • Francisco Jorge

    Francisco Jorge - 2019-01-11

    Hi,

    It is not an ssh connection, it is a telnet connection. This is the only thing that I see on the log, even if I paste the above lines:

    =~=~=~=~=~=~=~=~=~=~=~= PuTTY log 2019.01.11 15:51:39 =~=~=~=~=~=~=~=~=~=~=~=
    Event Log: Writing new session log (SSH raw data mode) to file: D:\t148594\Desktop\putty.log
    Event Log: Looking up host "10.57.25.175"
    Event Log: Connecting to 10.57.25.175 port 33161
    Event Log: client: WILL NAWS
    Event Log: client: WILL TSPEED
    Event Log: client: WILL TTYPE
    Event Log: client: WILL NEW_ENVIRON
    Event Log: client: DO ECHO
    Event Log: client: WILL SGA
    Event Log: client: DO SGA
    Event Log: server: DO TTYPE
    Event Log: server: WILL ECHO
    Event Log: server: WILL SGA
    Event Log: server: DONT LINEMODE
    Event Log: server: SB TTYPE SEND
    Event Log: client: SB TTYPE IS XTERM

    Regards.
    Fran

     
  • Noodle

    Noodle - 2019-01-13

    Hi Fran,

    Thanks man!
    Would you please take a pcap file with Wireshark? I want to know where does the long BS come from.

    BR//LuDong

     
  • Francisco Jorge

    Francisco Jorge - 2019-01-16

    Here you are.

    10.57.25.175 is the server, while 10.152.37.230 is the client.

    Hope it helps. Thanks for your interest.
    Fran

     
  • Noodle

    Noodle - 2019-01-16

    Hi Fran,

    Thanks for the info.
    I am afraid the issue lies in the server side.
    It looks clear with the wireshark dialog "following the tcp stream" as in the attachment.
    The client(putty-nd) sent the scripts as pasted, in many packets actually.
    The server then replyed with the long BS(0x08) inside. There must be something wrong on the server handling the scripts.
    So all that I can do, is to suggest you change the telnet server to other options, for example the dropbare(https://matt.ucc.asn.au/dropbear/dropbear.html).
    And thank you for your patience. This remind me of the days when I was supporting in Ericsson. It feels good.

    BR//LuDong

     
  • Francisco Jorge

    Francisco Jorge - 2019-01-16

    Hi Ludong.

    Thanks for you help. I have seen the TCP stream and, as you said, it is the server who sends those strange characters. However, MobaXterm seems to deal with them better that putty-nd, since in MobaXterm I do not see this behavior and I can paste all the text lines.
    I was just wondering if putty-nd could behave in this sense similar to MobaXterm.

    Thanks again.
    Fran

     
  • Noodle

    Noodle - 2019-01-17

    Hi Fran,

    Honestly, I don't know how to make the workaround as I don't know why the server generates the BS char.
    Sorry man.

    BR//LuDong

     
  • Francisco Jorge

    Francisco Jorge - 2019-01-18

    Hi.

    Please, do not get me wrong. I just want to help you find this issue in order to make putty-nd better. If you feel that I am being too insistent, just discard this message ;)

    I have done new wireshark captures with the same server, and using MobaXterm and putt-nd as clients.

    The relevant packets start:

    • putty-nd capture: 384
    • MobaXterm capture: 190

    As you can see, MobaXterm sends a 120 bytes packet, then a 56 bytes packet and then it is the server who responds with three 60 bytes packets. After that, MobaXterm sends an ACK. This repeats several times.

    However, putty-nd sends a bunch of 120-124 bytes and 56 bytes packes that seen to collapse the server.

     
  • Francisco Jorge

    Francisco Jorge - 2019-01-18

    here you can find the putty-nd capture

     
  • Noodle

    Noodle - 2019-01-18

    Wow, I don't know what to say. update you later.

     
  • Noodle

    Noodle - 2019-01-18

    Hi Fran,

    I can't find the content sent out in mobaxterm.pasting.long.text.pcapng. But nevermind.
    The line paste delay option is under terminial -> line paste delay.

    And if you want it to be sent in a packet, just open the command editor on the toolbar. Just paste in the editor dialog and click send. It is not controled by the line paste delay option yet.

    BR//LuDong

     
  • Noodle

    Noodle - 2019-01-18

    the config option pic.

     
  • Francisco Jorge

    Francisco Jorge - 2019-01-18

    I have uncompressed the attachment, renamed putty.exe.bak to putty.exe, and executed it. But I get an errror telling me that putty.exe cannot be run. I have tried to put it in serveral folders, to check if it is a permissions issue, but no luck.

    The putty.exe.bak file is 2,74 Mb long, while putty.exe for noodle-nd 6.5 is 1,11Mb.

    Strange enough.

     
  • Noodle

    Noodle - 2019-01-18

    no detail errors? the release version will be zipped with upx.exe. So it will be smaller.

     
  • Noodle

    Noodle - 2019-01-18

    I just downloaded and tested it on another pc. It works ok.

     

    Last edit: Noodle 2019-01-18
  • Francisco Jorge

    Francisco Jorge - 2019-01-21

    Hi.

    Somehow it runs now, and with a "Line paste delay" of 10 ms I have been able to paste all the text!!!!!

    I am so grateful!!! Thanks a lot for your time and your patience!!! Hope to see this and the "Select text by clicking start and shift clicking end of range" features in the upcoming release of this great piece of software.

    Fran

     
1 2 > >> (Page 1 of 2)

Log in to post a comment.