Stories
Slash Boxes
Comments
NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.

All the Perl that's Practical to Extract and Report

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.
  • by purlah (7048) on 2006.06.28 23:38 (#48453)
    it turns out i have to deal with this this week as well. i think this will become an increasingly common problem, and what we should do is fashion appropriate modifications into the command structure of Net::Telnet so it can be used as a drop-in replacement rather than having to rewrite everything via Expect (although that may get called on the backend).. anyway, let me know please if you have made progress on this yet.
    • I'm having the same problem. I have a bunch of Net::Telnet::Cisco scripts that need to be converted for SSH only use; the US DOD mandates that telnet never be used for switch management functions so we're having to convert everything. Did you guys make any headway? I'm not a big fan of expect either...
      • Expect worked fine for us.. but then a co-worker pointed out to me that he got stuck in a similar and got a way out by actually just RTFM. He found the solution in the Net::Telnet [cpan.org] example. It included an example with forking SSH. I still have to implement this solution but it worked for him :)
      • I know this is an old thread... but automating Cisco things has popped to the top of some people's stacks with these recent IOS expliots being announced.

        Anyway, check out my module for this, which is a wrapper around Net::Telnet and supports Telnet, SSH and Serial line scripted command sequences.

        Net::Appliance::Session 0.09 [cpan.org] (0.12 will be out this week, with some nice new features)