From: John David Anglin <dave.anglin@bell.net>
To: "Frank Ch. Eigler" <fche@redhat.com>
Cc: Overseers mailing list <overseers@sourceware.org>, overseers@gcc.gnu.org
Subject: Re: git access from 132.246.10.86 (hiauly3.hia.nrc.ca)
Date: Wed, 24 Mar 2021 18:09:51 -0400 [thread overview]
Message-ID: <06c46bbe-04fc-7403-93ea-897c2f748ccf@bell.net> (raw)
In-Reply-To: <20210324214752.GJ1619@redhat.com>
On 2021-03-24 5:47 p.m., Frank Ch. Eigler wrote:
> Hi -
>
>>> (You can use https:// git urls too.)
>> I just tried a couple of pulls.
>> It is possible that ISP is interfering. That's why I tested other sites.
> OK, tcpdump indicates only TCP-SYN packets being received and
> replied-to by the server. No further packets are received from your
> side to complete the TCP handshake or to exchange data.
>
> 20:01:41.705248 IP hiauly3.hia.nrc.ca.49527 > ip-8-43-85-97.sourceware.org.git: Flags [S], seq 3880651354, win 22080, options [mss 1380,nop,wscale 6,sackOK,eol], length 0
> 20:01:41.705295 IP ip-8-43-85-97.sourceware.org.git > hiauly3.hia.nrc.ca.49527: Flags [S.], seq 2021537575, ack 3880651355, win 29200, options [mss 1460,nop,nop,sackOK,nop,wscale 7], length 0
> 20:01:42.709082 IP ip-8-43-85-97.sourceware.org.git > hiauly3.hia.nrc.ca.49527: Flags [S.], seq 2021537575, ack 3880651355, win 29200, options [mss 1460,nop,nop,sackOK,nop,wscale 7], length 0
> 20:01:44.705048 IP hiauly3.hia.nrc.ca.49527 > ip-8-43-85-97.sourceware.org.git: Flags [S], seq 3880651354, win 22080, options [mss 1380,nop,wscale 6,sackOK,eol], length 0
> 20:01:44.705092 IP ip-8-43-85-97.sourceware.org.git > hiauly3.hia.nrc.ca.49527: Flags [S.], seq 2021537575, ack 3880651355, win 29200, options [mss 1460,nop,nop,sackOK,nop,wscale 7], length 0
> 20:01:46.741079 IP ip-8-43-85-97.sourceware.org.git > hiauly3.hia.nrc.ca.49527: Flags [S.], seq 2021537575, ack 3880651355, win 29200, options [mss 1460,nop,nop,sackOK,nop,wscale 7], length 0
> [...]
>
> I would assume there is some dynamic firewall problem at your end
> that prevents the reply packets from being received. Please try
> traffic through https (port 443) instead, which is less likely to
> be interfered with.
Puzzling.
> % git clone https://gcc.gnu.org/git/gcc.git
That doesn't work either:
-bash-4.4$ git clone -v https://gcc.gnu.org/git/gcc.git gcc-11-new
Cloning into 'gcc-11-new'...
fatal: unable to access 'https://gcc.gnu.org/git/gcc.git/': OpenSSL SSL_connect: SSL_ERROR_SYSCALL in connection to gcc.gnu.org:443
This seems to work:
git clone https://github.com/gcc-mirror/gcc gcc-11-new
and the following also works:
git clone git://github.com/gcc-mirror/gcc gcc-11-new
Thanks,
Dave
--
John David Anglin dave.anglin@bell.net
prev parent reply other threads:[~2021-03-24 22:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-24 19:46 John David Anglin
2021-03-24 19:53 ` Frank Ch. Eigler
2021-03-24 20:04 ` John David Anglin
2021-03-24 21:47 ` Frank Ch. Eigler
2021-03-24 22:09 ` John David Anglin [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=06c46bbe-04fc-7403-93ea-897c2f748ccf@bell.net \
--to=dave.anglin@bell.net \
--cc=fche@redhat.com \
--cc=overseers@gcc.gnu.org \
--cc=overseers@sourceware.org \
/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.
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).