Continuing the discussion from Tor > VPN connection issues - only in 4.1 - multiple test configurations & vpn providers:
Please see the 2nd post in this thread for the Template issue description. This first post is only to offer clarification how I came to the conclusion that the real problem is Template related and not VPN related.
I first noticed some odd networking issue back in alpha 4.1 releases and every release I picked up after through at least a month after beta continued to have the same issues.
Primary Issue (which lead to this template problem discover) VPN’s have issues connecting when connected after a TOR (sys-whonix) connection.
It seems to me, from a number of additional testings I did (see linked post above as well as 2nd post in this thread) that the problem has nothing to do with 4.1 specifically and instead entirely lies within the templates that come with 4.1 (or maybe the way they are installed/networked when installed via template dnf download).
I can’t tell you if this affects all templates. But it definitely affects Fedora 33 & 34 & Debian 10 installed from 4.1
I will explain the reason I believe the templates themselves are the issue in the post immediately following this one, first let me just repeat the actual issue from my other thread.
This is what works and does not work in a new 4.1 installation with templates fd33, fd34, deb10 installed (have not tried deb11 yet)
Assuming I have 2 VPN Qubes we will call VPN1 and VPN2 .
Working
NET > FW > VPN1 > AppVM
NET > FW > VPN2 > AppVM
NET > FW > VPN1 > VPN2 > AppVM
NET > FW > VPN2 > VPN1 > AppVM
NET > FW > VPN1 > SYS-WHONIX > AppVM
NET > FW > VPN2 > SYS-WHONIX > AppVM
Not Working
NET > FW > SYS-WHONIX > VPN1 > AppVM
NET > FW > SYS-WHONIX > VPN2 > AppVM
NET > SYS-WHONIX > VPN1 > AppVM
NET > SYS-WHONIX > VPN2 > AppVM
All of the above with identical Qube configs and layouts 100% work on 4.0
Whonix doesn’t seem to be part of the issue, I have a 4.1 Whonix 15 installed and it’s not breaking the networking.