No internet connectivity

[c.b...@posteo.jp]

I am using the current stable "Git for Windows" git-bash on Windows 10.
The Windows is online of course.

But using ping (or git over ssh) in the git-bash does not work. Ping
says no answer. Git says network is unreachable.
Is git-bash offline by default? Can I configure that?

[Johannes Schindelin]

Hi,

[sorry for the long wait]

Git Bash is neither online nor offline. The `ping.exe` program is not
included in Git for Windows, you should be able to find out from where
it comes via `which ping.exe`. Since it is not included in Git for
Windows, I would consider this not a bug in Git for Windows.

Ciao,
Johannes

>
> --
> You received this message because you are subscribed to the Google Groups
> "git-for-windows" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to git-for-windo...@googlegroups.com.
> To post to this group, send email to git-for...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/git-for-windows/2881276d42322280c23d0fdc4f71d5c1%40posteo.de.
> For more options, visit https://groups.google.com/d/optout.
>

[Nate Hansen]

To further expand on Johannes answer

Git for Windows is just an application its internet connectivity is provided by Windows. If you are experiencing issues with tools like 'ping' (Provided my Microsoft most likely) or using an SSH tunnel you should examine your firewall rules.

For example it is very typical for IT networks to prohibit outgoing ssh connections due to the use of them to circumnavigate firewalls. This is frequently true of ping packets as well.

I would compare the result of a "ping" request from a windows command prompt, if the results differ, its your "local" firewall rules, if you see the same results. You should contact your network administrator for further help.

If your network has a HTTP Proxy you must use you can find some configuration instructions here: https://gist.github.com/evantoli/f8c23a37eb3558ab8765 I would never disable http.<url>.sslVerify configuration setting, for any URL, as it can expose you to man in the middle attacks, or worse. Some git servers also allow for connections with HTTPs instead of ssh if your network prohibits the connection you can investigate that as an option.