FW: svn+ssh connection times out (fwd)

FW: svn+ssh connection times out (fwd)

[Hans-Peter Nilsson]

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.

---------- Forwarded message ----------
Date: Thu, 30 Aug 2012 03:04:57
From: "Kumar, Venkataramanan" <Venkataramanan.Kumar@amd.com>
To: Hans-Peter Nilsson <hp@bitrange.com>
Subject: FW: svn+ssh connection times out

Hi H-P,

Can you please have a look at this issue.

IT people say that traffic is dropping from the other end.  They say AMD NAT 202.56.249.162 added to Access control list in gcc.gnu.org will solve the issue.

-----Original Message-----
From: Kumar, Venkataramanan
Sent: Monday, August 27, 2012 12:00 PM
To: 'overseers@gcc.gnu.org'
Subject: svn+ssh connection times out

Hi,

My account name: vekumar@gcc.gnu.org

I have Write after approval access for the gcc repository.

I am trying to checkout gcc repository using svn+ssh from Bangalore (India).

> svn co svn+ssh://vekumar@gcc.gnu.org/svn/gcc/trunk gcc

Read from socket failed: Connection timed out
svn: Connection closed unexpectedly

I checked with our IT people. They say that gcc.gnu.org site is not allowing the Bangalore office traffic.

Please suggest a way to solve this.

Regards,
Venkat.

Re: FW: svn+ssh connection times out (fwd)

[Jonathan Larmour]

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.

Jifl

> ---------- Forwarded message ----------
> Date: Thu, 30 Aug 2012 03:04:57
> From: "Kumar, Venkataramanan" <Venkataramanan.Kumar@amd.com>
> To: Hans-Peter Nilsson <hp@bitrange.com>
> Subject: FW: svn+ssh connection times out
> 
> Hi H-P,
> 
> Can you please have a look at this issue.
> 
> IT people say that traffic is dropping from the other end.  They say AMD NAT 202.56.249.162 added to Access control list in gcc.gnu.org will solve the issue.
> 
> -----Original Message-----
> From: Kumar, Venkataramanan
> Sent: Monday, August 27, 2012 12:00 PM
> To: 'overseers@gcc.gnu.org'
> Subject: svn+ssh connection times out
> 
> Hi,
> 
> My account name: vekumar@gcc.gnu.org
> 
> I have Write after approval access for the gcc repository.
> 
> I am trying to checkout gcc repository using svn+ssh from Bangalore (India).
> 
>> svn co svn+ssh://vekumar@gcc.gnu.org/svn/gcc/trunk gcc
> 
> Read from socket failed: Connection timed out
> svn: Connection closed unexpectedly
> 
> I checked with our IT people. They say that gcc.gnu.org site is not allowing the Bangalore office traffic.
> 
> Please suggest a way to solve this.
> 
> Regards,
> Venkat.
> 
> 


-- 
--["No sense being pessimistic, it wouldn't work anyway"]-- Opinions==mine

Re: FW: svn+ssh connection times out (fwd)

[Frank Ch. Eigler]

Hi -

> 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.

We have on occasion blacklisted (iptables -j DROP) packets from ip
addresses/ranges where abusive accesses have originated.  202.56.* is not
covered by any of them AFAIK.

- FChE

Re: FW: svn+ssh connection times out (fwd)

[Matthew Galgoci]

> 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