Re^5: Broken Net::Telnet::Netscreen module?

Too bad, I thought I had the right idea

~~You are not very clear about whether you get error messages or not. If you get any, please post them~~. Otherwise you could repeat the trace and show that output if it changed.

I don't remember the regex syntax $result=\/^-/. Shouldn't the \ be ~ ?

UPDATE: Also you might use Data::Dumper to print out everything in @result, just to be sure what you get back

Comment on Re^5: Broken Net::Telnet::Netscreen module? Select or Download Code

Replies are listed 'Best First'.
Re^6: Broken Net::Telnet::Netscreen module? by spivey49 (Monk) on Aug 13, 2008 at 21:07 UTC
Well, we did fix another problem. Errors would have been returned incorrectly by the module with out revising the regex. `=~/\^-/` works too. Data::Dumper returns what I expected, the command sent to the firewall. I tried commenting out the error check as well with the same results. The script exits silently, no warnings, no errors.	[reply] [d/l]
Re^7: Broken Net::Telnet::Netscreen module? by jethro (Monsignor) on Aug 13, 2008 at 21:47 UTC
The trace you showed before seems to show that the method error() from Telnet.pm was called and the program died in line 535 of Telnet.pm (there is a die statement there). If I'm right you have to find out why error() is called. You can do this for example with the debugger. Set a breakpoint at the foreach line in unsetValue() and single step from there. Where exactly does the program stop? If you never reach the breakpoint, move the breakpoint to a previous line on the next run. If the error shows up only on the second run through unsetValue() 'c'ontinue at the first breakpoint and single step at the next stop You can also do this testing if you put print statements (like `print "1\n"; <statements>; print "2\n";`) between crucial statements and watch what number you see last. But the debugger is ultimately faster UPDATE: Just to make sure, `/\^-/` searches for a literal '^-' somewhere in the string, not for '-' at the start of the string. That is what you want, right? And hopefully you didn't post the real password of your netscreen firewall, especially if it is accessible from the internet	[reply] [d/l] [select]
Re^8: Broken Net::Telnet::Netscreen module? by spivey49 (Monk) on Aug 14, 2008 at 17:22 UTC
Thanks, I missed the die in the trace. Very odd all the checks I've been doing didn't pick that up either. I'll need to figure out why error() is being called. More specifically it's setting $mode to die I believe. That shouldn't be happening. I do want the literal '^-', it's the first two characters in the error messages. It's the real password, but it's also the default and it's in a lab, unaccessible from the internet.	[reply]