Jump to content

ludo84

Members
  • Posts

    2
  • Joined

  • Last visited

About ludo84

  • Rank
    Newbie
    Newbie

Profile Information

  • Location
    France
  1. OK, i found the source of problem. Indeed, it is a problem of nftable ruleset, ESET inject NAT rules with higher priority (priority -101). ESET rules NAT all TCP connections to 127.0.0.1:37687. But these strange connections are forbidden by my rules. I hope this port is static ! => not ! I will add a specific rule to accept this. (all interface, all IP to 127.0.0.1, is not beautiful) in output chain: ip daddr 127.0.0.1 tcp dport 1024-65535 accept
  2. Hy all, I have a problem with my nftables firewalls since i had installed ESET on my Linux Server. I have strange behavior of the loopback interface. Internal connections go through the network card, not "lo". These unusual connections are therefore blocked by the firewall. Bad log with ESET WAP: IN= OUT=wlp3s0 SRC=192.168.0.XXX DST=127.0.0.1 LEN=60 ............... Good log without ESET_WAP IN= OUT=lo SRC=127.0.0.1 DST=127.0.0.1 LEN=60 ............... System: Ubuntu 22LTS Kernel 6.5.0-25-generic ESET 10.2.2.0 Note: I have the problem with Debian 12 server.
×
×
  • Create New...