2011/6/21 Konstantin Khomoutov <flatw...@users.sourceforge.net>:
> On Tue, 21 Jun 2011 08:33:42 -0300
> Vinicius Massuchetto <viniciusmassuche...@gmail.com> wrote:
>> >> Yes. It appears to be listening properly. Here's the output of
>> >> `netstat -ntlp | grep git`:
>> >> tcp 0 0 0.0.0.0:9418 0.0.0.0:* LISTEN 23528/git-daemon
>> >> tcp6 0 0 :::9418 :::* LISTEN 23528/git-daemon
>> > Hmm, so it listens.
>> > Now what is the error git on a client machine shows you when you're
>> > trying to clone?
>> $ git clone -v git://cei.inf.ufpr.br/bcc.git
>> Initialized empty Git repository in /home/bcc/vam06/temp/bcc/.git/
>> cei.inf.ufpr.br[0: 188.8.131.52]: errno=Connection timed out
>> cei.inf.ufpr.br[0: 2801:82:80ff:c:216:3eff:fecc:bc]: errno=Network is
>> fatal: unable to connect a socket (Network is unreachable)
> Well, leaving aside inability to connect via IPv6, let's look at the
> IPv4 attempt: this error actually means that the destination socket did
> not respond within a certain timeout to the connection request.
> So may it be that you're simply having firewall issues?
That's problably it. As I can't fix that, we'll go for a different
approach, to make the repo public via http.
Many thanks for your help.
You received this message because you are subscribed to the Google Groups "Git
for human beings" group.
To post to this group, send email to firstname.lastname@example.org.
To unsubscribe from this group, send email to
For more options, visit this group at