public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: Arne Fitzenreiter <arne_f@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: git.ipfire.org Network is unreachable
Date: Thu, 03 Dec 2020 08:41:56 +0100	[thread overview]
Message-ID: <76ea7bd86a2f3c4addccb33758f3e79c@ipfire.org> (raw)
In-Reply-To: <84d3f11b-9d2d-7e56-b6ce-ac2b595811c2@ipfire.org>

[-- Attachment #1: Type: text/plain, Size: 1008 bytes --]

I was also blocked yesterday...

Am 2020-12-02 18:16, schrieb Matthias Fischer:
> On 02.12.2020 16:29, Michael Tremer wrote:
>> I just got kicked out, too.
> 
> Sorry, Michael, but ROTFSTC!
> 
>> The limits seem to be too low.
> 
> Indeed. But its somehow soothing, that I'm not the only one...
> 
> P.S.: Я признаю, что я в России. ;-)
> P.P.S.: 80.144.x.x - yes, this could have been me.
> 
>> -Michael
>> 
>>> On 1 Dec 2020, at 22:04, Peter Müller <peter.mueller(a)ipfire.org> 
>>> wrote:
>>> 
>>> Hello Matthias,
>>> 
>>> assuming you tried to log in from an IP address assigned to DTAG and 
>>> used for dial-up-purposes (80.144.x.x), there have been indeed four 
>>> failed SSH login attempts from it on Sunday morning (~ 08:00 CET).
>>> 
>>> The same IP address caused one failed SSH login attempt again 
>>> yesterday, at 15:56:44 CET, but did not exceed the limit this time. 
>>> :-)
>>> 
>>> Sorry for the inconvenience.
>>> 
>>> Thanks, and best regards,
>>> Peter Müller
>> 

      reply	other threads:[~2020-12-03  7:41 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-29 13:29 Matthias Fischer
2020-12-01 16:06 ` Michael Tremer
2020-12-01 16:19   ` Matthias Fischer
2020-12-01 16:19     ` Michael Tremer
2020-12-01 22:04       ` Peter Müller
2020-12-02 15:29         ` Michael Tremer
2020-12-02 17:16           ` Matthias Fischer
2020-12-03  7:41             ` Arne Fitzenreiter [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=76ea7bd86a2f3c4addccb33758f3e79c@ipfire.org \
    --to=arne_f@ipfire.org \
    --cc=development@lists.ipfire.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