Hi

I am having problems with NET::TELNET from my pc to a unix platform and from there telnet to a second unix like platform. On the final platform I want to put it into a command mode. However the prompt I get back from the shell is not being recognised due to some odd characters being returned. My code is simply:- 

    $telnet->prompt('/> $/');
    $telnet->print('ncli');

[download]
and the output I get is:- 
$ ncli

[ManagedElement=1]> 

[download]
These last three characters in hex are 1B 5B 6D.

If I do the same operation manually from the same intermediate node (using the unix telnet command) I see:- 

$ ncli
[ManagedElement=1]>

[download]
Any ideas on how I can either live with these characters (i.e. make the prompt accept them) or stop them all together.

THanks...bih71

In reply to Odd characters in Telnet prompt by bih71

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.