Re: Debian 12 - IPv4 blocked without fail2ban & co

[Romain <romain@borezo.info>]

No, I'm using the DNS server included in my ISP modem, in which I can only select the last digits. It's impossible that an internal device has received a public IP address in the DNS zone (or it's not something I've done).

With -n (sometimes it stops at hop 7, sometimes 9):

└─# mtr -nr 54.38.38.159 -4
Start: 2023-09-07T08:17:12+0000
HOST: rpi4                        Loss%   Snt   Last   Avg  Best  Wrst StDev
  1.|-- 192.168.0.1                0.0%    10    1.1   0.9   0.5   1.3   0.3
  2.|-- 80.10.239.9                0.0%    10    3.2   3.3   2.3   5.3   0.9
  3.|-- 193.253.80.138             0.0%    10    4.5   4.0   2.2   6.0   1.2
  4.|-- 193.252.98.94              0.0%    10    3.4   4.3   3.1  12.2   2.8
  5.|-- 193.252.98.101             0.0%    10    3.5   3.4   2.9   3.6   0.2
  6.|-- 91.121.131.193             0.0%    10    4.0  12.4   3.7  82.6  24.7
  7.|-- ???                       100.0    10    0.0   0.0   0.0   0.0   0.0
  8.|-- ???                       100.0    10    0.0   0.0   0.0   0.0   0.0
  9.|-- 192.168.0.2               90.0%    10  3461. 3461. 3461. 3461.   0.0

Le jeu. 7 sept. 2023 à 12:17, Max Nikulin <manikulin@gmail.com> a écrit :

On 07/09/2023 14:31, Romain wrote:
>   12.|-- rpi4.home                 90.0%    10  7955. 7955. 7955. 7955.
>    0.0

May it happen that you associated a local device with the IP of your
remote server? Check configuration of the .home DNS zone. Try to add -n
option to suppress DNS lookup and compare results.