![]() ![]() Some kind of mismatch between fedora-34 and fedora-34-minimal. Regardless, it works with the egress rules gone with that and I appreciate this tool, makes setting up VPN much easier / faster than the standard guide, thanks!Īpr 01 23:31:21 sys-vpn openvpn: Initialization Sequence CompletedĪpr 01 23:31:24 sys-vpn openvpn: read UDP : No route to host (code=113)Īpr 01 23:31:29 sys-vpn openvpn: read UDP : No route to host (code=113)Īpr 01 23:31:37 sys-vpn openvpn: read UDP : No route to host (code=113) I know far too little about configuring firewall rules correctly in Linux to be of much help with that. Perhaps something needs to be adjusted in the firewall scripts to make it more compatible with 34+? Your suggestion you just posted to enable vpn-handler-egress actually “fixes” this problem as you suggested, so that’s great! But this probably shouldn’t be necessary should it? The only difference between my two ProxyVM templates is that one is Fedora 33 and the other is Fedora 34, they’re both configured exactly the same way and the vpn-handler-egress is only required in 34. ![]() Also only exists if/when the Qubes-vpn-support is installed, it does not occur in the same VM if I fully remove it from the system (at which point I can connect to the vpn using standard openvpn commands as normal from the same Fedora 34 VM). I’ve been having same issues with dns name resolution as the OP but these issues only exist in Fedora 34 VM’s and not in Fedora 33 ones. Hey are you using your own Qubes-vpn-support tool & setup in a Fedora-34 VM as the ProxyVM? ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |