From: "Frank Ch. Eigler" <fche@redhat.com>
To: Overseers mailing list <overseers@sourceware.org>
Cc: overseers@gcc.gnu.org, John David Anglin <dave.anglin@bell.net>
Subject: Re: git access from 132.246.10.86 (hiauly3.hia.nrc.ca)
Date: Wed, 24 Mar 2021 15:53:40 -0400 [thread overview]
Message-ID: <20210324195340.GI1619@redhat.com> (raw)
In-Reply-To: <4c672346-fdad-610c-b711-143abe0a6148@bell.net>
Hi -
> A couple of days ago, git stopped working to clone or pull gcc to 132.246.10.86. I see the following error:
>
> -bash-4.4$ git pull --verbose
> Looking up gcc.gnu.org ... done.
> Connecting to gcc.gnu.org (port 9418) ... 8.43.85.97 done.
> fatal: read error: Connection reset by peer
I don't see any recent attempts from that host in any of the logs.
I have a tcpdump running for a little while, could you try right now?
Is it possible that your ISP is interfering with this traffic?
(You can use https:// git urls too.)
- FChE
next prev parent reply other threads:[~2021-03-24 19:53 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 [this message]
2021-03-24 20:04 ` John David Anglin
2021-03-24 21:47 ` Frank Ch. Eigler
2021-03-24 22:09 ` John David Anglin
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=20210324195340.GI1619@redhat.com \
--to=fche@redhat.com \
--cc=dave.anglin@bell.net \
--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).