From: Ralf Baechle <ralf@linux-mips.org>
To: "Steven J. Hill" <Steven.Hill@imgtec.com>
Cc: linux-mips@linux-mips.org
Subject: Re: Upgrade of linux-mips.org
Date: Tue, 9 Jun 2015 20:53:24 +0200 [thread overview]
Message-ID: <20150609185324.GD2753@linux-mips.org> (raw)
In-Reply-To: <5577342A.40206@imgtec.com>
On Tue, Jun 09, 2015 at 01:44:58PM -0500, Steven J. Hill wrote:
> On 06/01/2015 08:05 AM, Ralf Baechle wrote:
> > Over the weekend I've upgraded linux-mips.org's Linux distribution. I think
> > everything should be running fine again but just in case you notice any
> > issues, please report to me or the mailing list.
> >
> I cannot connect over port 22 with SSH with interactive shell or with
> git. Is anyone else having connection problems? Thanks.
Lmo has multiple IPs. Due to the excessive number of ssh probes which on
a bad day may actually go ino the 5 digit figures and consume a good bit
of resources in peak times I've limited ssh service to just one address,
148.251.95.138 / 2a01:4f8:201:92aa::3 which is www.linux-mips.org and a
few several other host names.
Ralf
prev parent reply other threads:[~2015-06-09 18:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-01 13:05 Upgrade of linux-mips.org Ralf Baechle
2015-06-09 18:44 ` Steven J. Hill
2015-06-09 18:44 ` Steven J. Hill
2015-06-09 18:53 ` Ralf Baechle [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=20150609185324.GD2753@linux-mips.org \
--to=ralf@linux-mips.org \
--cc=Steven.Hill@imgtec.com \
--cc=linux-mips@linux-mips.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