On 25 January 2011 15:27, Christian Robottom Reis kiko@linaro.org wrote:
On Tue, Jan 25, 2011 at 03:20:44PM +0100, Mattias Backman wrote:
On 25 January 2011 14:19, Christian Robottom Reis kiko@linaro.org wrote:
On Tue, Jan 25, 2011 at 12:09:39PM +0100, Mattias Backman wrote:
http://omappedia.org/wiki/Using_bzr_and_launchpad_behind_a_proxy
I have also added an authentication file like so: Host *.launchpad.net ProxyCommand corkscrew <our proxy> 8080 %h %p ~/.auth User <my user>
I guess you've seen http://www.mtu.net/~engstrom/ssh-proxy.php already?
Actually no, the web filter tells me I shouldn't read that... "ACCESS TO THIS CATEGORY OF WEB SITES (Proxy Avoidance;Information Technology) IS DENIED." So if you could paste the content in an email och repost it somewhere else it might be useful to me. :)
Man, that's painful. See attached.
Thanks. I actually already set everything up that way.
Sure, this the little that happens.
:~> ssh -v 91.189.90.11 OpenSSH_5.3p1 Debian-3ubuntu4, OpenSSL 0.9.8k 25 Mar 2009 debug1: Reading configuration data /home/ebacmat/.ssh/config debug1: Reading configuration data /etc/ssh/ssh_config debug1: Applying options for * debug1: Connecting to 91.189.90.11 [91.189.90.11] port 22. debug1: connect to address 91.189.90.11 port 22: Connection timed out ssh: connect to host 91.189.90.11 port 22: Connection timed out
:~> ssh -v bazaar.launchpad.net OpenSSH_5.3p1 Debian-3ubuntu4, OpenSSL 0.9.8k 25 Mar 2009 debug1: Reading configuration data /home/ebacmat/.ssh/config debug1: Applying options for *.launchpad.net debug1: Reading configuration data /etc/ssh/ssh_config debug1: Applying options for * debug1: Executing proxy command: exec corkscrew proxy.mydomain.com 8080 bazaar.launchpad.net 22 ~/.auth debug1: permanently_drop_suid: 71419 debug1: identity file /home/ebacmat/.ssh/identity type -1 debug1: identity file /home/ebacmat/.ssh/id_rsa type -1 debug1: identity file /home/ebacmat/.ssh/id_dsa type -1 ssh_exchange_identification: Connection closed by remote host
Could you try applying the corkscrew proxy command for everything under the 91.189.90 subnet, just in case the name resolution is happening in a weird way?
You could also try strace -f -econnect to see what the bzr client is doing -- it might surprise us.
I added the entire subnet which didn't help. The strace did tell me that nothing happens after the call to the proxy. After quite a few different attempts, I have tried to connect to a different server which I happen to know has ssh servers on nearly every port. The corkscrew solution works if I try to ssh to port 21 or 80, it does not work for 22 or anything else. Seems that our proxy will only let traffic out if it's bound for ftp or http ports.
-- Christian Robottom Reis | [+55] 16 9112 6430 | http://launchpad.net/~kiko Linaro Engineering VP | [ +1] 612 216 4935 | http://async.com.br/~kiko