My problem is resolved.
History of the decision.
My host is fedora 31, firewalld is enabled by default.
I turned off the firewall and the connection through the proxy worked, but not as it should. For unknown reasons, only obfs4 traffic worked through my proxy, and when I disconnected the connection through the proxy, Tor did not want to connect either through obfs4 or through a simple watchdog node - some kind of error. But now I know in which direction, it seems to me, I should go - since the problem is in the firewall. I turned on the firewall again and after searching on Google I found an article on the official Libvirt website which says that when installing KVM/libvirt it creates its own zone called libvirt. My solution was to add advanced firewall rules.
Here are my steps:
- Setting the proxy for listening - 10.0.2.2:1080
10.0.2.2 - ip of the Whonix Gateway virtual interface.
1080 - is the port that the proxy listens on.
- Add advanced firewall rules. Allow the connection from the specified ip and port.
firewall-cmd --permanent --zone = libvirt --add-rich-rule = ‘rule family = “ipv4” source address = “10.0.2.15” port protocol = “tcp” port = “1080” accept’
10.0.2.15 - ip of the Whonix Gateway virtual machine
1080 - the port specified for listening in the proxy client.
- Connected using the anon connection wizard to my socks5 client through the ip gateway and port -
That is actually all. Now everything works.