From: Sebastian Pipping <webmaster@hartwork.org>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: Re: git clone against firewall
Date: Fri, 15 Jan 2010 20:12:16 +0100 [thread overview]
Message-ID: <4B50BE10.5010603@hartwork.org> (raw)
In-Reply-To: <7vzl4fz0zb.fsf@alter.siamese.dyndns.org>
On 01/15/10 19:17, Junio C Hamano wrote:
> What do you exactly mean by "blocking"?
I chose "BLOCK always" as action for that port in my home router
(Netgear ProSafe 802.11g) config. No idea how it's exactly doing that.
> I am guessing that you can resolve the hostname in your environment
> (i.e. you configured your NAT to let DNS go directly outside).
Name resolution works, yes.
> What
> happens when you try the following?
>
> $ telnet git.overlays.gentoo.org 9418
>
> Do you get:
>
> Trying 66.219.59.40...
> telnet: Unable to connect to remote host: Connection refused
>
> If you get something like:
>
> Trying 66.219.59.40...
> Connected to pelican.gentoo.org.
> Escape character is '^]'.
>
> then I don't think you are blocked, and if that is the case, there is not
> much we can do about it.
I get a loop/freeze on
Trying 66.219.59.40...
nothing more. Can you deduce from that, what's happening?
> I think your firewall can help, though, by not pretending to be allowing
> the connection and then blocking you halfway.
I'm afraid I cannot configure that.
Sebastian
next prev parent reply other threads:[~2010-01-15 19:12 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-14 23:45 git clone against firewall Sebastian Pipping
2010-01-15 18:17 ` Junio C Hamano
2010-01-15 19:12 ` Sebastian Pipping [this message]
2010-01-15 19:19 ` Sebastian Pipping
2010-01-15 19:30 ` Andreas Schwab
2010-01-15 19:33 ` Sebastian Pipping
2010-01-15 23:03 ` Andreas Krey
2010-01-18 2:04 ` Sebastian Pipping
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4B50BE10.5010603@hartwork.org \
--to=webmaster@hartwork.org \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).