From: "Frank Ch. Eigler" <fche@redhat.com>
To: Overseers mailing list <overseers@sourceware.org>
Cc: Alexandre Oliva <oliva@gnu.org>
Subject: Re: friend reports blocked IP address
Date: Fri, 19 Mar 2021 11:26:13 -0400 [thread overview]
Message-ID: <20210319152613.GD11451@redhat.com> (raw)
In-Reply-To: <oreegbsqxs.fsf@lxoliva.fsfla.org>
Hi -
> lkcl, free software developer and activist, and project lead of
> libre-soc.org (and of eoma68 fame) tells me his server, lkcl.net AKA
> 217.147.94.29, has been blocked from accessing sourceware.org for
> months. Any clue as to why? Could the block possibly be lifted?
I don't see a trace of such a block. I see named complaining about
the domain:
Mar 19 12:24:08 server2 named[2640590]: REFUSED unexpected RCODE resolving 'ns1.libre-soc.org/AAAA/IN': 217.147.94.29#53
Mar 19 12:24:08 server2 named[2640590]: REFUSED unexpected RCODE resolving 'ns1.libre-soc.org/A/IN': 217.147.94.29#53
Mar 19 12:24:08 server2 named[2640590]: REFUSED unexpected RCODE resolving 'libre-riscv.ns.libre-soc.org/A/IN': 217.147.94.29#53
Mar 19 12:24:08 server2 named[2640590]: REFUSED unexpected RCODE resolving 'ns.libre-soc.org/A/IN': 217.147.94.29#53
Mar 19 12:24:08 server2 named[2640590]: REFUSED unexpected RCODE resolving 'libre-riscv.ns.libre-soc.org/AAAA/IN': 217.147.94.29#53
Mar 19 12:24:08 server2 named[2640590]: REFUSED unexpected RCODE resolving 'ns.libre-soc.org/AAAA/IN': 217.147.94.29#53
In the postfix logs, I see numerous errors like:
Mar 19 15:22:05 server2 postfix/smtp[3889716]: connect to smtp.lkcl.net[2002:2eeb:e34d::1]:25: Connection timed out
Mar 19 15:22:35 server2 postfix/smtp[3889716]: connect to smtp.lkcl.net[217.147.94.29]:25: Connection timed out
Mar 19 15:23:05 server2 postfix/smtp[3889716]: connect to smtp2.lkcl.net[217.147.94.29]:25: Connection timed out
Mar 19 15:23:05 server2 postfix/smtp[3889716]: 7F05B3857C60: to=<lkcl@lkcl.net>, relay=none, delay=357781, delays=357691/0/90/0, dsn=4.4.1, status=deferred (connect to smtp2.lkcl.net[217.147.94.29]:25: Connection timed out)
and a local outgoing telnet confirms inability to reach that host on
port 25, but I don't think it's anything we're doing.
- FChE
prev parent reply other threads:[~2021-03-19 15:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-19 4:33 Alexandre Oliva
2021-03-19 15:26 ` Frank Ch. Eigler [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=20210319152613.GD11451@redhat.com \
--to=fche@redhat.com \
--cc=oliva@gnu.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).