The native git transport uses TCP port 9418. However, git can also run over ssh (often used for pushing), http, https, and less often others.
You can look at the repository URL to find out which port it uses. Notice that many public repositories have several alternate URLs; for instance, the kernel.org repositories have git://, http://, and https:// URLs.
The common URL schemes for git repositories are:
ssh:// - default port 22
git:// - default port 9418
http:// - default port 80
https:// - default port 443
If the URL does not have a scheme, it it using ssh with a slightly different syntax.
See the git fetch manpage for more details on the available URL schemes.
It depends on the repository.
The native git transport uses TCP port 9418. However, git can also run over ssh (often used for pushing), http, https, and less often others.
You can look at the repository URL to find out which port it uses. Notice that many public repositories have several alternate URLs; for instance, the kernel.org repositories have
git://
,http://
, andhttps://
URLs.The common URL schemes for git repositories are:
ssh://
- default port 22git://
- default port 9418http://
- default port 80https://
- default port 443If the URL does not have a scheme, it it using ssh with a slightly different syntax.
See the git fetch manpage for more details on the available URL schemes.
Specifically TCP 9418, no need for UDP.
Reference.
Git uses port 9418. You can view connections using that port with
netstat -ntpl|grep -i 9418
Open 9418 and your traffic will pass through the firewall.
I've also found that the outbound SSH port 22 might need to be open as well as port 9418 for Git (both TCP). Depends on your setup though!