From: Aaron Conole <aconole@redhat.com>
To: Thomas Monjalon <thomas@monjalon.net>
Cc: Benjamin Andru <bandru@kalrayinc.com>,
web@dpdk.org, ci@dpdk.org,
Julien Hascoet <jhascoet@kalrayinc.com>,
Matheus Schuh <mschuh@kalrayinc.com>,
alialnu@nvidia.com
Subject: Re: Public IP blacklisted ?
Date: Mon, 29 Jan 2024 10:57:04 -0500 [thread overview]
Message-ID: <f7to7d4yvxr.fsf@redhat.com> (raw)
In-Reply-To: <2001415.CrzyxZ31qj@thomas> (Thomas Monjalon's message of "Mon, 29 Jan 2024 11:14:40 +0100")
Thomas Monjalon <thomas@monjalon.net> writes:
> 29/01/2024 10:41, Benjamin Andru:
>> Hello,
>>
>> We have a issue when we try to reach your website
>> "http://core.dpdk.org/<http://core.dpdk.org/doc/>" from our
>> headquarters.
>> We think that we were blacklisted due to a script we've run
>> It "wget" http://dpdk.org/browse/dpdk/snapshot a lot...
>>
>> We fixed that 12 january 2024.
>
> How did you fix it?
> We asked to use GitHub URL in scripts:
> http://inbox.dpdk.org/ci/5933180.BEx9A2HvPv@thomas/
Add onto this - what is the purpose of polling that URL with wget?
>> Can you remove your blacklist entry for 217.181.231.53 ?
>
> Unfortunately you didn't reply to above email,
> so we didn't know who was blacklisted.
>
>> Users in copy can tell you why we really want to have access to your website 🙂
>
> Ali can unblock and monitor your activity on the server.
Maybe you can help as well to add a custom user agent with your script
so we can at least know what you are polling when you hit the DPDK
servers?
next prev parent reply other threads:[~2024-01-29 15:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-29 9:41 Benjamin Andru
2024-01-29 10:14 ` Thomas Monjalon
2024-01-29 15:57 ` Aaron Conole [this message]
2024-01-29 17:55 ` Ali Alnubani
2024-01-29 21:00 ` Benjamin Andru
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=f7to7d4yvxr.fsf@redhat.com \
--to=aconole@redhat.com \
--cc=alialnu@nvidia.com \
--cc=bandru@kalrayinc.com \
--cc=ci@dpdk.org \
--cc=jhascoet@kalrayinc.com \
--cc=mschuh@kalrayinc.com \
--cc=thomas@monjalon.net \
--cc=web@dpdk.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 NNTP newsgroup(s).