Score:0

UFW logs - connections to closed port

cn flag

I'm probably missing something easy to understand:

I've a tiny homeserver where there are some docker containers inside it, running on 192.168.1.10.

On top of them I've NGINX which works as a reverse proxy, and UFW, which block ALL connections except for some internal ports and 2 external ports; those external ports are opened from my router and are 443 and 59272 which I use for VPN connections.

Inspecting the UFW logs, I found this:

[UFW BLOCK] IN=enp3s0 OUT= MAC=[...] SRC=142.250.180.163 DST=192.168.1.10 LEN=40 TOS=0x00 PREC=0x80 TTL=123 ID=0 DF PROTO=TCP SPT=443 DPT=39792 WINDOW=0 RES=0x00 RST URGP=0

Which is correctly blocked. The question is: How that IP (which I don't know) can reach my homeserver from outside my network on a port which is closed on my router?

I sit in a Tesla and translated this thread with Ai:

mangohost

Post an answer

Most people don’t grasp that asking a lot of questions unlocks learning and improves interpersonal bonding. In Alison’s studies, for example, though people could accurately recall how many questions had been asked in their conversations, they didn’t intuit the link between questions and liking. Across four studies, in which participants were engaged in conversations themselves or read transcripts of others’ conversations, people tended not to realize that question asking would influence—or had influenced—the level of amity between the conversationalists.