# getting paramiko to see /etc/ssh/ssh\_config

**URL:** <https://forum.ansible.com/t/getting-paramiko-to-see-etc-ssh-ssh-config/12664>\
**Category:** Ansible Project\
**Tags:** ansible-project\
**Created:** [April 11, 2013, 4:05pm UTC](https://forum.ansible.com/t/getting-paramiko-to-see-etc-ssh-ssh-config/12664 "2013-04-11T16:05:57Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Timothy\_Gerla](https://avatars.discourse-cdn.com/v4/letter/t/977dab/32.png) [@Timothy\_Gerla](https://forum.ansible.com/u/Timothy_Gerla)\
**Post date:** [April 11, 2013, 4:05pm UTC](https://forum.ansible.com/t/getting-paramiko-to-see-etc-ssh-ssh-config/12664/1 "2013-04-11T16:05:57Z")

</div>

Hi Makimoto,

If you want Ansible to rely on the ssh configuration file, you'll want  
to use the OpenSSH transport instead of the Paramiko transport. You  
can do this by specifying:

-c ssh

..on the command line. You can also use the variables ansible\_ssh\_host  
and ansible\_ssh\_port in your inventory file if you just have a simple  
port-based ssh jump host:

[myhosts]  
realhost ansible\_ssh\_host=jumphost ansible\_ssh\_port=2222

...but I am not sure if this wil work in your circumstance.

Hope this helps!

-Tim

---

<div class="post-metadata">

**Author:** ![Brian\_Coca1](https://avatars.discourse-cdn.com/v4/letter/b/278dde/32.png) [@Brian\_Coca1](https://forum.ansible.com/u/Brian_Coca1)\
**Post date:** [April 11, 2013, 4:38pm UTC](https://forum.ansible.com/t/getting-paramiko-to-see-etc-ssh-ssh-config/12664/2 "2013-04-11T16:38:04Z")

</div>

Ssh transport works fine with bridges/jumphosts

Brian Coca