Hi,
On Mon, Dec 02, 2024 at 12:38:23PM -0500, vi...@wlcr.net wrote:
> No idea how to troubleshoot that one.
What specifically do you want to troubleshoot?
My question would be:
whois in Debian 11 seems to consistently receive the blocked query
error showing a LACNIC IP while whois in Debian 12 doesn't, yet both
of them do contact LACNIC servers initially. So is this difference
due to different behaviour in Debian's whois, pure chance or
something else?
I'm not very motivated to do it personally but if you are you might want
to ask something like that to the Debian whois package maintainers (in a
bug report).
Some have said it's not a Debian issue, and that might be the case
since all error messages show RIPE blocking LACNIC, but I can't make it
happen with Debian 12.
It could also be worth asking RIPE about the block. They might just say
that it's due to client behaviour though.
For example, it was pointed out that using -r avoids the problem. It
could be that -r became a default with a later version. Reasons like
that are why I might ask Debian first (in a bug report).
> here's a new one of the same problem:
Is there any value in reporting more of these here? You're replying to a
message where I point out that:
- (some versions of) Debian's whois contact a LACNIC server that proxies
queries to RIPE servers which then block the LACNIC server, returning
an error message
you then post another example of this error message. What more have we
learned?
> %ERROR:201: access denied for 168.121.184.15
> I have nothing to do with 168.121.184.15.
Like I said, these things will be reverse proxies inside the
infrastructure of LACNIC or RIPE.
inetnum: 168.121.184.0/22
owner: LACNIC - Latin American and Caribbean IP address
It's pretty clear to me that (some versions of) whois contact a LACNIC
server which then contacts RIPE and is blocked.
> Short of packet capture and analysis, Is there such a thing as a traceroute
> following a command like whois?
You don't need one since the RIPE server helpfully told you which IP
address it is blocking.
I guess there could be multiple other steps within, but apparently none
of those steps are giving us a problem.
Thanks,
Andy
--
https://bitfolk.com/ -- No-nonsense VPS hosting
