public inbox for overseers@sourceware.org
 help / color / mirror / Atom feed
From: Jonathan Larmour <jlarmour@redhat.co.uk>
To: Jason Molenda <jason-swarelist@molenda.com>
Cc: Jimmy Guo <guo@cup.hp.com>, overseers@sourceware.cygnus.com
Subject: Re: need SSH help
Date: Sat, 30 Dec 2000 06:08:00 -0000	[thread overview]
Message-ID: <39888C6A.97C430B2@redhat.co.uk> (raw)
In-Reply-To: <20000802135016.B10481@shell17.ba.best.com>

Jason Molenda wrote:
> 
> On Wed, Aug 02, 2000 at 01:31:57PM -0700, Jimmy Guo wrote:
> > I'm trying to connect to sourceware.cygnus.com to commit patches.
> > Here is the connection log:
> >
> > hpcleara.cup.hp.com: Connecting to sourceware.cygnus.com [205.180.83.71] port 22
> > hpcleara.cup.hp.com: Allocated local port 1023.
> > hpcleara.cup.hp.com: connect: Connection refused
> > hpcleara.cup.hp.com: Trying again...
> 
> You might be firewalled.  Can you successfully telnet to sourceware
> port 22?

Or (as I had happen recently) it may be being firewalled because the local
port is <1024. Some routers may have blanket deny rules for packets flowing
into, say, HP with ports < 1024. Instead they should only be filtering SYN
TCP packets, i.e. only if you are trying to initiate a connection.

But that may be the problem. If it is, then you can configure ssh to not
use privileged ports using the "UsePrivilegedPorts no" directive in your
.ssh/config.

Jifl
-- 
Red Hat, 35 Cambridge Place, Cambridge, UK. CB2 1NS  Tel: +44 (1223) 728762
"Plan to be spontaneous tomorrow."  ||  These opinions are all my own fault

WARNING: multiple messages have this Message-ID
From: Jonathan Larmour <jlarmour@redhat.co.uk>
To: Jason Molenda <jason-swarelist@molenda.com>
Cc: Jimmy Guo <guo@cup.hp.com>, overseers@sourceware.cygnus.com
Subject: Re: need SSH help
Date: Wed, 02 Aug 2000 14:02:00 -0000	[thread overview]
Message-ID: <39888C6A.97C430B2@redhat.co.uk> (raw)
Message-ID: <20000802140200.yHQzYBmxMDuA1B73hx4Aj7ToNzHbEvTWESMaMtGfJck@z> (raw)
In-Reply-To: <20000802135016.B10481@shell17.ba.best.com>

Jason Molenda wrote:
> 
> On Wed, Aug 02, 2000 at 01:31:57PM -0700, Jimmy Guo wrote:
> > I'm trying to connect to sourceware.cygnus.com to commit patches.
> > Here is the connection log:
> >
> > hpcleara.cup.hp.com: Connecting to sourceware.cygnus.com [205.180.83.71] port 22
> > hpcleara.cup.hp.com: Allocated local port 1023.
> > hpcleara.cup.hp.com: connect: Connection refused
> > hpcleara.cup.hp.com: Trying again...
> 
> You might be firewalled.  Can you successfully telnet to sourceware
> port 22?

Or (as I had happen recently) it may be being firewalled because the local
port is <1024. Some routers may have blanket deny rules for packets flowing
into, say, HP with ports < 1024. Instead they should only be filtering SYN
TCP packets, i.e. only if you are trying to initiate a connection.

But that may be the problem. If it is, then you can configure ssh to not
use privileged ports using the "UsePrivilegedPorts no" directive in your
.ssh/config.

Jifl
-- 
Red Hat, 35 Cambridge Place, Cambridge, UK. CB2 1NS  Tel: +44 (1223) 728762
"Plan to be spontaneous tomorrow."  ||  These opinions are all my own fault

  parent reply	other threads:[~2000-12-30  6:08 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-12-30  6:08 Jimmy Guo
2000-08-02 13:32 ` Jimmy Guo
2000-12-30  6:08 ` Jason Molenda
2000-08-02 13:53   ` Jason Molenda
2000-12-30  6:08   ` Jimmy Guo
2000-08-02 14:04     ` Jimmy Guo
2000-12-30  6:08   ` Jonathan Larmour [this message]
2000-08-02 14:02     ` Jonathan Larmour
2000-12-30  6:08   ` Jimmy Guo
2000-08-02 13:59     ` Jimmy Guo
2000-12-30  6:08 ` Chris Faylor
2000-08-02 13:49   ` Chris Faylor
2000-12-30  6:08 ` Jim Kingdon
2000-08-02 13:51   ` Jim Kingdon
2000-12-30  6:08   ` Jim Blandy
2000-08-03 15:22     ` Jim Blandy
2000-12-30  6:08   ` Jim Blandy
2000-08-03 15:23     ` Jim Blandy
2000-12-30  6:08     ` Tom Tromey
2000-08-03 15:25       ` Tom Tromey

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=39888C6A.97C430B2@redhat.co.uk \
    --to=jlarmour@redhat.co.uk \
    --cc=guo@cup.hp.com \
    --cc=jason-swarelist@molenda.com \
    --cc=overseers@sourceware.cygnus.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.
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).