|
Hi Oliver, thanks for the reply!
my $first_router = Net::Appliance::Session->new(...)
$first_router->connect(...)
my $second_router = Net::Appliance::Session->new(
Transport => 'Proxy',
Via => $first_router,
);
$second_router->connect(...)
Not a bad idea, here's my 2 cents if you're interested. In some of the networks I work on it can take 2 or 3 router hops before I can reach my ultimate destination. I work as a consultant and use your module in my auto-backup script I run after finishing work on customer sites. I don't control the policies at these networks and many are partitioned off and/or have access-class statements that make it necessary for me to hop my way through a few routers to finally be able to make a connection to the intended router.
The above would be useful for me if it was architected in a nested manner that allowed for more than 1 router hop.
Expanding on what you have show would this then be possible?
my $third_router = Net::Appliance::Session->new(
Transport => 'Proxy',
Via => $second_router,
);
$third_router->connect(...)
|
(0)
]
