in reply to Re^2: telnet from host to remote host
in thread telnet from host to remote host

        "Software interprets lawyers as damage, and routes around them" - Larry Wall

Replies are listed 'Best First'.
Re^4: telnet from host to remote host
by abdullahcaldir (Initiate) on Sep 01, 2016 at 17:46 UTC
    < 0x00000: 0d 0a 4d 6f 6e 74 61 56 69 73 74 61 28 52 29 20 ..Monta +Vista(R) < 0x00010: 4c 69 6e 75 78 28 52 29 20 43 61 72 72 69 65 72 Linux(R +) Carrier < 0x00020: 20 47 72 61 64 65 20 45 64 69 74 69 6f 6e 20 34 Grade +Edition 4 < 0x00030: 2e 30 20 28 30 36 30 30 39 39 35 29 0d 0a 4c 69 .0 (060 +0995)..Li < 0x00040: 6e 75 78 2f 70 70 63 20 32 2e 36 2e 31 30 5f 6d nux/ppc + 2.6.10_m < 0x00050: 76 6c 63 67 65 34 30 31 2d 38 35 35 35 2d 63 70 vlcge40 +1-8555-cp < 0x00060: 6c 61 62 0d 0a 0d 0a lab.... < 0x00000: 45 43 31 38 33 30 2d 32 2d 31 20 6c 6f 67 69 6e EC1830- +2-1 login < 0x00010: 3a 20
    :
Re^4: telnet from host to remote host
by abdullahcaldir (Initiate) on Sep 01, 2016 at 17:49 UTC

    I tried to send ^E it did not work. Also I have tried $telnet->dump_log($filename) it was so different 0x0000 that kind of things

    Do you have other any idea ?
      I do not understand what you mean by:
      Also I have tried $telnet->dump_log($filename) it was so different 0x0000 that kind of things

      Did you get a log file ?

      Did the contents of that file help you diagnose the issue?

      A more sane approach would be to use Net:Telnet to connect directly to your target machine, instead of going through an intermediate host.

      You could also use something like tcpdump/wireshark, to capture packets between your intermediate and target hosts, to see what is going across, and where the protocol is breaking.

              "Software interprets lawyers as damage, and routes around them" - Larry Wall