Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.debian.user > #261546

Re: Debian 12 - IPv4 blocked without fail2ban & co

From Max Nikulin <manikulin@gmail.com>
Newsgroups linux.debian.user
Subject Re: Debian 12 - IPv4 blocked without fail2ban & co
Date 2023-09-07 13:00 +0200
Message-ID <HbkTT-7kmu-3@gated-at.bofh.it> (permalink)
References <HaUG6-72RC-5@gated-at.bofh.it> <HbhMl-7hVc-9@gated-at.bofh.it> <Hbkhc-7k6X-7@gated-at.bofh.it> <HbkqR-7kcK-9@gated-at.bofh.it> <HbkAx-7kgd-5@gated-at.bofh.it>
Organization linux.* mail to news gateway

Show all headers | View raw


On 07/09/2023 17:32, Andy Smith wrote:
> On Thu, Sep 07, 2023 at 12:20:18PM +0200, Romain wrote:
>> 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
          ^^^^
>>    9.|-- 192.168.0.2               90.0%    10  3461. 3461. 3461. 3461.   0.0
> To me this suggests that the ICMP Time Exceeded packet is arriving
> with source address 192.168.0.2, which I think means it is being
> sent to you by your own ISP.

I guess, these packets are generated by localhost = rpi4.home = 
192.168.0.2. At first I did not noticed excessively large time in the 
last line.

Concerning question related to .home, perhaps it is just /etc/hosts with
192.168.0.1 livebox.home
192.168.0.2 rpi4.home

I do not suspect some peculiarities in local configuration anymore. 
tcpdump on the server may shed some light if packets from localhost 
arrive to it.

Back to linux.debian.user | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread


Thread

Debian 12 - IPv4 blocked without fail2ban & co Romain <romain@borezo.info> - 2023-09-06 09:00 +0200
  Re: Debian 12 - IPv4 blocked without fail2ban & co Romain <romain@borezo.info> - 2023-09-06 10:50 +0200
  Re: Debian 12 - IPv4 blocked without fail2ban & co Michel Verdier <mv524@free.fr> - 2023-09-06 10:50 +0200
  Re: Debian 12 - IPv4 blocked without fail2ban & co Andy Smith <andy@strugglers.net> - 2023-09-06 11:00 +0200
    Re: Debian 12 - IPv4 blocked without fail2ban & co Romain <romain@borezo.info> - 2023-09-06 11:10 +0200
      Re: Debian 12 - IPv4 blocked without fail2ban & co Andy Smith <andy@strugglers.net> - 2023-09-06 15:30 +0200
        Re: Debian 12 - IPv4 blocked without fail2ban & co Romain <romain@borezo.info> - 2023-09-06 15:40 +0200
          Re: Debian 12 - IPv4 blocked without fail2ban & co Paul van der Vlis <paul@vandervlis.nl> - 2023-09-07 10:00 +0200
            Re: Debian 12 - IPv4 blocked without fail2ban & co Romain <romain@borezo.info> - 2023-09-07 10:40 +0200
  Re: Debian 12 - IPv4 blocked without fail2ban & co Romain <romain@borezo.info> - 2023-09-07 09:40 +0200
    Re: Debian 12 - IPv4 blocked without fail2ban & co Max Nikulin <manikulin@gmail.com> - 2023-09-07 12:20 +0200
      Re: Debian 12 - IPv4 blocked without fail2ban & co Romain <romain@borezo.info> - 2023-09-07 12:30 +0200
        Re: Debian 12 - IPv4 blocked without fail2ban & co Andy Smith <andy@strugglers.net> - 2023-09-07 12:40 +0200
          Re: Debian 12 - IPv4 blocked without fail2ban & co Max Nikulin <manikulin@gmail.com> - 2023-09-07 13:00 +0200
            Re: Debian 12 - IPv4 blocked without fail2ban & co zithro <slack@rabbit.lu> - 2023-09-07 14:20 +0200
              Re: Debian 12 - IPv4 blocked without fail2ban & co Romain <romain@borezo.info> - 2023-09-07 23:50 +0200
                Re: Debian 12 - IPv4 blocked without fail2ban & co Max Nikulin <manikulin@gmail.com> - 2023-09-09 05:00 +0200
                Re: Debian 12 - IPv4 blocked without fail2ban & co Timothy M Butterworth <timothy.m.butterworth@gmail.com> - 2023-09-09 06:50 +0200
                Re: Debian 12 - IPv4 blocked without fail2ban & co Romain <romain@borezo.info> - 2023-09-09 10:40 +0200

csiph-web