From: Matthew Galgoci <mgalgoci@redhat.com>
To: Venkataramanan.Kumar@amd.com
Cc: jifl@jifvik.org, Hans-Peter Nilsson <hp@bitrange.com>,
overseers@sourceware.org
Subject: Re: FW: svn+ssh connection times out (fwd)
Date: Thu, 30 Aug 2012 21:19:00 -0000 [thread overview]
Message-ID: <alpine.LFD.2.02.1208301715170.19648@oynqr.eqh.erqung.pbz> (raw)
In-Reply-To: <503FB5BF.2000807@jifvik.org>
> Date: Thu, 30 Aug 2012 19:49:35 +0100
> From: Jonathan Larmour <jifl@jifvik.org>
> To: "Kumar, Venkataramanan" <Venkataramanan.Kumar@amd.com>
> Cc: Hans-Peter Nilsson <hp@bitrange.com>, overseers@sourceware.org
> Subject: Re: FW: svn+ssh connection times out (fwd)
>
> On 30/08/12 11:40, Hans-Peter Nilsson wrote:
> > Not sure what *I* am asked to do (or why I was picked), unless
> > it's forwarding a message that bounced (perhaps due to the
> > connection failure) when trying to address the list directly.
>
> Looks like it... the previous mail didn't come through to the
> overseers@gcc.gnu.org list. That implies he can't contact the server at
> all. It seems like it's being filtered by a firewall, but I've checked the
> sourceware machine's own firewall and there's nothing with IP addresses
> 202.* being filtered.
>
> It might be the Red Hat infrastructure where sourceware is co-located is
> filtering things, although that seems unlikely. In particular on
> sourceware I can successfully ping the 202.56.249.162 address he provides.
>
> Kumar, please try pinging sourceware.org from your machine to see if that
> works. You can take off the 'overseers' list in your reply - let's do this
> off list instead.
We are not blocking 202.56.249.162 either directly or indirectly. I can
even ping it from the network gear at the data center.
Perhaps your company has an outbound application firewall that has decided to
block access to sourceware? It is not uncommon. Some companies view ssh
as a vector for exfiltration of data and thus block it.
--
Matthew Galgoci
Network Operations
Red Hat, Inc
919.754.3700 x44155
------------------------------
"It's not whether you get knocked down, it's whether you get up." - Vince Lombardi
prev parent reply other threads:[~2012-08-30 21:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-30 10:40 Hans-Peter Nilsson
2012-08-30 18:49 ` Jonathan Larmour
2012-08-30 20:26 ` Frank Ch. Eigler
2012-08-30 21:19 ` Matthew Galgoci [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=alpine.LFD.2.02.1208301715170.19648@oynqr.eqh.erqung.pbz \
--to=mgalgoci@redhat.com \
--cc=Venkataramanan.Kumar@amd.com \
--cc=hp@bitrange.com \
--cc=jifl@jifvik.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).