I have installed WSL (Windows subsystem for Linux) and I am trying to ping 22.214.171.124 from linux but I am blocked by the FW. When I disable the FW - it’s ok.
I don’t see any event for it in the log, and I don’t know how to unblock it.
I merged your topic with this existing one of the same issue. Try adding Windows Operating System to the firewall application rules and set it to outgoing ruleset. To add WOS you need use the running process option and add it from the running process window. Also make sure windows firewall is off for all 3 profiles but leave the windows firewall service running.
All I know is that WSLv1 works without issues, using WSLv2 only works up to version 126.96.36.19982 as newer CIS builds prevents the creation of the hyper-v virtual network adapter. That issue is supposedly going to be fixed in the next release, as for this issue I think a configuration conflict is causing the blockage. Maybe try using one of the default configs that hasn’t been modified yet.
No switch to one of the default configurations that you have not made changes to, i.e. switch to either the proactive, firewall, or internet security config. Just switch to a different config that is not currently set as the active configuration. Otherwise just wait for the next release to see if it fixes the issue.
Wouldn’t have a clue how would I change it I could only select from custom ruleset or safe mode for the firewall, don’t know where to change what you described. But since then comodo started behanving badly with not showing popups at all so I just disabled the comodo firewall and went with tinywall, now everything works nicely, including wsl2.
Just managed to overcome connectivity issues on my Windows 10 Ubuntu (WSL 2).
Altering the following setting:
Comodo → Advanced Settings → Firewall → Global Rules → Block IP in Any To MAC Any Where Protocol is Any
by excluding the vEthernet (WSL) from this rule (please see attached screenshot),
allowed sudo apt update to execute successfully.