[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Debian 12 - IPv4 blocked without fail2ban & co



As already reported, when it's blocked, all traffic is blocked on IPv4, including SSH & HTTP.

Le sam. 9 sept. 2023 à 06:42, Timothy M Butterworth <timothy.m.butterworth@gmail.com> a écrit :


On Fri, Sep 8, 2023 at 10:52 PM Max Nikulin <manikulin@gmail.com> wrote:
On 08/09/2023 04:39, Romain wrote:
> I can confirm that when this happens, it's the OVH server that fails to
> send the response to my network.
>
> 35 9.862648672 MY_PUBLIC_IP_AT_HOME → 54.38.38.159 ICMP 78 Echo (ping)
> request  id=0x4b30, seq=33150/32385, ttl=1
> 36 9.862704895 54.38.38.159 → MY_PUBLIC_IP_AT_HOME  ICMP 106 Destination
> unreachable (Port unreachable)

Your hosting company may have PING flood protection. If you are running a constant PING from your PC to your server it could be detected as a PING flood. Are you able to SSH to the server while the PING is failing?

 
Some intermediate firewall may have specific rules for ICMP.

It is better to try tcpdump (its capture file may be later loaded to
wireshark) for HTTP and SSH packets at 54.38.38.159 and 192.168.0.2
rpi4.home, or if your router allows it, even better at 192.168.0.1
livebox.home.




--
⢀⣴⠾⠻⢶⣦⠀
⣾⠁⢠⠒⠀⣿⡁ Debian - The universal operating system
⢿⡄⠘⠷⠚⠋⠀ https://www.debian.org/
⠈⠳⣄⠀⠀

Reply to: