Thanks Chris...again thank you for the effort! This tool is great...
Does it matter that Private internet access provides 3 seperate files (key,
cert and client config)?
I have the proxy AppVM set up with "provides network"(proxy) checked, I have
tried a setup in proxy only and a setup in Template/Proxy, PVH(tried
PV...similar to 3.2)...I don't think it is the setup as much as the
configuration of the template?
I installed GNOME and Openvpn (Using those names specifically) in Debian, no
additional packages installed in stock fedora...
I feel like I am missing a very basic command or tweak, whonix works, wireless
works, sys-firewall works...any help would be appreciated. It seems something
releated to PIA VPN configuration or VPN-handler-openvpn
Here are my logs/commands from your suggestions:
root@sys-VPNb5:/home/user# ls -l /rw/config/qubes-firewall.d
total 0
lrwxrwxrwx 1 root root 38 Apr 5 13:16 90_tunnel-restrict ->
/usr/lib/qubes/proxy-firewall-restrict
root@sys-VPNb5:/home/user# iptables -v -L FORWARD
Chain FORWARD (policy DROP 0 packets, 0 bytes)
pkts bytes target prot opt in out source destination
0 0 DROP all -- eth0 any anywhere anywhere
0 0 DROP all -- any eth0 anywhere anywhere
0 0 ACCEPT all -- any any anywhere anywhere
ctstate RELATED,ESTABLISHED
0 0 QBS-FORWARD all -- any any anywhere anywhere
0 0 DROP all -- vif+ vif+ anywhere anywhere
0 0 ACCEPT all -- vif+ any anywhere anywhere
0 0 DROP all -- any any anywhere anywhere
I copied errors when I run journalctl:
Apr 06 02:09:52 sys-VPNb5 gnome-terminal-[966]: unable to open file
'/etc/dconf/db/local': Failed to open file '/etc/dconf/db/local': open()
failed: No such file or directory; expect degra
Apr 06 02:09:50 sys-VPNb5 systemd[664]: pam_unix(systemd-user:session): session
opened for user user by (uid=0)
Apr 06 02:09:50 sys-VPNb5 systemd[1]: qubes-vpn-handler.service: Control
process exited, code=exited status=1
Apr 06 02:09:50 sys-VPNb5 systemd[1]: Failed to start VPN Client for Qubes
proxyVM.
Apr 06 02:09:46 localhost systemd[1]: Started Adjust root filesystem size.
Apr 06 02:09:46 localhost kernel: Error: Driver 'pcspkr' is already registered,
aborting...
Apr 06 02:09:46 localhost mount-dirs.sh[351]: Private device management:
fsck.ext4 of /dev/xvdb succeeded
Apr 06 02:09:45 localhost kernel: xvdc: xvdc1
Apr 06 02:09:45 localhost kernel: EXT4-fs (xvda3): couldn't mount as ext3 due
to feature incompatibilities
Apr 06 02:09:45 localhost kernel: EXT4-fs (xvda3): couldn't mount as ext2 due
to feature incompatibilities
Apr 06 02:09:45 localhost kernel: EXT4-fs (xvda3): mounted filesystem with
ordered data mode. Opts: (null)
Apr 06 02:09:45 localhost kernel: EXT4-fs (xvdd): mounting ext3 file system
using the ext4 subsystem
Apr 06 02:09:45 localhost kernel: dmi-sysfs: dmi entry is absent.
Apr 06 02:09:50 sys-VPNb5 systemd[1]: Started Serial Getty on hvc0.
Apr 06 02:09:50 sys-VPNb5 systemd[1]: Reached target Login Prompts.
Apr 06 02:09:50 sys-VPNb5 systemd[664]: pam_unix(systemd-user:session): session
opened for user user by (uid=0)
Apr 06 02:09:50 sys-VPNb5 systemd[1]: qubes-vpn-handler.service: Control
process exited, code=exited status=1
Apr 06 02:09:50 sys-VPNb5 systemd[1]: Failed to start VPN Client for Qubes
proxyVM.
Apr 06 02:09:50 sys-VPNb5 systemd[1]: qubes-vpn-handler.service: Unit entered
failed state.
Apr 06 02:09:50 sys-VPNb5 systemd[1]: qubes-vpn-handler.service: Failed with
result 'exit-code'.
Apr 06 02:09:50 sys-VPNb5 systemd[664]: Listening on GnuPG network certificate
management daemon.
Apr 06 02:09:50 sys-VPNb5 systemd[664]: Listening on GnuPG cryptographic agent
(ssh-agent emulation).
--
You received this message because you are subscribed to the Google Groups
"qubes-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/qubes-users/dcabc134-6488-46c4-a359-bca31e0d365e%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
