Forum Discussion
smp_86112
Cirrostratus
CirrostratusProblem with RADIUS monitor
I have LTMs running 9.3.1HF6 in an Active/Standby config. I have 5 pools, each with two members, which are being checked by a RADIUS monitor. On the Active unit, the checks are being performed and the...
david_20523
Nimbostratus
NimbostratusI wrote this for telnet in route domains but it would be easy to change it for SSH and other bash tools. I found it easier than keep doing ipv6 converts
modify script telnet {
proc script::run {} {
set base_record [split $tmsh::argv ]
set ipdomain [lindex $base_record 1]
set ip_domain [split $ipdomain "%" ]
set ip_addr [lindex $ip_domain 0]
set domain [lindex $ip_domain 1]
set hex_domain [format %04x $domain]
set port [lindex $base_record 2 ]
set string [list "2620:0000:0c10:f501:0000:$hex_domain:$ip_addr"]
if {$tmsh::argc eq 2} {
catch {exec telnet "$string"} result
} else {
catch {exec telnet "$string" "$port"} result
}
puts "$result"
if {$base_record eq "telnet" } {
puts "You must supply at least a IP address and route domain"
}
}
proc script::help {} {
tmsh::add_help "This will allow telnet to connect to a IP within a route domain\n\nUsage telnet <%route_domain_id> <%route_domain_id> "
}
} - Which platform are you developing on? Also, which version of perl2exe are you using? I haven't had any experience converting our sample code to standalone executables so if you pass along your specifics, I'll see if I can get things working. Crypt::SSLeay uses a shared library and relies on openssl's shared library. There may be a problem with the migration of the reliant shared objects.
-Joe 
jajamax_127538I'm running activestate perl 5.8 on an xp box using the latest version of perl2exe. The problem seems to be in the ssleay.dll. The error message is"501 Protocol scheme 'https' is not supported (Crypt::SSLeay not installed) at C:\Perl\2varsA.exe line 113" 2VarsA is the locallbnode.pl renamed.- Now for the final piece...
Try adding the following lines to your script.perl2exe_bundle "c:\perl\bin\ssleay32.dll"; perl2exe_bundle "c:\perl\bin\libeay32.dll";
Replace "c:\perl\bin" with the location of your perl binaries directory. The perl2exe_bundle directive, causes the modules to be included in the compiled executable and extracted at runtime. The manual documents this.
Let me know if this works out for you.
-Joe - A quick update. I've got sample code compiled and running on my dev machine. I had to add the following lines to the top of the script.
use Crypt::SSLeay; use SOAP::Transport::HTTP; use LWP::UserAgent; use URI::https; use Carp::Heavy; use LWP::Protocol::https; use LWP::Authen::Basic;
In the perl2exe manual(http://www.indigostar.com/pxman.htm), I found a runtime flag that helped out. When you run the executable, if you add '-p2x_test' before any other arguments, missing module information is presented. I still get a warning at compile time, but the executable is created and works.
The error you presented for "... (Crypt::SSLeay not installed)" is something I'll look into. You might have to use the perl2exe_bundle filename directive discussed in their manual to bundle additional dll's needed when deploying to other machines. I'll try to verify this for you.
-Joe
![\"F5](\"https://www.f5.com/content/dam/f5/f5-logo.svg\"){kind=logo}
