ArminM

As you can see in the first screenshot, the ESET firewall blocks access to svchost/udp/53 coming from the 172.17.87 network. So it seems to me that the automatic firewall mode (whatever it normally does) does not handle this and that I have to create a manual rule to allow those connections. That solves my problem, but I kind of had expected that this would not require manual interaction, given that the WSL2 / 172.17.87 network could/should be a trusted network. But the labeling of the networks I had accumulated over time (like Virtual Network 21) doesn't give me any clues there. Anyway, I guess my issues is solved for now with the manual rule.

Well, the repro is really simple, start a WSL2 shell and observe the activity in the ESET dashboard. I can of course unblock that specific occurrence, but next time, WSL2's IP will change, so it seems to me this really requires an additional firewall rule which I created now for remote 172.17.87.0/24 to port 53 local udp on svchost. For now that seems to work.

Hi, so I read this topic, I have the latest ESET IS version, and the network is trusted, still it blocks access for the WSL2 network. For now, If unlocked that specific IP, but that won't help for other IPs on the subnet. What am I missing, i.e. how do I properly unblock that adapter? Thanks.