You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@tlaurion The first thing I'd do is switch the "up" and "down" script to the one that Qubes-vpn-support (or qubes-tunnel) uses... qubes-vpn-ns or qtunnel-connect. This will get DNS working right.
Second, I'd disable the openpyn firewall routine when Qubes is detected (check for file /var/run/qubes/this-is-proxyvm) and use a firewall script from Qubes-vpn-support/qubes-tunnel. This means the firewall is configured at install time (since you want to have Qubes activate it at boot from /rw/config/qubes-firewall.d/90_tunnel-restrict), not at run time.
An alternative might be to integrate in the other direction, for example adapt the config selection routine for qubes-tunnel. Not sure how openpyn does it, but ability to select sites is what I had in mind for the future systray icon: tasket/Qubes-vpn-support#17
@tasket: what else should be done here to adapt openpyn to QubesOS R4?
In QubesOS debian-9 template:
In Qubes proxyVM:
Qubes proxyVM qube settings -> Service: add openpyn
That proxyvm cannot be used by other qubes.
The text was updated successfully, but these errors were encountered: