Thanks for taking time to look at it and pointing me to the link. We arrived at a similar work around to go ahead.

I have pointed out before in this discussion, this may not be a problem of tty setting. I can type any number of characters as my command or it's parameter and get it executed on the native telnet connection. Am I missing something?

The main reason of reporting it as a bug/ feature improvement is to have the code modified in the core module itself so that we won't have to write wrappers where ever we use it. In the worst case we can push this wrapper into the package itself so that the end user won't have a clue.

The solution uses bash. What if my system doesn't have one? In our situation the scripts used csh. I have to do modifications at around a dozzne places to switch between bash and csh.

Net::Telnet is a great package and we are using it at many places in our automation. But that doesn't mean we should stop improving it. We missed this bug before probably due to the assumption "tty setting is the culprit". Why not look at it more closely now?

I won't close this bug unless I find a satisfying explanation.

Thanks and regards

Debashish.