Problem solved. We had ssh_options[:port] = 22 in our recipe, which seems to have taken precedence over the gateway tunnels.
Cheers, / oscar On Oct 8, 11:52 am, rylin <[EMAIL PROTECTED]> wrote: > Hey, > I'm seeing issues with a gateway configuration in 1.4.1, and I'm > guessing it's no longer supported - but I'd be thankful for any > help ;-) > > What seems to happen is that no matter what I set the gateway to be, > it thinks localhost is the gateway, but the debug data is fine. > > establishing connection to gateway 205.234.x.y > starting connection to gateway 205.234.x.y > gateway connection established > establishing connection to 10.0.1.110 via gateway > establishing connection to 10.0.1.120 via gateway > establishing connection to 10.0.1.130 via gateway > establishing connection to 10.0.1.140 via gateway > > At this point, I can ssh to *localhost*:65532 (and the other forwarded > ports) > [EMAIL PROTECTED] www]$ ssh -l oscar -p 65532 localhost > Last login: Mon Oct 8 06:27:27 2007 from 10.0.1.1 > [EMAIL PROTECTED] ~]$ > > So far so good. > The problem here is that all tasks get run against localhost:22 > instead of localhost:forwardedport - i.e. the machine running > capistrano. > > I'd be thankful for any advice, especially ones that don't involve > upgrading to 2.0 ;) > > Cheers, > / oscar --~--~---------~--~----~------------~-------~--~----~ To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/capistrano -~----------~----~----~----~------~----~------~--~---
